netdev - Re: [PATCH net-next] virtio_net: migrate mergeable rx buffers to page frag allocators

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]

Date:	Mon, 28 Oct 2013 23:57:21 -0400 (EDT)
From:	David Miller <davem@...emloft.net>
To:	eric.dumazet@...il.com
Cc:	mwdalton@...gle.com, netdev@...r.kernel.org, edumazet@...gle.com,
	rusty@...tcorp.com.au, mst@...hat.com, dborkman@...hat.com,
	virtualization@...ts.linux-foundation.org, ffusco@...hat.com
Subject: Re: [PATCH net-next] virtio_net: migrate mergeable rx buffers to
 page frag allocators

From: Eric Dumazet <eric.dumazet@...il.com>
Date: Mon, 28 Oct 2013 16:19:49 -0700

> On Mon, 2013-10-28 at 15:44 -0700, Michael Dalton wrote:
>> The virtio_net driver's mergeable receive buffer allocator
>> uses 4KB packet buffers. For MTU-sized traffic, SKB truesize
>> is > 4KB but only ~1500 bytes of the buffer is used to store
>> packet data, reducing the effective TCP window size
>> substantially. This patch addresses the performance concerns
>> with mergeable receive buffers by allocating MTU-sized packet
>> buffers using page frag allocators. If more than MAX_SKB_FRAGS
>> buffers are needed, the SKB frag_list is used.
>> 
>> Signed-off-by: Michael Dalton <mwdalton@...gle.com>
>> ---
> 
> Signed-off-by: Eric Dumazet <edumazet@...gle.com>
> 
> Daniel & Francesco, this should address the performance problem you
> tried to address with ("tcp: rcvbuf autotuning improvements") 
> 
> ( http://www.spinics.net/lists/netdev/msg252642.html )

Applied, thanks everyone.
--
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