DPDK patches and discussions
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: Nelson Escobar <neescoba@cisco.com>
Cc: dev@dpdk.org, johndale@cisco.com
Subject: Re: [dpdk-dev] [PATCH v2] enic: scattered Rx
Date: Fri, 24 Jun 2016 11:42:59 +0100	[thread overview]
Message-ID: <20160624104258.GA13456@bricha3-MOBL3> (raw)
In-Reply-To: <1466104745-21528-1-git-send-email-neescoba@cisco.com>

On Thu, Jun 16, 2016 at 12:19:05PM -0700, Nelson Escobar wrote:
> For performance reasons, this patch uses 2 VIC RQs per RQ presented to
> DPDK.
> 
> The VIC requires that each descriptor be marked as either a start of
> packet (SOP) descriptor or a non-SOP descriptor.  A one RQ solution
> requires skipping descriptors when receiving small packets and results
> in bad performance when receiving many small packets.
> 
> The 2 RQ solution makes use of the VIC feature that allows a receive
> on primary queue to 'spill over' into another queue if the receive is
> too large to fit in the buffer assigned to the descriptor on the
> primary queue.  This means that there is no skipping of descriptors
> when receiving small packets and results in much better performance.
> 
> Signed-off-by: Nelson Escobar <neescoba@cisco.com>
> Reviewed-by: John Daley <johndale@cisco.com>
> ---
> 
Applied to dpdk-next-net/rel_16_07

/Bruce

      reply	other threads:[~2016-06-24 10:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-14 23:55 [dpdk-dev] [PATCH] " Nelson Escobar
2016-06-16 19:19 ` [dpdk-dev] [PATCH v2] " Nelson Escobar
2016-06-24 10:42   ` Bruce Richardson [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20160624104258.GA13456@bricha3-MOBL3 \
    --to=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=johndale@cisco.com \
    --cc=neescoba@cisco.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).