netdev - Re: MAX_SKB_FRAGS and GRO

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4B704FAF.4010209@hp.com>
Date:	Mon, 08 Feb 2010 09:53:51 -0800
From:	Rick Jones <rick.jones2@...com>
To:	"Brandeburg, Jesse" <jesse.brandeburg@...el.com>
CC:	Herbert Xu <herbert@...dor.apana.org.au>,
	Anton Blanchard <anton@...ba.org>,
	"Kirsher, Jeffrey T" <jeffrey.t.kirsher@...el.com>,
	"Allan, Bruce W" <bruce.w.allan@...el.com>,
	"Duyck, Alexander H" <alexander.h.duyck@...el.com>,
	"Waskiewicz Jr, Peter P" <peter.p.waskiewicz.jr@...el.com>,
	"Ronciak, John" <john.ronciak@...el.com>,
	"divy@...lsio.com" <divy@...lsio.com>,
	"netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: Re: MAX_SKB_FRAGS and GRO

>>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
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html