From: Thomas Graf <tgraf@redhat.com>
To: Ben Pfaff <blp@nicira.com>
Cc: jesse@nicira.com, dev@openvswitch.org, netdev@vger.kernel.org,
dborkman@redhat.com, ffusco@redhat.com, fleitner@redhat.com,
xiyou.wangcong@gmail.com
Subject: Re: [PATCH openvswitch v2] netlink: Implement & enable memory mapped netlink i/o
Date: Mon, 02 Dec 2013 23:16:31 +0100 [thread overview]
Message-ID: <529D06BF.1010701@redhat.com> (raw)
In-Reply-To: <20131202212325.GG15335@nicira.com>
On 12/02/2013 10:23 PM, Ben Pfaff wrote:
> On Sat, Nov 30, 2013 at 01:27:33PM +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.
>>
>> Signed-off-by: Thomas Graf <tgraf@redhat.com>
>
> Clang reports:
>
> ../lib/netlink-socket.c:330:12: error: cast from 'char *' to 'struct nl_mmap_hdr *' increases required alignment from 1 to 4 [-Werror,-Wcast-align]
> return (struct nl_mmap_hdr *)(start + r->head * sock->frame_size);
> ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> ../lib/netlink-socket.c:369:22: error: implicit declaration of function '__ALIGN_KERNEL' is invalid in C99 [-Werror,-Wimplicit-function-declaration]
> -> sock->frame_size)
> ^
> ../lib/netlink-protocol.h:213:26: note: expanded from macro 'NL_MMAP_HDRLEN'
> #define NL_MMAP_HDRLEN NL_MMAP_MSG_ALIGN(sizeof(struct nl_mmap_hdr))
> ^
> ../lib/netlink-protocol.h:212:32: note: expanded from macro 'NL_MMAP_MSG_ALIGN'
> #define NL_MMAP_MSG_ALIGN(sz) __ALIGN_KERNEL(sz, NL_MMAP_MSG_ALIGNMENT)
> ^
> GCC reports:
>
> ../lib/netlink-socket.c: In function 'nl_sock_send_mmap':
> ../lib/netlink-socket.c:369:5: error: implicit declaration of function '__ALIGN_KERNEL' [-Werror=implicit-function-declaration]
> cc1: all warnings being treated as errors
Just so we can simplify this process: what's the oldest environment you
want the code to compile on?
next prev parent reply other threads:[~2013-12-02 22:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-30 12:27 [PATCH openvswitch v2] netlink: Implement & enable memory mapped netlink i/o Thomas Graf
2013-12-02 21:23 ` Ben Pfaff
2013-12-02 22:16 ` Thomas Graf [this message]
2013-12-02 22:26 ` Ben Pfaff
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=529D06BF.1010701@redhat.com \
--to=tgraf@redhat.com \
--cc=blp@nicira.com \
--cc=dborkman@redhat.com \
--cc=dev@openvswitch.org \
--cc=ffusco@redhat.com \
--cc=fleitner@redhat.com \
--cc=jesse@nicira.com \
--cc=netdev@vger.kernel.org \
--cc=xiyou.wangcong@gmail.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