From: "K. Y. Srinivasan" <kys@microsoft.com>
To: davem@davemloft.net, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, devel@linuxdriverproject.org,
olaf@aepfle.de, apw@canonical.com, jasowang@redhat.com
Cc: "K. Y. Srinivasan" <kys@microsoft.com>
Subject: [PATCH net-next 0/2] hv_netvsc: Eliminate memory allocation in the send path
Date: Sun, 29 Mar 2015 21:07:58 -0700 [thread overview]
Message-ID: <1427688478-27950-1-git-send-email-kys@microsoft.com> (raw)
The network protocol used to communicate with the host is the remote ndis (rndis)
protocol. We need to decorate each outgoing packet with a rndis header and
additional rndis state (rndis per-packet state). To manage this state, we
currently allocate memory in the transmit path. Eliminate this allocation by
requesting additional head room in the skb.
K. Y. Srinivasan (2):
hyperv: Cleanup the test for freeing skb when we use sendbuf
mechanism
hyperv: Eliminate memory allocation in the packet send path
drivers/net/hyperv/hyperv_net.h | 3 +-
drivers/net/hyperv/netvsc.c | 9 ++++-
drivers/net/hyperv/netvsc_drv.c | 70 ++++++++++++++++++++++++++----------
drivers/net/hyperv/rndis_filter.c | 2 +
4 files changed, 61 insertions(+), 23 deletions(-)
--
1.7.4.1
next reply other threads:[~2015-03-30 2:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-30 4:07 K. Y. Srinivasan [this message]
2015-03-30 4:08 ` [PATCH net-next 1/2] hv_netvsc: Cleanup the test for freeing skb when we use sendbuf mechanism K. Y. Srinivasan
2015-03-30 4:08 ` [PATCH net-next 2/2] hv_netvsc: Eliminate memory allocation in the packet send path K. Y. Srinivasan
2015-03-30 9:02 ` [PATCH net-next 1/2] hv_netvsc: Cleanup the test for freeing skb when we use sendbuf mechanism Dan Carpenter
2015-03-30 14:25 ` KY Srinivasan
2015-03-31 18:12 ` [PATCH net-next 0/2] hv_netvsc: Eliminate memory allocation in the send path 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=1427688478-27950-1-git-send-email-kys@microsoft.com \
--to=kys@microsoft.com \
--cc=apw@canonical.com \
--cc=davem@davemloft.net \
--cc=devel@linuxdriverproject.org \
--cc=jasowang@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=olaf@aepfle.de \
/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).