From: Jason Wang <jasowang@redhat.com>
To: Tiwei Bie <tiwei.bie@intel.com>,
maxime.coquelin@redhat.com, zhihong.wang@intel.com, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH 0/5] Fixes and enhancements for Tx path in Virtio PMD
Date: Tue, 19 Feb 2019 21:40:05 +0800 [thread overview]
Message-ID: <6226c4fc-9671-451c-cb60-0b03a6216080@redhat.com> (raw)
In-Reply-To: <20190219105951.31046-1-tiwei.bie@intel.com>
On 2019/2/19 下午6:59, Tiwei Bie wrote:
> Below is a quick (unofficial) performance test (macfwd loop, 64B)
> for the packed ring optimizations in this series on an Intel(R)
> Xeon(R) Gold 6140 CPU @ 2.30GHz platform:
>
> w/o this series:
> packed ring normal/in-order: ~10.4 Mpps
>
> w/ this series:
> packed ring normal: ~10.9 Mpps
> packed ring in-order: ~11.3 Mpps
Since your series contain optimization for split ring as well. I wonder
whether you have its numbers as well.
Thanks
>
> In the test, we need to make sure that the vhost side is fast enough.
> So 4 forwarding cores are used in vhost side, and 1 forwarding core is
> used in virtio side.
>
> vhost side:
>
> ./x86_64-native-linuxapp-gcc/app/testpmd \
> -l 13,14,15,16,17 \
> --socket-mem 1024,0 \
> --file-prefix=vhost \
> --vdev=net_vhost0,iface=/tmp/vhost0,queues=4 \
> -- \
> --forward-mode=mac \
> -i \
> --rxq=4 \
> --txq=4 \
> --nb-cores 4
>
> virtio side:
>
> ./x86_64-native-linuxapp-gcc/app/testpmd \
> -l 8,9,10,11,12 \
> --socket-mem 1024,0 \
> --single-file-segments \
> --file-prefix=virtio-user \
> --vdev=virtio_user0,path=/tmp/vhost0,queues=4,in_order=1,packed_vq=1 \
> -- \
> --forward-mode=mac \
> -i \
> --rxq=4 \
> --txq=4 \
> --nb-cores 1
>
>
> Tiwei Bie (5):
> net/virtio: fix Tx desc cleanup for packed ring
> net/virtio: fix in-order Tx path for split ring
> net/virtio: fix in-order Tx path for packed ring
> net/virtio: introduce a helper for clearing net header
> net/virtio: optimize xmit enqueue for packed ring
>
> drivers/net/virtio/virtio_ethdev.c | 4 +-
> drivers/net/virtio/virtio_rxtx.c | 203 ++++++++++++++++++++---------
> 2 files changed, 146 insertions(+), 61 deletions(-)
>
next prev parent reply other threads:[~2019-02-19 13:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-19 10:59 Tiwei Bie
2019-02-19 10:59 ` [dpdk-dev] [PATCH 1/5] net/virtio: fix Tx desc cleanup for packed ring Tiwei Bie
2019-02-21 11:05 ` Maxime Coquelin
2019-02-19 10:59 ` [dpdk-dev] [PATCH 2/5] net/virtio: fix in-order Tx path for split ring Tiwei Bie
2019-02-21 11:08 ` Maxime Coquelin
2019-02-19 10:59 ` [dpdk-dev] [PATCH 3/5] net/virtio: fix in-order Tx path for packed ring Tiwei Bie
2019-02-21 11:16 ` Maxime Coquelin
2019-02-19 10:59 ` [dpdk-dev] [PATCH 4/5] net/virtio: introduce a helper for clearing net header Tiwei Bie
2019-02-21 11:18 ` Maxime Coquelin
2019-02-19 10:59 ` [dpdk-dev] [PATCH 5/5] net/virtio: optimize xmit enqueue for packed ring Tiwei Bie
2019-02-21 11:22 ` Maxime Coquelin
2019-02-21 12:25 ` Tiwei Bie
2019-02-21 12:31 ` Maxime Coquelin
2019-02-19 13:40 ` Jason Wang [this message]
2019-02-20 2:23 ` [dpdk-dev] [PATCH 0/5] Fixes and enhancements for Tx path in Virtio PMD Tiwei Bie
2019-02-21 17:45 ` 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=6226c4fc-9671-451c-cb60-0b03a6216080@redhat.com \
--to=jasowang@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).