From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Stephen Hemminger <stephen@networkplumber.org>, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH 0/4] netvsc performance enhancements
Date: Thu, 23 Aug 2018 15:47:27 +0100 [thread overview]
Message-ID: <b246d2c7-4fe3-7a87-01a6-13533535f888@intel.com> (raw)
In-Reply-To: <20180809175008.5787-1-stephen@networkplumber.org>
On 8/9/2018 6:50 PM, Stephen Hemminger wrote:
> Some more netvsc performance related changes.
> The biggest benefit comes from lowering the hypervisor polling rate
> from 100us to 50us. Supporting tx_done_cleanup can also help some
> applications get through the send completions faster.
>
> Stephen Hemminger (4):
> netvsc: chimney buffer size error handling
> bus/vmbus: add host latency tuning function
> netvsc: set lower host latency
> netvsc: implement tx_done_cleanup
Series applied to dpdk-next-net/master, thanks.
(Mentioned changes in individual patches applied while applying.)
prev parent reply other threads:[~2018-08-23 14:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-09 17:50 Stephen Hemminger
2018-08-09 17:50 ` [dpdk-dev] [PATCH 1/4] netvsc: chimney buffer size error handling Stephen Hemminger
2018-08-23 14:45 ` Ferruh Yigit
2018-08-23 15:38 ` Stephen Hemminger
2018-08-09 17:50 ` [dpdk-dev] [PATCH 2/4] bus/vmbus: add host latency tuning function Stephen Hemminger
2018-08-23 14:45 ` Ferruh Yigit
2018-08-23 15:40 ` Stephen Hemminger
2018-08-09 17:50 ` [dpdk-dev] [PATCH 3/4] netvsc: set lower host latency Stephen Hemminger
2018-08-09 17:50 ` [dpdk-dev] [PATCH 4/4] netvsc: implement tx_done_cleanup Stephen Hemminger
2018-08-23 14:46 ` Ferruh Yigit
2018-08-23 14:47 ` Ferruh Yigit [this message]
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=b246d2c7-4fe3-7a87-01a6-13533535f888@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=stephen@networkplumber.org \
/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).