From: "Tan, Jianfeng" <jianfeng.tan@intel.com>
To: "Tan, Jianfeng" <jianfeng.tan@intel.com>,
Maxime Coquelin <maxime.coquelin@redhat.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH 1/2] virtio: fix resuming traffic with rx vector path
Date: Tue, 13 Feb 2018 00:49:52 +0000 [thread overview]
Message-ID: <ED26CBA2FAD1BF48A8719AEF02201E365143D31F@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <b1a41802-4c87-c76d-a50c-3222df8845ef@intel.com>
Just realize that I forgot to CC dev@dpdk.org.
> -----Original Message-----
> From: Tan, Jianfeng [mailto:jianfeng.tan@intel.com]
> Sent: Monday, February 12, 2018 8:51 PM
> To: Maxime Coquelin
> Subject: Re: [dpdk-dev] [PATCH 1/2] virtio: fix resuming traffic with rx vector
> path
>
>
>
> On 2/9/2018 10:26 PM, Maxime Coquelin wrote:
> > This patch fixes traffic resuming issue seen when using
> > Rx vector path.
>
> A nit: AFAIK, this issue happens after start/stop/start? "traffic
> resuming" seems not accurate.
>
> >
> > Fixes: efc83a1e7fc3 ("net/virtio: fix queue setup consistency")
> >
> > Signed-off-by: Tiwei Bie <tiwei.bie@intel.com>
> > Signed-off-by: Maxime Coquelin <maxime.coquelin@redhat.com>
>
> Besides that,
>
> Reviewed-by: Jianfeng Tan <jianfeng.tan@intel.com>
>
> Thanks for this timely fix!
>
> Thanks,
> Jianfeng
next prev parent reply other threads:[~2018-02-13 0:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-09 14:26 [dpdk-dev] [PATCH 0/2] Vhost & Virtio fixes for -rc4 Maxime Coquelin
2018-02-09 14:26 ` [dpdk-dev] [PATCH 1/2] virtio: fix resuming traffic with rx vector path Maxime Coquelin
2018-02-11 8:02 ` Yao, Lei A
2018-02-12 13:18 ` Olivier Matz
[not found] ` <b1a41802-4c87-c76d-a50c-3222df8845ef@intel.com>
2018-02-13 0:49 ` Tan, Jianfeng [this message]
2018-02-09 14:26 ` [dpdk-dev] [PATCH 2/2] vhost: don't take access_lock on VHOST_USER_RESET_OWNER Maxime Coquelin
2018-02-12 9:40 ` Tiwei Bie
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=ED26CBA2FAD1BF48A8719AEF02201E365143D31F@SHSMSX103.ccr.corp.intel.com \
--to=jianfeng.tan@intel.com \
--cc=dev@dpdk.org \
--cc=maxime.coquelin@redhat.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).