From: "Michael S. Tsirkin" <mst@redhat.com>
To: Jason Wang <jasowang@redhat.com>
Cc: Tonghao Zhang <xiangxia.m.yue@gmail.com>,
makita.toshiaki@lab.ntt.co.jp,
virtualization@lists.linux-foundation.org,
Linux Kernel Network Developers <netdev@vger.kernel.org>
Subject: Re: [PATCH net-next v5 0/4] net: vhost: improve performance when enable busyloop
Date: Wed, 11 Jul 2018 14:59:05 +0300 [thread overview]
Message-ID: <20180711145421-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <4901593f-1d9e-2c47-b963-5fc1f48a1bfe@redhat.com>
On Wed, Jul 11, 2018 at 01:12:59PM +0800, Jason Wang wrote:
>
>
> On 2018年07月11日 11:49, Tonghao Zhang wrote:
> > On Wed, Jul 11, 2018 at 10:56 AM Jason Wang <jasowang@redhat.com> wrote:
> > >
> > >
> > > On 2018年07月04日 12:31, xiangxia.m.yue@gmail.com wrote:
> > > > From: Tonghao Zhang <xiangxia.m.yue@gmail.com>
> > > >
> > > > This patches improve the guest receive and transmit performance.
> > > > On the handle_tx side, we poll the sock receive queue at the same time.
> > > > handle_rx do that in the same way.
> > > >
> > > > For more performance report, see patch 4.
> > > >
> > > > v4 -> v5:
> > > > fix some issues
> > > >
> > > > v3 -> v4:
> > > > fix some issues
> > > >
> > > > v2 -> v3:
> > > > This patches are splited from previous big patch:
> > > > http://patchwork.ozlabs.org/patch/934673/
> > > >
> > > > Tonghao Zhang (4):
> > > > vhost: lock the vqs one by one
> > > > net: vhost: replace magic number of lock annotation
> > > > net: vhost: factor out busy polling logic to vhost_net_busy_poll()
> > > > net: vhost: add rx busy polling in tx path
> > > >
> > > > drivers/vhost/net.c | 108 ++++++++++++++++++++++++++++----------------------
> > > > drivers/vhost/vhost.c | 24 ++++-------
> > > > 2 files changed, 67 insertions(+), 65 deletions(-)
> > > >
> > > Hi, any progress on the new version?
> > >
> > > I plan to send a new series of packed virtqueue support of vhost. If you
> > > plan to send it soon, I can wait. Otherwise, I will send my series.
> > I rebase the codes. and find there is no improvement anymore, the
> > patches of makita may solve the problem. jason you may send your
> > patches, and I will do some research on busypoll.
>
> I see. Maybe you can try some bi-directional traffic.
>
> Btw, lots of optimizations could be done for busy polling. E.g integrating
> with host NAPI busy polling or a 100% busy polling vhost_net. You're welcome
> to work or propose new ideas.
>
> Thanks
It seems clear we do need adaptive polling. The difficulty with NAPI
polling is it can't access guest memory easily. But maybe
get_user_pages on the polled memory+NAPI polling can work.
> >
> > > Thanks
next prev parent reply other threads:[~2018-07-11 12:03 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-04 4:31 [PATCH net-next v5 0/4] net: vhost: improve performance when enable busyloop xiangxia.m.yue
2018-07-04 4:31 ` [PATCH net-next v5 1/4] net: vhost: lock the vqs one by one xiangxia.m.yue
2018-07-04 4:31 ` [PATCH net-next v5 2/4] net: vhost: replace magic number of lock annotation xiangxia.m.yue
2018-07-04 4:31 ` [PATCH net-next v5 3/4] net: vhost: factor out busy polling logic to vhost_net_busy_poll() xiangxia.m.yue
2018-07-04 7:59 ` Toshiaki Makita
2018-07-04 9:18 ` Jason Wang
2018-07-04 9:46 ` Tonghao Zhang
2018-07-04 11:59 ` Jason Wang
2018-07-04 4:31 ` [PATCH net-next v5 4/4] net: vhost: add rx busy polling in tx path xiangxia.m.yue
2018-07-04 6:27 ` [PATCH net-next v5 0/4] net: vhost: improve performance when enable busyloop Jason Wang
2018-07-11 2:56 ` Jason Wang
2018-07-11 3:49 ` Tonghao Zhang
2018-07-11 5:12 ` Jason Wang
2018-07-11 11:59 ` Michael S. Tsirkin [this message]
2018-07-12 3:26 ` Jason Wang
2018-07-12 3:34 ` Michael S. Tsirkin
2018-07-12 5:21 ` Jason Wang
2018-07-12 5:24 ` Michael S. Tsirkin
2018-07-12 5:51 ` Jason Wang
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=20180711145421-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=jasowang@redhat.com \
--cc=makita.toshiaki@lab.ntt.co.jp \
--cc=netdev@vger.kernel.org \
--cc=virtualization@lists.linux-foundation.org \
--cc=xiangxia.m.yue@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).