DPDK patches and discussions
 help / color / mirror / Atom feed
From: Maxime Coquelin <maxime.coquelin@redhat.com>
To: "Pierre Pfister (ppfister)" <ppfister@cisco.com>,
	Yuanhan Liu <yuanhan.liu@linux.intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v2] virtio: enable indirect descriptors feature
Date: Mon, 5 Sep 2016 16:24:13 +0200	[thread overview]
Message-ID: <1dfca8cf-e5ef-1040-8a40-d617ed03e5c0@redhat.com> (raw)
In-Reply-To: <6EFF45F1-172E-4470-B4D7-AED90474DE50@cisco.com>

Thanks Pierre for sending the fix.

Minor comments below:

On 09/05/2016 08:52 AM, Pierre Pfister (ppfister) wrote:
> Indirect descriptors support was disabled by commit 4a92b67151be11,
> presumably by accident as it was correctly supported.
>
> This patch simply adds VIRTIO_RING_F_INDIRECT_DESC back to
> the supported features bit mask, hence enabling the use of
> indirect descriptors when the feature is negociated with the
> device.
>

You should add the below line:
Fixes: 4a92b671 ("virtio: clarify feature bit handling")

Also, maybe we should consider add stable@dpdk.org in cc:,
because the regression was introduced before v16.07 final tag.
But the problem is that all the final validation has been done
without this feature enabled, and it impact quite a few lines of
code in Virtio PMD.

Other than that, you can add:
Reviewed-by: Maxime Coquelin <maxime.coquelin@¶edhat.com>

> Signed-off-by: Pierre Pfister <ppfister@cisco.com>
> ---
>  drivers/net/virtio/virtio_ethdev.h | 1 +
>  1 file changed, 1 insertion(+)
>
> diff --git a/drivers/net/virtio/virtio_ethdev.h b/drivers/net/virtio/virtio_ethdev.h
> index 2ecec6e..31c91a5 100644
> --- a/drivers/net/virtio/virtio_ethdev.h
> +++ b/drivers/net/virtio/virtio_ethdev.h
> @@ -63,6 +63,7 @@
>          1u << VIRTIO_NET_F_CTRL_RX       |     \
>          1u << VIRTIO_NET_F_CTRL_VLAN     |     \
>          1u << VIRTIO_NET_F_MRG_RXBUF     |     \
> +        1u << VIRTIO_RING_F_INDIRECT_DESC |    \
>          1ULL << VIRTIO_F_VERSION_1)
>
>  /*
> --
> 2.7.4 (Apple Git-66)
>


One off-topic question, do you measure some improvement in perfs using
the feature? If yes, could you describe the use-case, and the figures?
I ask because I have implemented TX indirect descriptor in vhost lib
(see http://dpdk.org/dev/patchwork/patch/14797/), and failed to see
some use-case benefiting of it.

Regards,
Maxime

  parent reply	other threads:[~2016-09-05 14:24 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-02 15:55 [dpdk-dev] [PATCH] " Pierre Pfister (ppfister)
2016-09-05  2:20 ` Yuanhan Liu
2016-09-05  6:49   ` Pierre Pfister (ppfister)
2016-09-05  6:49     ` Pierre Pfister (ppfister)
2016-09-05  6:49     ` Pierre Pfister (ppfister)
2016-09-05  6:52   ` [dpdk-dev] [PATCH v2] " Pierre Pfister (ppfister)
2016-09-05  6:52     ` Pierre Pfister (ppfister)
2016-09-05  6:52     ` Pierre Pfister (ppfister)
2016-09-05 14:24     ` Maxime Coquelin [this message]
2016-09-05 21:08       ` Stephen Hemminger
2016-09-06  6:49         ` Pierre Pfister (ppfister)
2016-09-06 15:32           ` Stephen Hemminger
2016-09-06 16:09             ` [dpdk-dev] [PATCH v3] " Pierre Pfister (ppfister)
2016-09-07  2:57               ` Yuanhan Liu
2016-09-06  7:44         ` [dpdk-dev] [PATCH v2] " Maxime Coquelin

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=1dfca8cf-e5ef-1040-8a40-d617ed03e5c0@redhat.com \
    --to=maxime.coquelin@redhat.com \
    --cc=dev@dpdk.org \
    --cc=ppfister@cisco.com \
    --cc=yuanhan.liu@linux.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).