From: Vitaly Kuznetsov <vkuznets@redhat.com>
To: devel@linuxdriverproject.org
Cc: linux-kernel@vger.kernel.org,
"K. Y. Srinivasan" <kys@microsoft.com>,
Haiyang Zhang <haiyangz@microsoft.com>
Subject: [PATCH 0/4] Drivers: hv: ring_buffer: make in-place consumption always possible
Date: Fri, 10 Jun 2016 11:47:08 +0200 [thread overview]
Message-ID: <1465552032-28933-1-git-send-email-vkuznets@redhat.com> (raw)
K. Y.,
I'd like to accompany your netvsc performance improvement work by making
in-place consumption of VMBus packets always possible. Currently we forbid
it when a packet 'wraps around' the ring so we can't provide a single
pointer to it.
The idea if this series is dead simple: let's make a single virtual mapping
for two copies (actually, two sets of pages which consist the ring buffer)
of the ring buffer. With such a mapping we can always provide a pointers
for in-place consumption to drivers. Copy path can also benefit from such
mappings as we eliminate the need for conditional checking in copy_to/
copy_from functions and use a single memcpy().
Lightly tested with 'netvsc: Use the new in-place consumption APIs in the
rx path' patch and with storvsc driver.
Vitaly Kuznetsov (4):
Drivers: hv: cleanup vmbus_open() for wrap around mappings
Drivers: hv: ring_buffer: wrap around mappings for ring buffers
Drivers: hv: ring_buffer: use wrap around mappings in
hv_copy{from,to}_ringbuffer()
Drivers: hv: ring_buffer: count on wrap around mappings in
get_next_pkt_raw()
drivers/hv/channel.c | 68 ++++++++++++++++++++++++-----------------------
drivers/hv/hyperv_vmbus.h | 4 +--
drivers/hv/ring_buffer.c | 61 ++++++++++++++++++++++++------------------
include/linux/hyperv.h | 32 ++++++++--------------
4 files changed, 83 insertions(+), 82 deletions(-)
--
2.5.5
next reply other threads:[~2016-06-10 9:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-10 9:47 Vitaly Kuznetsov [this message]
2016-06-10 9:47 ` [PATCH 1/4] Drivers: hv: cleanup vmbus_open() for wrap around mappings Vitaly Kuznetsov
2016-06-10 9:47 ` [PATCH 2/4] Drivers: hv: ring_buffer: wrap around mappings for ring buffers Vitaly Kuznetsov
2016-06-10 9:47 ` [PATCH 3/4] Drivers: hv: ring_buffer: use wrap around mappings in hv_copy{from,to}_ringbuffer() Vitaly Kuznetsov
2016-06-10 9:47 ` [PATCH 4/4] Drivers: hv: ring_buffer: count on wrap around mappings in get_next_pkt_raw() Vitaly Kuznetsov
2016-06-10 13:30 ` [PATCH 0/4] Drivers: hv: ring_buffer: make in-place consumption always possible KY Srinivasan
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=1465552032-28933-1-git-send-email-vkuznets@redhat.com \
--to=vkuznets@redhat.com \
--cc=devel@linuxdriverproject.org \
--cc=haiyangz@microsoft.com \
--cc=kys@microsoft.com \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®