From: "Michael S. Tsirkin" <mst@redhat.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: Luke Gorrie <luke@snabb.co>,
"snabb-devel@googlegroups.com" <snabb-devel@googlegroups.com>,
qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [snabb-devel] Re: Make virtio-net.c ring size configurable?
Date: Thu, 27 Feb 2014 16:49:49 +0200 [thread overview]
Message-ID: <20140227144949.GA21933@redhat.com> (raw)
In-Reply-To: <20140227141744.GG30387@stefanha-thinkpad.redhat.com>
On Thu, Feb 27, 2014 at 03:17:44PM +0100, Stefan Hajnoczi wrote:
> On Mon, Feb 24, 2014 at 05:14:04PM +0100, Luke Gorrie wrote:
> > On 24 February 2014 16:20, Stefan Hajnoczi <stefanha@gmail.com> wrote:
> >
> > > Do you want the 1:1 mapping to achieve best performance or just to
> > > simplify the coding?
> > >
> >
> > We want to keep the real-time constraints on the data plane comfortable.
> >
> > The question I ask myself is: How long can I buffer packets during
> > processing before something is dropped?
> >
> > 256 buffers can be consumed in 17 microseconds on a 10G interface.
>
> This is a good point. The virtio-net vring is too small at 256 buffers
> for workloads that want to send/receive small packets at 10 Gbit/s line
> rate. (Minimum UDP packet size is 52 bytes!)
>
> Michael: Luke has asked to increase the virtio-net virtqueue size.
> Thoughts?
>
> Stefan
Heh you want to increase the bufferbloat?
Each buffer pointer takes up 16 bytes so we are using order-2
allocations as it is, anything more and it'll start to fail
if hotplug happens long after boot.
AFAIK baremetal does not push line rate with 1 byte payload
either.
--
MST
next prev parent reply other threads:[~2014-02-27 14:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-14 13:43 [Qemu-devel] Make virtio-net.c ring size configurable? Luke Gorrie
2014-02-14 19:34 ` Mario Smarduch
2014-02-24 15:20 ` Stefan Hajnoczi
2014-02-24 16:14 ` [Qemu-devel] [snabb-devel] " Luke Gorrie
2014-02-27 14:17 ` Stefan Hajnoczi
2014-02-27 14:49 ` Michael S. Tsirkin [this message]
2014-02-28 8:02 ` Luke Gorrie
2014-02-24 19:16 ` Luke Gorrie
2016-05-12 17:38 ` [Qemu-devel] " xchenum
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=20140227144949.GA21933@redhat.com \
--to=mst@redhat.com \
--cc=luke@snabb.co \
--cc=qemu-devel@nongnu.org \
--cc=snabb-devel@googlegroups.com \
--cc=stefanha@gmail.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).