From: David Miller <davem@davemloft.net>
To: arnd@arndb.de
Cc: avi@redhat.com, herbert@gondor.apana.org.au, chrisw@sous-sol.org,
rusty@rustcorp.com.au, kvm@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: copyless virtio net thoughts?
Date: Sat, 07 Feb 2009 19:01:56 -0800 (PST) [thread overview]
Message-ID: <20090207.190156.209878491.davem@davemloft.net> (raw)
In-Reply-To: <200902071256.07513.arnd@arndb.de>
From: Arnd Bergmann <arnd@arndb.de>
Date: Sat, 7 Feb 2009 12:56:06 +0100
> Having the load spread evenly over all guests sounds like a much rarer
> use case.
Totally agreed.
prev parent reply other threads:[~2009-02-08 3:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090205020732.GA27684@sequoia.sous-sol.org>
[not found] ` <498ADD73.3060906@redhat.com>
2009-02-06 5:40 ` copyless virtio net thoughts? Herbert Xu
2009-02-06 8:46 ` Avi Kivity
2009-02-06 9:19 ` Herbert Xu
2009-02-06 14:55 ` Avi Kivity
2009-02-07 11:56 ` Arnd Bergmann
2009-02-08 3:01 ` David Miller [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=20090207.190156.209878491.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=arnd@arndb.de \
--cc=avi@redhat.com \
--cc=chrisw@sous-sol.org \
--cc=herbert@gondor.apana.org.au \
--cc=kvm@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
/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).