From: Ben Hutchings <bhutchings@solarflare.com>
To: John Lumby <johnlumby@hotmail.com>
Cc: netdev@vger.kernel.org
Subject: Re: r8169 : always copying the rx buffer to new skb
Date: Mon, 18 Apr 2011 18:27:56 +0100 [thread overview]
Message-ID: <1303147676.2857.20.camel@bwh-desktop> (raw)
In-Reply-To: <4DAC7001.9060800@hotmail.com>
On Mon, 2011-04-18 at 13:08 -0400, John Lumby wrote:
> Summary - current r8169 always memcpy's every received buffer to new skb,
> and I'd like to propose that it should not,
> which can improve throughput / reduce CPU utilization by
> around 10%
At least some variants of the hardware have a bug in RX DMA scatter that
can be exploited for denial-of-service. The workaround is to allocate
huge RX buffers (16K). Then, to avoid allocation failures later on (and
to save memory) the buffers must be copied rather than passed up the
stack and reallocated.
[...]
> As a second proposal (which I made before), I'd like to suggest that
> the number of rx buffers allocated at open should be configurable by
> module param.
[...]
No, it should implement the ethtool set_ringparam operation.
Ben.
--
Ben Hutchings, Senior Software Engineer, Solarflare
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.
next prev parent reply other threads:[~2011-04-18 17:27 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-18 17:08 r8169 : always copying the rx buffer to new skb John Lumby
2011-04-18 17:27 ` Ben Hutchings [this message]
2011-04-18 21:26 ` John Lumby
2011-04-20 19:13 ` Francois Romieu
2011-04-21 3:41 ` John Lumby
2011-04-21 3:52 ` John Lumby
2011-04-27 2:18 ` John Lumby
2011-04-27 3:57 ` Eric Dumazet
2011-04-27 20:35 ` Francois Romieu
2011-04-29 1:55 ` John Lumby
2011-04-29 4:54 ` Eric Dumazet
2011-05-02 19:04 ` Chris Friesen
2011-05-03 11:59 ` hayeswang
2011-04-18 18:21 ` Francois Romieu
-- strict thread matches above, loose matches on Subject: below --
2011-06-27 22:54 John Lumby
2011-06-28 7:55 ` Francois Romieu
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=1303147676.2857.20.camel@bwh-desktop \
--to=bhutchings@solarflare.com \
--cc=johnlumby@hotmail.com \
--cc=netdev@vger.kernel.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).