From: Ben Hutchings <bhutchings@solarflare•com>
To: Dave Taht <dave.taht@gmail•com>
Cc: Eric Dumazet <eric.dumazet@gmail•com>,
Tom Herbert <therbert@google•com>, <davem@davemloft•net>,
<netdev@vger•kernel.org>
Subject: Re: [PATCH v4 0/10] bql: Byte Queue Limits
Date: Tue, 29 Nov 2011 16:41:29 +0000 [thread overview]
Message-ID: <1322584889.2684.25.camel@bwh-desktop> (raw)
In-Reply-To: <CAA93jw5UG4=QRN3Wnh82wRg8YCSV7vDqGp0HyeVxsihUwLuioQ@mail.gmail.com>
On Tue, 2011-11-29 at 17:06 +0100, Dave Taht wrote:
> On Tue, Nov 29, 2011 at 3:29 PM, Eric Dumazet <eric.dumazet@gmail•com> wrote:
> > Le mardi 29 novembre 2011 à 14:24 +0000, Ben Hutchings a écrit :
> >
> >> Not if you separate hardware queues by priority (and your high priority
> >> packets are non-TCP or PuSHed).
> >
> > I mostly have tg3 , bnx2 cards, mono queues...
> >
> > I presume Dave, working on small Wifi/ADSL routers have same kind of
> > hardware.
>
> Nothing but mono queues here on wired - 4 queues on wireless, however.
>
> and a focus on trying to make sure the
> 10Gig guys don't swamp the 128Kbit to 100Mbit guys, and everything in
> between that bandwidth range is what I care about, mostly against GigE
> servers...
I'm not objecting to that, just the assertion that TSO can be a problem
even on 10G hardware. In fact it makes a big improvement to CPU
efficiency (even if you do it in the driver, it can be better than GSO)
and almost all 10G hardware has multiple queues which can be used to
avoid the latency penalty.
> ( I'm still waiting on some 10Gig hw donations to arrive)
[...]
If you have a proposal to do interesting things with 10G hardware and
drivers then I can forward it for consideration here.
Ben.
--
Ben Hutchings, Staff 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-11-29 16:41 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-29 2:32 [PATCH v4 0/10] bql: Byte Queue Limits Tom Herbert
2011-11-29 4:23 ` Dave Taht
2011-11-29 7:02 ` Eric Dumazet
2011-11-29 7:07 ` Eric Dumazet
2011-11-29 7:23 ` John Fastabend
2011-11-29 7:45 ` Eric Dumazet
2011-11-29 8:03 ` John Fastabend
2011-11-29 8:37 ` Dave Taht
2011-11-29 8:43 ` Eric Dumazet
2011-11-29 8:51 ` Dave Taht
2011-11-29 14:57 ` Eric Dumazet
2011-11-29 16:24 ` Dave Taht
2011-11-29 17:06 ` David Laight
2011-11-29 14:24 ` Ben Hutchings
2011-11-29 14:29 ` Eric Dumazet
2011-11-29 16:06 ` Dave Taht
2011-11-29 16:41 ` Ben Hutchings [this message]
2011-11-29 17:28 ` Rick Jones
2011-11-29 16:46 ` Eric Dumazet
2011-11-29 17:47 ` David Miller
2011-11-29 18:31 ` Tom Herbert
2011-12-01 16:50 ` Kirill Smelkov
2011-12-01 18:00 ` David Miller
2011-12-02 11:22 ` Kirill Smelkov
2011-12-02 11:57 ` Eric Dumazet
2011-12-02 12:26 ` Kirill Smelkov
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=1322584889.2684.25.camel@bwh-desktop \
--to=bhutchings@solarflare$(echo .)com \
--cc=dave.taht@gmail$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=eric.dumazet@gmail$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=therbert@google$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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