From: Maxime Coquelin <maxime.coquelin@redhat.com>
To: Cheng Jiang <Cheng1.jiang@intel.com>,
tiwei.bie@intel.com, zhihong.wang@intel.com, yong.liu@intel.com
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v4] net/virtio: packed ring notification data feature support
Date: Mon, 13 Jan 2020 16:02:56 +0100 [thread overview]
Message-ID: <2ee924fd-a041-be2a-ca8a-1e48f6234cb9@redhat.com> (raw)
In-Reply-To: <20200113033133.55731-1-Cheng1.jiang@intel.com>
On 1/13/20 4:31 AM, Cheng Jiang wrote:
> This patch supports the feature that the driver passes extra data
> (besides identifying the virtqueue) in its device notifications,
> expanding the notifications to include the avail index and avail
> wrap counter.
>
> Signed-off-by: Cheng Jiang <Cheng1.jiang@intel.com>
> ---
>
> v4:
> * Replaced used_wrap_counter with avail_wrap_counter.
>
> v3:
> * Modified the commit log to make it more detailed.
> * Modified the shift mode of notify_data to make it more intuitive.
>
> v2:
> * Removed rte_unused attribute in *hw.
> * Added some comments on notify_data.
>
> drivers/net/virtio/virtio_ethdev.h | 3 ++-
> drivers/net/virtio/virtio_pci.c | 29 +++++++++++++++++++++++++++--
> drivers/net/virtio/virtio_pci.h | 6 ++++++
> 3 files changed, 35 insertions(+), 3 deletions(-)
>
Reviewed-by: Maxime Coquelin <maxime.coquelin@redhat.com>
Thanks,
Maxime
next prev parent reply other threads:[~2020-01-13 15:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-04 15:03 [dpdk-dev] [DPDK] " Cheng Jiang
2019-12-09 1:59 ` Liu, Yong
2019-12-12 9:08 ` Jiang, Cheng1
2019-12-18 8:17 ` [dpdk-dev] [PATCH v2] " Cheng Jiang
2019-12-18 9:51 ` Gavin Hu
2019-12-23 2:34 ` Jiang, Cheng1
2019-12-23 5:15 ` [dpdk-dev] [PATCH v3] " Cheng Jiang
2019-12-23 6:49 ` Gavin Hu
2020-01-13 3:31 ` [dpdk-dev] [PATCH v4] " Cheng Jiang
2020-01-13 15:02 ` Maxime Coquelin [this message]
2020-01-15 11:18 ` Maxime Coquelin
2020-01-09 7:29 ` [dpdk-dev] [DPDK] " Liu, Yong
2020-01-13 2:57 ` Jiang, Cheng1
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=2ee924fd-a041-be2a-ca8a-1e48f6234cb9@redhat.com \
--to=maxime.coquelin@redhat.com \
--cc=Cheng1.jiang@intel.com \
--cc=dev@dpdk.org \
--cc=tiwei.bie@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).