patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Maxime Coquelin <maxime.coquelin@redhat.com>
To: Jiayu Hu <jiayu.hu@intel.com>, dev@dpdk.org
Cc: tiwei.bie@intel.com, yinan.wang@intel.com, stable@dpdk.org
Subject: Re: [dpdk-stable] [PATCH v2] vhost: fix interrupt suppression for the split ring
Date: Wed, 20 Mar 2019 08:36:04 +0100	[thread overview]
Message-ID: <bd333017-1918-2da6-d802-91caf7373fbd@redhat.com> (raw)
In-Reply-To: <1552804712-9973-1-git-send-email-jiayu.hu@intel.com>



On 3/17/19 7:38 AM, Jiayu Hu wrote:
> The VIRTIO_RING_F_EVENT_IDX feature of split ring might
> be broken, as the value of signalled_used is invalid
> after live migration, start up and virtio driver reload.
> This patch fixes it by using signalled_used_valid.
> 
> In addition, this patch makes the VIRTIO_RING_F_EVENT_IDX
> implementation of split ring match kernel backend to suppress
> more interrupts.
> 
> Fixes: e37ff954405a ("vhost: support virtqueue interrupt/notification suppression")
> Cc:stable@dpdk.org
> 
> Signed-off-by: Jiayu Hu<jiayu.hu@intel.com>
> ---
> change in v2:
> - fix virtio-net driver reload
> 
>   lib/librte_vhost/vhost.h      | 12 ++++++++----
>   lib/librte_vhost/vhost_user.c |  2 ++
>   2 files changed, 10 insertions(+), 4 deletions(-)


Applied to dpdk-next-virtio/master branch.

Thanks,
Maxime

      parent reply	other threads:[~2019-03-20  7:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-22  8:13 [dpdk-stable] [PATCH] " Jiayu Hu
2019-02-25  7:06 ` Tiwei Bie
2019-02-27  5:38   ` Hu, Jiayu
2019-02-27 10:55     ` Tiwei Bie
2019-03-17  6:38 ` [dpdk-stable] [PATCH v2] " Jiayu Hu
2019-03-20  0:45   ` Wang, Yinan
2019-03-20  4:56   ` Tiwei Bie
2019-03-20  7:36   ` Maxime Coquelin [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=bd333017-1918-2da6-d802-91caf7373fbd@redhat.com \
    --to=maxime.coquelin@redhat.com \
    --cc=dev@dpdk.org \
    --cc=jiayu.hu@intel.com \
    --cc=stable@dpdk.org \
    --cc=tiwei.bie@intel.com \
    --cc=yinan.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 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).