From: Thomas Graf <tgraf-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Ben Pfaff <blp-l0M0P4e3n4LQT0dZR+AlfA@public.gmane.org>
Cc: dev-yBygre7rU0TnMu66kgdUjQ@public.gmane.org,
netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
fleitner-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org
Subject: Re: [PATCH openvswitch] netlink: Implement & enable memory mapped netlink i/o
Date: Wed, 27 Nov 2013 23:51:20 +0100 [thread overview]
Message-ID: <52967768.8090308@redhat.com> (raw)
In-Reply-To: <20131125230253.GR1435-l0M0P4e3n4LQT0dZR+AlfA@public.gmane.org>
On 11/26/2013 12:02 AM, Ben Pfaff wrote:
> On Thu, Nov 21, 2013 at 07:16:54PM +0100, Thomas Graf wrote:
>> Based on the initial patch by Cong Wang posted a couple of months
>> ago.
>>
>> This is the user space counterpart needed for the kernel patch
>> '[PATCH net-next 3/8] openvswitch: Enable memory mapped Netlink i/o'
>>
>> Allows the kernel to construct Netlink messages on memory mapped
>> buffers and thus avoids copying. The functionality is enabled on
>> sockets used for unicast traffic.
>>
>> Further optimizations are possible by avoiding the copy into the
>> ofpbuf after reading.
>>
>> Cc: Cong Wang <xiyou.wangcong-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
>> Signed-off-by: Thomas Graf <tgraf-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
>
> Does this depend on other patches or some specific Linux kernel
> headers? It doesn't build here on GCC (similar results with Clang):
Yes, it depends on a sufficiently recent <linux/netlink.h>. We can
either #ifdef the mmap code or we provide a local copy of
<linux/netlink.h> in include/linux. The code automatically falls back if
the kernel does not support NL MMAP so that seems superior.
What do you prefer?
next prev parent reply other threads:[~2013-11-27 22:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-21 18:16 [PATCH openvswitch] netlink: Implement & enable memory mapped netlink i/o Thomas Graf
2013-11-25 23:02 ` [ovs-dev] " Ben Pfaff
[not found] ` <20131125230253.GR1435-l0M0P4e3n4LQT0dZR+AlfA@public.gmane.org>
2013-11-27 22:51 ` Thomas Graf [this message]
2013-11-28 19:24 ` Ben Pfaff
[not found] ` <20131128192449.GA28279-l0M0P4e3n4LQT0dZR+AlfA@public.gmane.org>
2013-11-28 22:31 ` Thomas Graf
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=52967768.8090308@redhat.com \
--to=tgraf-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
--cc=blp-l0M0P4e3n4LQT0dZR+AlfA@public.gmane.org \
--cc=dev-yBygre7rU0TnMu66kgdUjQ@public.gmane.org \
--cc=fleitner-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.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).