From: Maxime Coquelin <maxime.coquelin@redhat.com>
To: Marvin Liu <yong.liu@intel.com>,
xiaolong.ye@intel.com, zhihong.wang@intel.com
Cc: dev@dpdk.org, stable@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] vhost: fix shadowed descs not flushed
Date: Fri, 17 Apr 2020 19:08:36 +0200 [thread overview]
Message-ID: <e321a89d-69f6-195c-d349-33565ba4dc4b@redhat.com> (raw)
In-Reply-To: <20200417011609.29971-1-yong.liu@intel.com>
On 4/17/20 3:16 AM, Marvin Liu wrote:
> When ring size or enqueue packets not aligned with batch number, it is
> possible that descs update still kept in shadowed used structure when
> batched enqueue. Fix this issue by flushing remained shadowed used descs
> before batch flush.
>
> Fixes: f41516c309d ("vhost: flush batched enqueue descs directly")
> Cc: stable@dpdk.org
>
> Signed-off-by: Marvin Liu <yong.liu@intel.com>
Applied to dpdk-next-virtio/master
Thanks,
Maxime
prev parent reply other threads:[~2020-04-17 17:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-17 1:16 Marvin Liu
2020-04-17 15:21 ` Maxime Coquelin
2020-04-17 17:08 ` 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=e321a89d-69f6-195c-d349-33565ba4dc4b@redhat.com \
--to=maxime.coquelin@redhat.com \
--cc=dev@dpdk.org \
--cc=stable@dpdk.org \
--cc=xiaolong.ye@intel.com \
--cc=yong.liu@intel.com \
--cc=zhihong.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).