From: Yuanhan Liu <yliu@fridaylinux.org>
To: "Yao, Lei A" <lei.a.yao@intel.com>
Cc: "Chen, Junjie J" <junjie.j.chen@intel.com>,
"maxime.coquelin@redhat.com" <maxime.coquelin@redhat.com>,
"Wang, Xiao W" <xiao.w.wang@intel.com>,
"Bie, Tiwei" <tiwei.bie@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [PATCH v7] vhost: support virtqueue interrupt/notification suppression
Date: Tue, 9 Jan 2018 20:58:58 +0800 [thread overview]
Message-ID: <20180109125858.GI29540@yliu-mob> (raw)
In-Reply-To: <2DBBFF226F7CF64BAFCA79B681719D953A3220A3@shsmsx102.ccr.corp.intel.com>
On Tue, Jan 09, 2018 at 07:34:17AM +0000, Yao, Lei A wrote:
>
>
> > -----Original Message-----
> > From: Chen, Junjie J
> > Sent: Tuesday, January 9, 2018 7:04 PM
> > To: yliu@fridaylinux.org; maxime.coquelin@redhat.com; Wang, Xiao W
> > <xiao.w.wang@intel.com>; Bie, Tiwei <tiwei.bie@intel.com>; Yao, Lei A
> > <lei.a.yao@intel.com>
> > Cc: dev@dpdk.org; Chen, Junjie J <junjie.j.chen@intel.com>
> > Subject: [PATCH v7] vhost: support virtqueue interrupt/notification
> > suppression
> >
> > The driver can suppress interrupt when VIRTIO_F_EVENT_IDX feature bit is
> > negotiated. The driver set vring flags to 0, and MAY use used_event in
> > available ring to advise device interrupt util reach an index specified
> > by used_event. The device ignore the lower bit of vring flags, and send
> > an interrupt when index reach used_event.
> >
> > The device can suppress notification in a manner analogous to the ways
> > driver suppress interrupt. The device manipulates flags or avail_event in
> > the used ring in the same way the driver manipulates flags or used_event in
> > available ring.
> >
> > Signed-off-by: Junjie Chen <junjie.j.chen@intel.com>
> Tested-by: Lei Yao <lei.a.yao@intel.com>
Applied to dpdk-next-virtio.
Thanks.
--yliu
> VM2VM Iperf test has been executed with virtio-net driver after apply this patch.
> No performance drop.
> CPU: Intel(R) Xeon(R) CPU E5-2699 v4 @ 2.20GHz
> Host OS: Ubuntu 16.04
> Guest OS: Ubuntu 16.04
> Kernel: 4.4.0
next prev parent reply other threads:[~2018-01-09 12:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-28 11:02 [PATCH v4] vhost: support virtqueue interrupt/notification suppression junjie.j.chen
2017-12-23 16:55 ` [PATCH v5] " Junjie Chen
2017-12-26 8:03 ` Wang, Xiao W
2017-12-26 17:43 ` [PATCH v6] " Junjie Chen
2018-01-05 5:25 ` Wang, Xiao W
2018-01-08 14:06 ` Yuanhan Liu
2018-01-09 2:12 ` Chen, Junjie J
2018-01-09 2:29 ` Yuanhan Liu
2018-01-09 11:03 ` [PATCH v7] " Junjie Chen
2018-01-09 7:34 ` Yao, Lei A
2018-01-09 12:58 ` Yuanhan Liu [this message]
2018-01-09 8:56 ` Maxime Coquelin
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=20180109125858.GI29540@yliu-mob \
--to=yliu@fridaylinux.org \
--cc=dev@dpdk.org \
--cc=junjie.j.chen@intel.com \
--cc=lei.a.yao@intel.com \
--cc=maxime.coquelin@redhat.com \
--cc=tiwei.bie@intel.com \
--cc=xiao.w.wang@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.