All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: David Miller <davem@davemloft.net>
Cc: ffusco@redhat.com, mwdalton@google.com, eric.dumazet@gmail.com,
	netdev@vger.kernel.org, dborkman@redhat.com,
	virtualization@lists.linux-foundation.org, edumazet@google.com
Subject: Re: [PATCH net-next] virtio_net: migrate mergeable rx buffers to page frag allocators
Date: Tue, 29 Oct 2013 21:12:50 +0200	[thread overview]
Message-ID: <20131029191250.GE20848@redhat.com> (raw)
In-Reply-To: <20131028.235721.919284648105056096.davem@davemloft.net>

On Mon, Oct 28, 2013 at 11:57:21PM -0400, David Miller wrote:
> From: Eric Dumazet <eric.dumazet@gmail.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@google.com>
> >> ---
> > 
> > Signed-off-by: Eric Dumazet <edumazet@google.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.

Hmm that was very quick. It *should* fix a bug, great.
But how about we wait for some Tested-by reports that it actually does?

-- 
MST

  reply	other threads:[~2013-10-29 19:12 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-28 22:44 [PATCH net-next] virtio_net: migrate mergeable rx buffers to page frag allocators Michael Dalton
2013-10-28 23:19 ` Eric Dumazet
2013-10-29  3:57   ` David Miller
2013-10-29 19:12     ` Michael S. Tsirkin [this message]
2013-10-29  7:30   ` Daniel Borkmann
2013-10-29  7:30   ` Daniel Borkmann
2013-10-29  1:51 ` Rusty Russell
2013-10-29  1:51 ` Rusty Russell
2013-10-29  6:27 ` Jason Wang
2013-10-29 18:44 ` Eric Northup
2013-10-29 19:05   ` Michael Dalton
2013-10-29 19:05   ` Michael Dalton
2013-10-29 19:17     ` Michael S. Tsirkin
2013-10-30  4:41     ` Jason Wang
2013-10-29 19:05   ` Michael S. Tsirkin
  -- strict thread matches above, loose matches on Subject: below --
2013-10-28 22:44 Michael Dalton

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=20131029191250.GE20848@redhat.com \
    --to=mst@redhat.com \
    --cc=davem@davemloft.net \
    --cc=dborkman@redhat.com \
    --cc=edumazet@google.com \
    --cc=eric.dumazet@gmail.com \
    --cc=ffusco@redhat.com \
    --cc=mwdalton@google.com \
    --cc=netdev@vger.kernel.org \
    --cc=virtualization@lists.linux-foundation.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.