From: "Michael S. Tsirkin" <mst@redhat.com>
To: David Miller <davem@davemloft.net>
Cc: jasowang@redhat.com, kvm@vger.kernel.org,
virtualization@lists.linux-foundation.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
RAPOPORT@il.ibm.com, yang.zhang.wz@gmail.com
Subject: Re: [PATCH V3 0/3] basic busy polling support for vhost_net
Date: Sun, 28 Feb 2016 11:12:55 +0200 [thread overview]
Message-ID: <20160228111248-mutt-send-email-mst@redhat.com> (raw)
In-Reply-To: <20160226.114502.171815325392990783.davem@davemloft.net>
On Fri, Feb 26, 2016 at 11:45:02AM -0500, David Miller wrote:
> From: Jason Wang <jasowang@redhat.com>
> Date: Fri, 26 Feb 2016 16:42:41 +0800
>
> > This series tries to add basic busy polling for vhost net. The idea is
> > simple: at the end of tx/rx processing, busy polling for new tx added
> > descriptor and rx receive socket for a while. The maximum number of
> > time (in us) could be spent on busy polling was specified ioctl.
>
> I'm assuming this will go through Michael's tree.
Definitely.
prev parent reply other threads:[~2016-02-28 9:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-26 8:42 [PATCH V3 0/3] basic busy polling support for vhost_net Jason Wang
2016-02-26 8:42 ` [PATCH V3 1/3] vhost: introduce vhost_has_work() Jason Wang
2016-02-26 8:42 ` [PATCH V3 2/3] vhost: introduce vhost_vq_avail_empty() Jason Wang
2016-02-26 8:42 ` [PATCH V3 3/3] vhost_net: basic polling support Jason Wang
2016-02-28 14:09 ` Michael S. Tsirkin
2016-02-29 5:15 ` Jason Wang
2016-02-29 9:03 ` Michael S. Tsirkin
2016-02-28 21:56 ` Christian Borntraeger
2016-02-29 5:17 ` Jason Wang
2016-02-26 16:45 ` [PATCH V3 0/3] basic busy polling support for vhost_net David Miller
2016-02-28 9:12 ` Michael S. Tsirkin [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=20160228111248-mutt-send-email-mst@redhat.com \
--to=mst@redhat.com \
--cc=RAPOPORT@il.ibm.com \
--cc=davem@davemloft.net \
--cc=jasowang@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=virtualization@lists.linux-foundation.org \
--cc=yang.zhang.wz@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).