From: Maxime Coquelin <maxime.coquelin@redhat.com>
To: Xuan Ding <xuan.ding@intel.com>, chenbo.xia@intel.com
Cc: dev@dpdk.org, jiayu.hu@intel.com, yinan.wang@intel.com,
stable@dpdk.org, yong.liu@intel.com
Subject: Re: [dpdk-dev] [PATCH] net/virtio: fix indirect descriptors reconnection
Date: Thu, 23 Sep 2021 10:15:54 +0200 [thread overview]
Message-ID: <38c47e02-408f-d06d-5d96-26824239fa30@redhat.com> (raw)
In-Reply-To: <20210819053518.106296-1-xuan.ding@intel.com>
Hi Xuan,
On 8/19/21 07:35, Xuan Ding wrote:
> Since packed indirect descriptors are added and initialized when
> initializing vring, the reconnection path also needs to be considered.
>
> Fixes: 381f39ebb78a ("net/virtio: fix packed ring indirect descricptors setup")
> Cc: stable@dpdk.org
> Cc: yong.liu@intel.com
>
> Signed-off-by: Xuan Ding <xuan.ding@intel.com>
> ---
> drivers/net/virtio/virtqueue.c | 14 ++++++++++++++
> 1 file changed, 14 insertions(+)
>
> diff --git a/drivers/net/virtio/virtqueue.c b/drivers/net/virtio/virtqueue.c
> index 1f9af3c31b..47229f35c4 100644
> --- a/drivers/net/virtio/virtqueue.c
> +++ b/drivers/net/virtio/virtqueue.c
> @@ -208,6 +208,20 @@ virtqueue_txvq_reset_packed(struct virtqueue *vq)
> rte_pktmbuf_free(dxp->cookie);
> dxp->cookie = NULL;
> }
It makes me think we might save quite some bytes by not allocating
indirect descriptors when feature is not negotiated, but it might have
a cost in term of performance.
> +
> + struct virtio_tx_region *txr;
Don't mix declarations within code.
> + txr = txvq->virtio_net_hdr_mz->addr;
> + /* first indirect descriptor is always the tx header */
> + struct vring_packed_desc *start_dp =
> + txr[desc_idx].tx_packed_indir;
Ditto.
> + vring_desc_init_indirect_packed(start_dp,
> + RTE_DIM(txr[desc_idx].tx_packed_indir));
> + start_dp->addr = txvq->virtio_net_hdr_mem
> + + desc_idx * sizeof(*txr)
> + + offsetof(struct virtio_tx_region,
> + tx_hdr);
> + start_dp->len = vq->hw->vtnet_hdr_size;
> +
> }
>
> vring_desc_init_packed(vq, size);
>
Thanks,
Maxime
next prev parent reply other threads:[~2021-09-23 8:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-19 5:35 Xuan Ding
2021-09-23 8:15 ` Maxime Coquelin [this message]
2021-09-23 8:35 ` Ding, Xuan
2021-09-23 9:21 ` Ding, Xuan
2021-10-12 8:48 ` Maxime Coquelin
2021-10-13 0:28 ` Wang, Yinan
2021-10-13 1:36 ` [dpdk-dev] [PATCH v2] " Xuan Ding
2021-10-14 7:59 ` Maxime Coquelin
2021-10-21 12:32 ` 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=38c47e02-408f-d06d-5d96-26824239fa30@redhat.com \
--to=maxime.coquelin@redhat.com \
--cc=chenbo.xia@intel.com \
--cc=dev@dpdk.org \
--cc=jiayu.hu@intel.com \
--cc=stable@dpdk.org \
--cc=xuan.ding@intel.com \
--cc=yinan.wang@intel.com \
--cc=yong.liu@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).