From: Eric Dumazet <eric.dumazet@gmail.com>
To: Jesper Dangaard Brouer <hawk@comx.dk>
Cc: Van Jacobson <van@parc.com>,
bloat-devel@lists.bufferbloat.net, herbert@gondor.apana.org.au,
bloat@lists.bufferbloat.net
Subject: Re: GSO (was: Please enter issues into the issue tracker - Issue system organisation needed)
Date: Fri, 25 Feb 2011 17:19:22 +0100 [thread overview]
Message-ID: <1298650762.2659.74.camel@edumazet-laptop> (raw)
In-Reply-To: <1298648937.28000.41.camel@traveldev.cxnet.dk>
Le vendredi 25 février 2011 à 16:48 +0100, Jesper Dangaard Brouer a
écrit :
> > > I'm wondering if LRO (Large-Receive-Offload) affect you, when you are
> > > using SFQ on ingress?
> > >
> > >
> >
> > GRO/LRO can have an impact, for sure. But most 'current' kernels dont
> > have GRO/LRO by default. I mean, kernels in use by 2-3 years old
> > distros.
>
> Hmm, are you sure?
> The speed test server runs Debian Lenny and kernel 2.6.26-2-686, and had
> GSO enabled...
I am sure about GRO (Receive) side. It was mostly disabled on old
kernels. Only very recently we switched it ON.
next prev parent reply other threads:[~2011-02-25 16:19 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-24 14:19 Please enter issues into the issue tracker - Issue system organisation needed Jim Gettys
2011-02-24 15:00 ` [Bloat] " Fred Baker
2011-02-24 16:32 ` Jim Gettys
2011-02-24 17:08 ` Eric Dumazet
2011-02-24 18:31 ` Dave Täht
2011-02-24 19:29 ` Eric Dumazet
2011-02-25 11:21 ` GSO (was: Please enter issues into the issue tracker - Issue system organisation needed) Jesper Dangaard Brouer
2011-02-25 11:54 ` Eric Dumazet
2011-02-25 15:48 ` Jesper Dangaard Brouer
2011-02-25 16:19 ` Eric Dumazet [this message]
2011-02-25 16:33 ` Eric Dumazet
2011-02-25 17:15 ` Jesper Dangaard Brouer
2011-02-26 2:41 ` GSO Dave Täht
2011-03-02 8:30 ` GSO Jesper Dangaard Brouer
2011-03-04 2:23 ` GSO Dave Täht
2011-02-24 23:15 ` debloat-testing: Kitten not eaten - was Re: [Bloat] Please enter issues into the issue tracker - Issue system organisation needed Jim Gettys
2011-02-24 23:18 ` Dave Täht
2011-02-24 23:31 ` Jim Gettys
2011-02-25 15:40 ` John W. Linville
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=1298650762.2659.74.camel@edumazet-laptop \
--to=eric.dumazet@gmail.com \
--cc=bloat-devel@lists.bufferbloat.net \
--cc=bloat@lists.bufferbloat.net \
--cc=hawk@comx.dk \
--cc=herbert@gondor.apana.org.au \
--cc=van@parc.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