DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Wang, Shawn" <xingbow@amazon.com>
To: "Pattan, Reshma" <reshma.pattan@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Newbie question about distributor library
Date: Fri, 10 Oct 2014 21:06:13 +0000	[thread overview]
Message-ID: <12C2AAD9525203489F7B523D670129D91CA95933@ex10-mbx-31007.ant.amazon.com> (raw)
In-Reply-To: <3AEA2BF9852C6F48A459DA490692831FE22975@IRSMSX109.ger.corp.intel.com>

15.5 mpps is amazing.
Does the RX core run the distributor or there is another distributor core?

Thanks.
________________________________________
From: Pattan, Reshma [reshma.pattan@intel.com]
Sent: Friday, October 10, 2014 12:47 AM
To: Wang, Shawn; dev@dpdk.org
Subject: RE: Newbie question about distributor library

> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Wang, Shawn
> Sent: Thursday, October 9, 2014 7:00 PM
> To: dev@dpdk.org
> Subject: [dpdk-dev] Newbie question about distributor library
>
> Hi:
>
> I am reading document about distributor library which is added in DPDK 1.7.
> The document mentioned the packets are dynamically load balanced between a
> set of worker cores.
> So I am wondering is this the only reason we need distributor library? What else
> could it give us?
> Do we have any performance number on this new library?
>
> Thanks.

Hi,

Distributor library  only takes care of load distribution based on flow type i.e. based on rss ( which is calculated based on 5 tuple of the packet)
value of mbuf to workers. Packets with same rss will be given to same worker. Hence different flows goes to different workers.

15.5 mpps was the performance  we achieved  with 8 worker cores, 1 Rx core and 1 TX core using sample application.

Thanks,
Reshma



  reply	other threads:[~2014-10-10 20:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-09 17:59 Wang, Shawn
2014-10-10  7:47 ` Pattan, Reshma
2014-10-10 21:06   ` Wang, Shawn [this message]
2014-10-12  9:00     ` Pattan, Reshma

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=12C2AAD9525203489F7B523D670129D91CA95933@ex10-mbx-31007.ant.amazon.com \
    --to=xingbow@amazon.com \
    --cc=dev@dpdk.org \
    --cc=reshma.pattan@intel.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).