qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@gmail.com>
To: sfeldma@cumulusnetworks.com
Cc: aliguori@us.ibm.com, stephanha@redhat.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] net: increase buffer size to accommodate Jumbo frame pkts over netdev UDP socket
Date: Mon, 18 Mar 2013 17:08:39 +0100	[thread overview]
Message-ID: <20130318160839.GD13065@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <1363392758-15228-1-git-send-email-sfeldma@cumulusnetworks.com>

On Fri, Mar 15, 2013 at 05:12:38PM -0700, sfeldma@cumulusnetworks.com wrote:
> From: Scott Feldman <sfeldma@cumulusnetworks.com>
> 
> Socket buffer sizes were hard-coded to 4K.  Bump this up to 12K to handle typical
> MTU=9000 Jumbo frame pkt.  Ran into this limitation when using -netdev UDP sockets
> to connect VM-to-VM, where VM interface is configure with MTU=9000.  Using
> virtio_net NIC model.  Test is simple: ping -M do -s 8500 <target>.  This test
> will attempt to ping with unfragmented packet of given size.  Without patch,
> size is limited to < 4K (minus protocol hdrs).  With patch, ping test works
> with pkt size up to 9000 (again, minus protocol hdrs).
> 
> Signed-off-by: Scott Feldman <sfeldma@cumulusnetworks.com>
> ---
>  net/net.c    |    2 +-
>  net/socket.c |    4 ++--
>  2 files changed, 3 insertions(+), 3 deletions(-)

grep reveals that VDE is limited in a similar way.  tap-win32 may be
affected too.

I noticed that Linux tap goes straight for:
net/tap.c:#define TAP_BUFSIZE (4096 + 65536)

The 4096 is reserved for network/virtio headers.

Please move TAP_BUFSIZE to include/net/net.h and rename it to
NET_BUFSIZE.  Then socket, vde, and tap-win32 can use it.

Stefan

      reply	other threads:[~2013-03-18 16:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-16  0:12 [Qemu-devel] [PATCH] net: increase buffer size to accommodate Jumbo frame pkts over netdev UDP socket sfeldma
2013-03-18 16:08 ` Stefan Hajnoczi [this message]

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=20130318160839.GD13065@stefanha-thinkpad.redhat.com \
    --to=stefanha@gmail.com \
    --cc=aliguori@us.ibm.com \
    --cc=qemu-devel@nongnu.org \
    --cc=sfeldma@cumulusnetworks.com \
    --cc=stephanha@redhat.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).