From: Stephen Hemminger <stephen@networkplumber.org>
To: kys@microsoft.com, haiyangz@microsoft.com, sthemmin@microsoft.com
Cc: devel@linuxdriverproject.org, netdev@vger.kernel.org
Subject: [PATCH net-next 0/5] netvsc: fixes and performance related changes
Date: Tue, 25 Jul 2017 13:04:17 -0700 [thread overview]
Message-ID: <20170725200422.13795-1-sthemmin@microsoft.com> (raw)
The first two are more fixes to problems introduced in
latest net-next changes. The rest are changes to improve performance
and reduce memory footprint. The driver used to allocate large
amounts of memory (33M) per interface, this reduces that down to
about 7M.
Stephen Hemminger (5):
netvsc: fix return value for set_channels
netvsc: fix warnings reported by lockdep
netvsc: optimize receive completions
netvsc: signal host if receive ring is emptied
netvsc: allow smaller send/recv buffer size
drivers/net/hyperv/hyperv_net.h | 24 ++--
drivers/net/hyperv/netvsc.c | 293 ++++++++++++++++----------------------
drivers/net/hyperv/netvsc_drv.c | 48 ++++++-
drivers/net/hyperv/rndis_filter.c | 104 +++++++-------
4 files changed, 228 insertions(+), 241 deletions(-)
--
2.11.0
next reply other threads:[~2017-07-25 20:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-25 20:04 Stephen Hemminger [this message]
2017-07-25 20:04 ` [PATCH net-next 1/5] netvsc: fix return value for set_channels Stephen Hemminger
2017-07-25 20:04 ` [PATCH net-next 2/5] netvsc: fix warnings reported by lockdep Stephen Hemminger
2017-07-25 20:04 ` [PATCH net-next 3/5] netvsc: optimize receive completions Stephen Hemminger
2017-07-25 21:07 ` Stephen Hemminger
2017-07-25 20:04 ` [PATCH net-next 4/5] netvsc: signal host if receive ring is emptied Stephen Hemminger
2017-07-25 20:04 ` [PATCH net-next 5/5] netvsc: allow smaller send/recv buffer size Stephen Hemminger
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=20170725200422.13795-1-sthemmin@microsoft.com \
--to=stephen@networkplumber.org \
--cc=devel@linuxdriverproject.org \
--cc=haiyangz@microsoft.com \
--cc=kys@microsoft.com \
--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).