From: Ben Pfaff <blp-l0M0P4e3n4LQT0dZR+AlfA@public.gmane.org>
To: Sergei Shtylyov
<sergei.shtylyov-M4DtvfQ/ZS1MRgGoP+s0PdBPR1lH4CV8@public.gmane.org>
Cc: dev-yBygre7rU0TnMu66kgdUjQ@public.gmane.org,
netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH openvswitch] linux: Signal datapath that unaligned Netlink message can be received
Date: Thu, 21 Nov 2013 12:52:08 -0800 [thread overview]
Message-ID: <20131121205208.GA24729@nicira.com> (raw)
In-Reply-To: <528E559C.4020201-M4DtvfQ/ZS1MRgGoP+s0PdBPR1lH4CV8@public.gmane.org>
On Thu, Nov 21, 2013 at 10:49:00PM +0400, Sergei Shtylyov wrote:
> On 21-11-2013 22:15, Thomas Graf wrote:
>
> >Following commit (''netlink: Do not enforce alignment of last Netlink
> >attribute''), signal the ability to receive unaligned Netlink messages
> >to the datapath to enable utilization of zerocopy optimizations.
>
> >Signed-off-by: Thomas Graf <tgraf-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
> [...]
>
> >diff --git a/lib/dpif-linux.c b/lib/dpif-linux.c
> >index 1dcf321..5c952bc 100644
> >--- a/lib/dpif-linux.c
> >+++ b/lib/dpif-linux.c
> [...]
> >@@ -1839,6 +1841,10 @@ dpif_linux_dp_to_ofpbuf(const struct dpif_linux_dp *dp, struct ofpbuf *buf)
> > nl_msg_put_u32(buf, OVS_DP_ATTR_UPCALL_PID, *dp->upcall_pid);
> > }
> >
> >+ if (dp->user_features) {
> >+ nl_msg_put_u32(buf, OVS_DP_ATTR_USER_FEATURES, dp->user_features);
> >+ }
> >+
>
> {} not needed here.
This is Open vSwitch code, so it follows Open vSwitch coding style,
which requires the {}.
next prev parent reply other threads:[~2013-11-21 20:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-21 18:15 [PATCH openvswitch] linux: Signal datapath that unaligned Netlink message can be received Thomas Graf
[not found] ` <48c93fb3c82bca0c9858ff528e2cf79d72d76082.1385057672.git.tgraf-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2013-11-21 18:49 ` Sergei Shtylyov
[not found] ` <528E559C.4020201-M4DtvfQ/ZS1MRgGoP+s0PdBPR1lH4CV8@public.gmane.org>
2013-11-21 20:52 ` Ben Pfaff [this message]
2013-11-22 15:41 ` [ovs-dev] " Sergei Shtylyov
2013-11-25 23:41 ` Jesse Gross
[not found] ` <CAEP_g=9Ax4A+eKZyUXhZhqFQ8Nyi5JeQzwyqJY=rVceKZHEHNw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-11-27 22:41 ` 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=20131121205208.GA24729@nicira.com \
--to=blp-l0m0p4e3n4lqt0dzr+alfa@public.gmane.org \
--cc=dev-yBygre7rU0TnMu66kgdUjQ@public.gmane.org \
--cc=netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=sergei.shtylyov-M4DtvfQ/ZS1MRgGoP+s0PdBPR1lH4CV8@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.