netdev - Re: [Xen-devel] [PATCH net-next] xen-netfront: convert to GRO API and advertise this feature

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: <523E8E3B.3050805@redhat.com>
Date:	Sun, 22 Sep 2013 14:29:15 +0800
From:	Jason Wang <jasowang@...hat.com>
To:	Wei Liu <wei.liu2@...rix.com>, netdev@...r.kernel.org
CC:	Anirban Chakraborty <abchak@...iper.net>,
	Ian Campbell <ian.campbell@...rix.com>, xen-devel@...ts.xen.org
Subject: Re: [Xen-devel] [PATCH net-next] xen-netfront: convert to GRO API
 and advertise this feature

On 09/22/2013 12:05 AM, Wei Liu wrote:
> Anirban was seeing netfront received MTU size packets, which downgraded
> throughput. The following patch makes netfront use GRO API which
> improves throughput for that case.
>
> Signed-off-by: Wei Liu <wei.liu2@...rix.com>
> Signed-off-by: Anirban Chakraborty <abchak@...iper.net>
> Cc: Ian Campbell <ian.campbell@...rix.com>

Maybe a dumb question: doesn't Xen depends on the driver of host card to
do GRO and pass it to netfront? What the case that netfront can receive
a MTU size packet, for a card that does not support GRO in host? Doing
GRO twice may introduce extra overheads.

Thanks
--
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