From: Yongseok Koh <yskoh@mellanox.com>
To: Tiwei Bie <tiwei.bie@intel.com>
Cc: "stable@dpdk.org" <stable@dpdk.org>,
"maxime.coquelin@redhat.com" <maxime.coquelin@redhat.com>,
"zhihong.wang@intel.com" <zhihong.wang@intel.com>
Subject: Re: [dpdk-stable] [PATCH 17.11] net/virtio: add barrier in interrupt enable
Date: Mon, 12 Aug 2019 18:49:52 +0000 [thread overview]
Message-ID: <80CEC349-D88C-4481-87DD-CD2C1F0F7052@mellanox.com> (raw)
In-Reply-To: <20190809110904.31669-1-tiwei.bie@intel.com>
> On Aug 9, 2019, at 4:09 AM, Tiwei Bie <tiwei.bie@intel.com> wrote:
>
> [ backported from upstream commit 8f66bc4ac3c0d4a11252d860f495abd806aa871f ]
>
> Typically, after enabling Rx interrupt, a check should be done
> to make sure that there is no new incoming packets before going
> to sleep. So a barrier is needed to make sure that any following
> check won't happen before the interrupt is actually enabled.
>
> Fixes: c056be239db5 ("net/virtio: add Rx interrupt enable/disable functions")
>
> Signed-off-by: Tiwei Bie <tiwei.bie@intel.com>
> Reviewed-by: Maxime Coquelin <maxime.coquelin@redhat.com>
> ---
applied to stable/17.11
thanks,
Yongseok
> drivers/net/virtio/virtio_ethdev.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/net/virtio/virtio_ethdev.c b/drivers/net/virtio/virtio_ethdev.c
> index b3e55ff3b..1bdf37e4b 100644
> --- a/drivers/net/virtio/virtio_ethdev.c
> +++ b/drivers/net/virtio/virtio_ethdev.c
> @@ -739,6 +739,7 @@ virtio_dev_rx_queue_intr_enable(struct rte_eth_dev *dev, uint16_t queue_id)
> struct virtqueue *vq = rxvq->vq;
>
> virtqueue_enable_intr(vq);
> + virtio_mb();
> return 0;
> }
>
> --
> 2.17.1
>
prev parent reply other threads:[~2019-08-12 18:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-09 11:09 Tiwei Bie
2019-08-12 18:49 ` Yongseok Koh [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=80CEC349-D88C-4481-87DD-CD2C1F0F7052@mellanox.com \
--to=yskoh@mellanox.com \
--cc=maxime.coquelin@redhat.com \
--cc=stable@dpdk.org \
--cc=tiwei.bie@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).