From: Yuanhan Liu <yuanhan.liu@linux.intel.com>
To: Rich Lane <rich.lane@bigswitch.com>
Cc: dev@dpdk.org, Huawei Xie <huawei.xie@intel.com>
Subject: Re: [PATCH] vhost: add back support for concurrent enqueue
Date: Tue, 16 Aug 2016 10:37:15 +0800 [thread overview]
Message-ID: <20160816023715.GL30752@yliu-dev.sh.intel.com> (raw)
In-Reply-To: <1471291224-12755-1-git-send-email-rich.lane@bigswitch.com>
On Mon, Aug 15, 2016 at 01:00:24PM -0700, Rich Lane wrote:
> Concurrent enqueue is an important performance optimization when the number
> of cores used for switching is different than the number of vhost queues.
> I've observed a 20% performance improvement compared to a strategy that
> binds queues to cores.
>
> The atomic cmpset is only executed when the application calls
> rte_vhost_enqueue_burst_mp. Benchmarks show no performance impact
> when not using concurrent enqueue.
>
> Mergeable RX buffers aren't supported by concurrent enqueue to minimize
> code complexity.
I think that would break things when Mergeable rx is enabled (which is
actually enabled by default).
Besides that, as mentioned in the last week f2f talk, do you think adding
a new flag RTE_VHOST_USER_CONCURRENT_ENQUEUE (for rte_vhost_driver_register())
__might__ be a better idea? That could save us a API, to which I don't object
though.
--yliu
next prev parent reply other threads:[~2016-08-16 2:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-15 20:00 [PATCH] vhost: add back support for concurrent enqueue Rich Lane
2016-08-16 2:37 ` Yuanhan Liu [this message]
2016-08-18 18:27 ` Rich Lane
2016-08-22 14:16 ` Yuanhan Liu
2016-08-23 22:42 ` Rich Lane
2017-03-09 13:46 ` Thomas Monjalon
2017-03-14 5:59 ` Yuanhan Liu
2016-09-11 12:18 ` 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=20160816023715.GL30752@yliu-dev.sh.intel.com \
--to=yuanhan.liu@linux.intel.com \
--cc=dev@dpdk.org \
--cc=huawei.xie@intel.com \
--cc=rich.lane@bigswitch.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.