From: Stephen Hemminger <stephen@networkplumber.org>
To: davem@davemloft.net
Cc: netdev@vger.kernel.org, Stephen Hemminger <sthemmin@microsoft.com>
Subject: [PATCH net-next 00/15] netvsc: misc patches
Date: Wed, 3 May 2017 16:01:02 -0700 [thread overview]
Message-ID: <20170503230117.20070-1-sthemmin@microsoft.com> (raw)
Mostly these are performance related. There is also one bug fix for
incorrect handling of NAPI on device removal
Stephen Hemminger (15):
vmbus: simplify hv_ringbuffer_read
vmbus: fix unnecessary signal events as result of NAPI
netvsc: make sure napi enabled before vmbus_open
netvsc: don't reacquire rtnl on device removal
netvsc: optimize avail percent calculation
netvsc: prefetch the first incoming ring element
netvsc: convert ring_size to unsigned
netvsc: allow overriding send/recv buffer size
netvsc: optimize netvsc_send_pkt
netvsc: replace modulus with mask for alignment
netvsc: reduce unnecessary memset
netvsc: size receive completion ring based on receive area
netvsc: convert open count from atomic to refcount
netvsc: optimize receive completions
netvsc: use vzalloc_node for receive completion data
drivers/hv/ring_buffer.c | 179 +++++++++---------------
drivers/net/hyperv/hyperv_net.h | 32 +++--
drivers/net/hyperv/netvsc.c | 282 +++++++++++++++++---------------------
drivers/net/hyperv/netvsc_drv.c | 56 ++++++--
drivers/net/hyperv/rndis_filter.c | 20 +--
include/linux/hyperv.h | 70 +---------
6 files changed, 266 insertions(+), 373 deletions(-)
--
2.11.0
next reply other threads:[~2017-05-03 23:01 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-03 23:01 Stephen Hemminger [this message]
2017-05-03 23:01 ` [PATCH net-next 01/15] vmbus: simplify hv_ringbuffer_read Stephen Hemminger
2017-05-03 23:01 ` [PATCH net-next 02/15] vmbus: fix unnecessary signal events as result of NAPI Stephen Hemminger
2017-05-03 23:01 ` [PATCH net-next 03/15] netvsc: make sure napi enabled before vmbus_open Stephen Hemminger
2017-05-03 23:01 ` [PATCH net-next 04/15] netvsc: don't reacquire rtnl on device removal Stephen Hemminger
2017-05-03 23:01 ` [PATCH net-next 05/15] netvsc: optimize avail percent calculation Stephen Hemminger
2017-05-03 23:01 ` [PATCH net-next 06/15] netvsc: prefetch the first incoming ring element Stephen Hemminger
2017-05-03 23:01 ` [PATCH net-next 07/15] netvsc: convert ring_size to unsigned Stephen Hemminger
2017-05-03 23:01 ` [PATCH net-next 08/15] netvsc: allow overriding send/recv buffer size Stephen Hemminger
2017-05-03 23:01 ` [PATCH net-next 09/15] netvsc: optimize netvsc_send_pkt Stephen Hemminger
2017-05-03 23:01 ` [PATCH net-next 10/15] netvsc: replace modulus with mask for alignment Stephen Hemminger
2017-05-03 23:01 ` [PATCH net-next 11/15] netvsc: reduce unnecessary memset Stephen Hemminger
2017-05-03 23:01 ` [PATCH net-next 12/15] netvsc: size receive completion ring based on receive area Stephen Hemminger
2017-05-03 23:01 ` [PATCH net-next 13/15] netvsc: convert open count from atomic to refcount Stephen Hemminger
2017-05-03 23:01 ` [PATCH net-next 14/15] netvsc: optimize receive completions Stephen Hemminger
2017-05-03 23:01 ` [PATCH 15/15] netvsc: use vzalloc_node for receive completion data Stephen Hemminger
2017-05-03 23:35 ` [PATCH net-next 00/15] netvsc: misc patches David Miller
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=20170503230117.20070-1-sthemmin@microsoft.com \
--to=stephen@networkplumber.org \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=sthemmin@microsoft.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).