From: Maxime Coquelin <maxime.coquelin@redhat.com>
To: yuanhan.liu@linux.intel.com, dev@dpdk.org, mst@redhat.com
Cc: zhihong.wang@intel.com, ciara.loftus@intel.com,
Maxime Coquelin <maxime.coquelin@redhat.com>
Subject: [dpdk-dev] [PATCH 0/2] vhost: Add support to indirect descriptors on Rx path
Date: Tue, 18 Oct 2016 17:35:37 +0200 [thread overview]
Message-ID: <1476804939-8675-1-git-send-email-maxime.coquelin@redhat.com> (raw)
Indirect descriptor feature has been enabled in v16.11-rc1, but only TX path
was implemented.
However, some configurations expect it is supported for the Rx path:
- Windows guests with and without mergeable buffers enabled
- Linux guests with Kernel drivr with mergeable buffers disabled
This series add the support of indirect descs for the Rx path, and has been
tested with following configurations:
- Windows guest with indirect ON, mergeeable ON/OFF
- Linux guest with Kernel driver with indirect ON/OFF, mergeable ON/OFF
- Linux guest with Virtio PMD with mergeable ON/OFF
The performance degradation measured with/without this series with Virtio PMD
is around 1% (which doesn't use indirect descs for the Rx path).
The series is based on top of "vhost: optimize mergeable Rx path" v7.
Maxime Coquelin (2):
vhost: Add indirect desc support to Rx mergeable path
vhost: Add indirect desc support to the Rx no-mergeable path
lib/librte_vhost/virtio_net.c | 73 ++++++++++++++++++++++++++++++-------------
1 file changed, 51 insertions(+), 22 deletions(-)
--
2.7.4
next reply other threads:[~2016-10-18 15:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-18 15:35 Maxime Coquelin [this message]
2016-10-18 15:35 ` [dpdk-dev] [PATCH 1/2] vhost: Add indirect desc support to Rx mergeable path Maxime Coquelin
2016-10-18 15:35 ` [dpdk-dev] [PATCH 2/2] vhost: Add indirect desc support to the Rx no-mergeable path Maxime Coquelin
2016-10-21 15:58 ` [dpdk-dev] [PATCH 0/2] vhost: Add support to indirect descriptors on Rx path Yuanhan Liu
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=1476804939-8675-1-git-send-email-maxime.coquelin@redhat.com \
--to=maxime.coquelin@redhat.com \
--cc=ciara.loftus@intel.com \
--cc=dev@dpdk.org \
--cc=mst@redhat.com \
--cc=yuanhan.liu@linux.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).