From: "Wiles, Keith" <keith.wiles@intel.com>
To: Theano <theanosaurus@gmail.com>
Cc: "users@dpdk.org" <users@dpdk.org>,
Christopher Hodsdon <chrischodsdon@gmail.com>
Subject: Re: [dpdk-users] Throughput dropping by half with 1B increase in packet size
Date: Fri, 9 Feb 2018 15:55:28 +0000 [thread overview]
Message-ID: <006F812B-472C-492F-9E0A-30D1E430933E@intel.com> (raw)
In-Reply-To: <CABYfMMg-q-ktLJ-7AkS7BCxhqA-swMisjcQKZHiv2S27DQWq9A@mail.gmail.com>
> On Feb 9, 2018, at 9:39 AM, Theano <theanosaurus@gmail.com> wrote:
>
> Hi All,
>
> We are eventually going to build an application over DPDK, and we've
> started out with a very simple pktgen-like application that sends and
> receives packets to a different machine running l2fwd.
>
> With packets up to 64B (60B headers and payload + 4B of FCS), l2fwd shows
> line rate packet forwarding of this application's packets. As soon as the
> packet size increases to 65B, the throughput (in pps) halves. With
> dpdk-pktgen we observe a much more graceful decline in packet throughput as
> packet size increases.
>
> I examined the dpdk-pktgen code and can't find any significant differences
> between how it constructs its packets vs. how we do it, but of course I'm
> missing something.
>
> Has anyone seen this before and/or has any ideas on how to identify the
> problem?
Adding one byte will push you to have two cache lines used and that can reduce performance. Make sure the packets are aligned to a 64 byte boundary.
Other then that I see no reason for the 1/2 performance without comparing the code. Pktgen-dpdk I spent a fair amount of time looking at the performance, but I also had to play with burst size and the number of packet sent to the NIC they too need to be cached aligned or multiples of a cache line.
>
> We are using DPDK version 17.02.1; please let me know if any other
> information would be helpful.
> Thanks,
> Theano.
Regards,
Keith
parent reply other threads:[~2018-02-09 15:55 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <CABYfMMg-q-ktLJ-7AkS7BCxhqA-swMisjcQKZHiv2S27DQWq9A@mail.gmail.com>]
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=006F812B-472C-492F-9E0A-30D1E430933E@intel.com \
--to=keith.wiles@intel.com \
--cc=chrischodsdon@gmail.com \
--cc=theanosaurus@gmail.com \
--cc=users@dpdk.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).