From: Shinae Woo <shinae2012@gmail.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] Performances are not scale with multiple ports
Date: Tue, 28 May 2013 13:00:25 +0900 [thread overview]
Message-ID: <CA+f=ZzuPLuup+ntqGSD3wrB6mVM6d8+8bo58j+egn82g94tdEQ@mail.gmail.com> (raw)
In-Reply-To: <20130527202946.75184090@nehalam.linuxnetplumber.net>
[-- Attachment #1: Type: text/plain, Size: 1563 bytes --]
Actually, I made my own packet reception application using DPDK
to utilize multiple RSS which map each core (in my case, 12 queues for 12
cores).
But it shows that multiple RSS shows, the reception performance is rather
decreasing as below.
# queue
1 2 3 4 5 6 Bandwidth (Gbps) 8.95 8.90 8.89 8.57 7.95 7.62 #queue 7 8 9
10 11 12 Bandwidth (Gbps) 7.18 7.13 7.12 7.04 7.58 6.80
I will try with testpmd to load balance again.
I use the custom packet generator module over Packet I/O,
but I'm looking forward to the pktgen for DPDK of Stephen's, too.
Thanks,
Shinae
On Tue, May 28, 2013 at 12:29 PM, Stephen Hemminger <
stephen@networkplumber.org> wrote:
> On Mon, 27 May 2013 20:15:23 -0700
> Emre Eraltan <emre.eraltan@6wind.com> wrote:
>
> > Hello Shinae,
> >
> > Did you try to use the testpmd tool with multiple queues per port? It
> > gives you more flexibility compared to l2fwd app.
> >
> > You need to trigger the RSS feature of the NIC by sending different
> > streams (just by changing the destination port for instance or any
> > information in the 5-tuple). This will load balance your packets among
> > several cores so that you can probe multiple queues with different
> > cores. Otherwise, you will use only one core (or thread if HT is
> > enabled) per port for the RX side.
> >
> > Best Regards,
> > Emre
> >
>
> I wrote a partial baked version of pktgen for DPDK. Let me see if I can
> get ok to release and clean it up.
>
> Windriver has one as well, and they use it in their demo clases.
> Not sure why it never got included.
>
>
[-- Attachment #2: Type: text/html, Size: 4037 bytes --]
next prev parent reply other threads:[~2013-05-28 4:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-28 2:26 Shinae Woo
2013-05-28 2:30 ` Naoto MATSUMOTO
2013-05-28 3:05 ` Shinae Woo
2013-05-28 3:15 ` Emre Eraltan
2013-05-28 3:29 ` Stephen Hemminger
2013-05-28 4:00 ` Shinae Woo [this message]
2013-05-29 3:09 ` Naoto MATSUMOTO
2013-05-28 9:22 ` Thomas Monjalon
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='CA+f=ZzuPLuup+ntqGSD3wrB6mVM6d8+8bo58j+egn82g94tdEQ@mail.gmail.com' \
--to=shinae2012@gmail.com \
--cc=dev@dpdk.org \
--cc=stephen@networkplumber.org \
/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).