From: "Michael S. Tsirkin" <mst@redhat.com>
To: "Peter Huang(Peng)" <peter.huangpeng@huawei.com>
Cc: xiaohui.xin@intel.com, kvm@vger.kernel.org,
netdev@vger.kernel.org,
virtualization@lists.linux-foundation.org, avi@redhat.com,
Stephen Hemminger <shemminger@vyatta.com>
Subject: Re: [Question]About KVM network zero-copy feature!
Date: Mon, 13 Aug 2012 10:18:44 +0300 [thread overview]
Message-ID: <20120813071843.GC14081@redhat.com> (raw)
In-Reply-To: <50285766.50307@huawei.com>
Last patchset version was this:
[PATCH v16 00/17] Provide a zero-copy method on KVM virtio-net
IIRC the main issue was the need to integrate the patchset with
macvtap (as opposed to using a separate device).
On Mon, Aug 13, 2012 at 09:24:54AM +0800, Peter Huang(Peng) wrote:
> Hi, Michael
>
> IIt will be usefull if we can implement rx zero-copy, could you give
> me some help if you know some technical details or some
> references on the internet?
>
> I am wondering may be I can take a deep look on it first then decide
> if I can take it over or not.
>
> Thanks a lot.
>
> On 2012/8/12 17:37, Michael S. Tsirkin wrote:
> > On Sat, Aug 11, 2012 at 08:42:44PM -0400, Robert Vineyard wrote:
> >> (adding Xin Xiaohui to the conversation for comment)
> >>
> >> According to the NetworkingTodo page on the KVM wiki, zero-copy RX
> >> for macvtap is in fact on the roadmap, assigned to Xin:
> >>
> >> http://www.linux-kvm.org/page/NetworkingTodo
> > AFAIK Xin left Intel and is not working on it.
> > Contributions are welcome.
> >
next prev parent reply other threads:[~2012-08-13 7:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-10 3:34 [Question]About KVM network zero-copy feature! Peter Huang(Peng)
2012-08-11 20:55 ` Stephen Hemminger
2012-08-11 21:54 ` Robert Vineyard
2012-08-12 0:42 ` Robert Vineyard
2012-08-12 9:37 ` Michael S. Tsirkin
2012-08-13 1:24 ` Peter Huang(Peng)
2012-08-13 7:18 ` Michael S. Tsirkin [this message]
2012-08-13 3:45 ` Robert Vineyard
2012-08-13 5:59 ` Robert Vineyard
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=20120813071843.GC14081@redhat.com \
--to=mst@redhat.com \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=peter.huangpeng@huawei.com \
--cc=shemminger@vyatta.com \
--cc=virtualization@lists.linux-foundation.org \
--cc=xiaohui.xin@intel.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).