From: David Miller <davem@davemloft.net>
To: eric.dumazet@gmail.com
Cc: shemminger@vyatta.com, jesse.brandeburg@gmail.com, hawk@diku.dk,
netdev@vger.kernel.org
Subject: Re: [RFC] skb align patch
Date: Mon, 21 Sep 2009 22:29:40 -0700 (PDT) [thread overview]
Message-ID: <20090921.222940.258576265.davem@davemloft.net> (raw)
In-Reply-To: <4AB84295.3050509@gmail.com>
From: Eric Dumazet <eric.dumazet@gmail.com>
Date: Tue, 22 Sep 2009 05:20:53 +0200
> Oh I see, you want to optimize the rx (NIC has to do a DMA to write
> packet into host memory and this DMA could be a read /modify/write
> if address is not aligned, instead of a pure write), while I tried
> to align skb to optimize the pktgen tx (NIC has to do a DMA to read
> packet from host), and align the skb had no effect.
This is a problem with these kinds of changes.
This patch from Stephen came out of a presentation and discussion
at netconf where the Intel folks showed that if they did a combination
of things it improved NUMA forwarding numbers a lot.
So you couldn't just do NUMA spreading of RX queue memory, or just
do this ALIGN patch, or just eliminate the false sharing from
statistics updates.
You had to do all three to start seeing forwarding rates go up.
So don't worry, this is getting us somewhere to where improvement
shows, but individually each change won't trigger it.
The alignment in this patch is a real big deal for 64 byte forwarding
tests, where the entire packet is a whole PCI-E cacheline. But not
if it isn't aligned properly.
next prev parent reply other threads:[~2009-09-22 5:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-20 21:22 [RFC] skb align patch Stephen Hemminger
2009-09-21 6:13 ` Eric Dumazet
2009-09-22 4:30 ` Stephen Hemminger
2009-09-22 3:20 ` Eric Dumazet
2009-09-22 5:23 ` Stephen Hemminger
2009-09-22 5:29 ` David Miller [this message]
2009-09-23 5:47 ` Thomas Graf
2009-09-25 22:18 ` Herbert Xu
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=20090921.222940.258576265.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=hawk@diku.dk \
--cc=jesse.brandeburg@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=shemminger@vyatta.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).