From: Rick Jones <rick.jones2@hp.com>
To: "Brandeburg, Jesse" <jesse.brandeburg@intel.com>
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
Anton Blanchard <anton@samba.org>,
"Kirsher, Jeffrey T" <jeffrey.t.kirsher@intel.com>,
"Allan, Bruce W" <bruce.w.allan@intel.com>,
"Duyck, Alexander H" <alexander.h.duyck@intel.com>,
"Waskiewicz Jr, Peter P" <peter.p.waskiewicz.jr@intel.com>,
"Ronciak, John" <john.ronciak@intel.com>,
"divy@chelsio.com" <divy@chelsio.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: MAX_SKB_FRAGS and GRO
Date: Mon, 08 Feb 2010 09:53:51 -0800 [thread overview]
Message-ID: <4B704FAF.4010209@hp.com> (raw)
In-Reply-To: <alpine.WNT.2.00.1002080936180.6892@jbrandeb-desk1.amr.corp.intel.com>
>>First of all this isn't GRO, but RSC. With GRO we impose extra
>>restrictions on what packets can be merged while RSC is more
>>permissive.
>
>
> Herbert is right. Just for clarity lets not call it "hardware GRO" but
> instead just call it RSC or hardware RSC (receive side coalescing)
I'll paint a stripe on the bikeshed and suggest something even more
explicit - if it is the hardware, how about HRC (Hardware Receive
Coalescing) or NRC (Nic Receive Coalescing).
rick jones
next prev parent reply other threads:[~2010-02-08 17:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-08 10:03 MAX_SKB_FRAGS and GRO Anton Blanchard
2010-02-08 12:47 ` Herbert Xu
2010-02-08 17:35 ` Duyck, Alexander H
2010-02-08 17:41 ` Brandeburg, Jesse
2010-02-08 17:53 ` Rick Jones [this message]
2010-02-08 19:12 ` Ben Hutchings
2010-02-08 22:21 ` 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=4B704FAF.4010209@hp.com \
--to=rick.jones2@hp.com \
--cc=alexander.h.duyck@intel.com \
--cc=anton@samba.org \
--cc=bruce.w.allan@intel.com \
--cc=divy@chelsio.com \
--cc=herbert@gondor.apana.org.au \
--cc=jeffrey.t.kirsher@intel.com \
--cc=jesse.brandeburg@intel.com \
--cc=john.ronciak@intel.com \
--cc=netdev@vger.kernel.org \
--cc=peter.p.waskiewicz.jr@intel.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).