From: Jens Freimann <jfreimann@redhat.com>
To: Maxime Coquelin <maxime.coquelin@redhat.com>
Cc: dev@dpdk.org, tiwei.bie@intel.com, zhihong.wang@intel.com
Subject: Re: [dpdk-dev] [PATCH v2 3/3] net/virtio: improve batching in mergeable path
Date: Wed, 19 Dec 2018 10:47:43 +0100 [thread overview]
Message-ID: <20181219094743.yjuqrbwk6mjiilt4@jenstp.localdomain> (raw)
In-Reply-To: <20181211134804.10318-4-maxime.coquelin@redhat.com>
On Tue, Dec 11, 2018 at 02:48:04PM +0100, Maxime Coquelin wrote:
>This patch improves both descriptors dequeue and refill,
>by using the same bathing strategy as done in in-order path.
s/bathing/batching/
>
>Signed-off-by: Maxime Coquelin <maxime.coquelin@redhat.com>
>---
> drivers/net/virtio/virtio_rxtx.c | 237 ++++++++++++++++---------------
> 1 file changed, 126 insertions(+), 111 deletions(-)
>
>diff --git a/drivers/net/virtio/virtio_rxtx.c b/drivers/net/virtio/virtio_rxtx.c
>index ebe5c74b5..59bcac2f7 100644
>--- a/drivers/net/virtio/virtio_rxtx.c
>+++ b/drivers/net/virtio/virtio_rxtx.c
>@@ -267,41 +267,42 @@ virtqueue_enqueue_refill_inorder(struct virtqueue *vq,
> }
>
> static inline int
>-virtqueue_enqueue_recv_refill(struct virtqueue *vq, struct rte_mbuf *cookie)
>+virtqueue_enqueue_recv_refill(struct virtqueue *vq, struct rte_mbuf **cookie,
>+ uint16_t num)
> {
> struct vq_desc_extra *dxp;
> struct virtio_hw *hw = vq->hw;
>- struct vring_desc *start_dp;
>- uint16_t needed = 1;
>- uint16_t head_idx, idx;
>+ struct vring_desc *start_dp = vq->vq_ring.desc;
>+ uint16_t idx, i;
>
> if (unlikely(vq->vq_free_cnt == 0))
> return -ENOSPC;
>- if (unlikely(vq->vq_free_cnt < needed))
>+ if (unlikely(vq->vq_free_cnt < num))
> return -EMSGSIZE;
>
>- head_idx = vq->vq_desc_head_idx;
>- if (unlikely(head_idx >= vq->vq_nentries))
>+ if (unlikely(vq->vq_desc_head_idx >= vq->vq_nentries))
> return -EFAULT;
>
>- idx = head_idx;
>- dxp = &vq->vq_descx[idx];
>- dxp->cookie = (void *)cookie;
>- dxp->ndescs = needed;
>+ for (i = 0; i < num; i++) {
>+ idx = vq->vq_desc_head_idx;
>+ dxp = &vq->vq_descx[idx];
>+ dxp->cookie = (void *)cookie[i];
I think code is safe as it is, but should we check if cookie actually points to something?
I tested this patch and saw the same performance improvement, so
Tested-by: Jens Freimann <jfreimann@redhat.com>
Reviewed-by: Jens Freimann <jfreimann@redhat.com>
regards,
Jens
next prev parent reply other threads:[~2018-12-19 9:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-11 13:48 [dpdk-dev] [PATCH v2 0/3] net/virtio: Rx paths improvements Maxime Coquelin
2018-12-11 13:48 ` [dpdk-dev] [PATCH v2 1/3] net/virtio: inline refill and offload helpers Maxime Coquelin
2018-12-19 9:25 ` Jens Freimann
2018-12-19 10:26 ` Gavin Hu (Arm Technology China)
2018-12-19 10:53 ` Jens Freimann
2018-12-19 12:04 ` Maxime Coquelin
2018-12-11 13:48 ` [dpdk-dev] [PATCH v2 2/3] net/virtio: add non-mergeable support to in-order path Maxime Coquelin
2018-12-19 11:27 ` Tiwei Bie
2018-12-11 13:48 ` [dpdk-dev] [PATCH v2 3/3] net/virtio: improve batching in mergeable path Maxime Coquelin
2018-12-19 9:47 ` Jens Freimann [this message]
2018-12-19 12:08 ` Maxime Coquelin
2018-12-19 11:18 ` Tiwei Bie
2018-12-19 12:01 ` 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=20181219094743.yjuqrbwk6mjiilt4@jenstp.localdomain \
--to=jfreimann@redhat.com \
--cc=dev@dpdk.org \
--cc=maxime.coquelin@redhat.com \
--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).