From: "Michael S. Tsirkin" <mst@redhat.com>
To: Robert Vineyard <vineyard@tuffmail.com>
Cc: xiaohui.xin@intel.com, kvm@vger.kernel.org,
netdev@vger.kernel.org,
"Peter Huang(Peng)" <peter.huangpeng@huawei.com>,
virtualization@lists.linux-foundation.org, avi@redhat.com,
Stephen Hemminger <shemminger@vyatta.com>
Subject: Re: [Question]About KVM network zero-copy feature!
Date: Sun, 12 Aug 2012 12:37:31 +0300 [thread overview]
Message-ID: <20120812093730.GD1421@redhat.com> (raw)
In-Reply-To: <5026FC04.6080108@tuffmail.com>
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.
> The Release Notes for RHEL 6.2 (originally published on 12/06/2011)
> also specifically mention macvtap/vhost zero-copy capabilities as
> being included as a Technology Preview:
>
> http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html/6.2_Release_Notes/virtualization.html
>
> Since I've been unable to find much information on the current
> status of this development, can anyone confirm if this functionality
> is still in the works? If so, is there any planned ETA?
>
> Thanks,
> Robert Vineyard
I think this means TX.
--
MST
WARNING: multiple messages have this Message-ID (diff)
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Robert Vineyard <vineyard@tuffmail.com>
Cc: xiaohui.xin@intel.com, kvm@vger.kernel.org,
netdev@vger.kernel.org,
"Peter Huang\(Peng\)" <peter.huangpeng@huawei.com>,
virtualization@lists.linux-foundation.org, avi@redhat.com,
Stephen Hemminger <shemminger@vyatta.com>
Subject: Re: [Question]About KVM network zero-copy feature!
Date: Sun, 12 Aug 2012 12:37:31 +0300 [thread overview]
Message-ID: <20120812093730.GD1421@redhat.com> (raw)
In-Reply-To: <5026FC04.6080108@tuffmail.com>
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.
> The Release Notes for RHEL 6.2 (originally published on 12/06/2011)
> also specifically mention macvtap/vhost zero-copy capabilities as
> being included as a Technology Preview:
>
> http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html/6.2_Release_Notes/virtualization.html
>
> Since I've been unable to find much information on the current
> status of this development, can anyone confirm if this functionality
> is still in the works? If so, is there any planned ETA?
>
> Thanks,
> Robert Vineyard
I think this means TX.
--
MST
next prev parent reply other threads:[~2012-08-12 9:37 UTC|newest]
Thread overview: 15+ 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-11 21:54 ` Robert Vineyard
2012-08-12 0:42 ` Robert Vineyard
2012-08-12 0:42 ` Robert Vineyard
2012-08-12 9:37 ` Michael S. Tsirkin [this message]
2012-08-12 9:37 ` Michael S. Tsirkin
2012-08-13 1:24 ` Peter Huang(Peng)
2012-08-13 7:18 ` Michael S. Tsirkin
2012-08-13 3:45 ` Robert Vineyard
2012-08-13 3:45 ` Robert Vineyard
2012-08-13 5:59 ` Robert Vineyard
2012-08-13 5:59 ` Robert Vineyard
-- strict thread matches above, loose matches on Subject: below --
2012-08-10 3:34 Peter Huang(Peng)
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=20120812093730.GD1421@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=vineyard@tuffmail.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 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.