From: Stephen Hemminger <shemming@brocade.com>
To: Phil Sutter <phil@nwl.cc>
Cc: <netdev@vger.kernel.org>
Subject: Re: [iproute PATCH RFC] libnetlink: introduce DECLARE_NLREQ
Date: Sun, 29 Nov 2015 12:07:52 -0800 [thread overview]
Message-ID: <20151129120752.73834f50@xeon-e3> (raw)
In-Reply-To: <1448544365-23153-1-git-send-email-phil@nwl.cc>
On Thu, 26 Nov 2015 14:26:05 +0100
Phil Sutter <phil@nwl.cc> wrote:
> This macro aims to simplify most netlink users' pattern to prepare a
> request, which is to create an unnamed struct and initialize it:
>
> | struct {
> | struct nlmsghdr n;
> | struct whatever foo;
> | char buf[arbitrary number];
> | } req;
> |
> | memset(&req, 0, sizeof(req));
> | req.n.nlmsg_len = NLMSG_LENGTH(sizeof(struct whatever));
> | req.n.nlmsg_flags = NLM_F_REQUEST;
>
> Having this patch applied, the above can be replaced by a static
> initializer like so:
>
> | DECLARE_NLREQ(req, n, struct whatever foo, arbitrary number);
>
> There is an added benefit, as well: Due to explicit alignment, the
> requested tailroom is really as big as requested no matter what size
> struct whatever really is.
>
> Signed-off-by: Phil Sutter <phil@nwl.cc>
> ---
> This patch is RFC because I want to wait for peer review and upstream
> acceptance before sending in the big refactoring patch itself.
> ---
> include/libnetlink.h | 11 +++++++++++
> 1 file changed, 11 insertions(+)
I am not a fan of complex macros. But netlink seems to get lots of them.
You need to add more parens round arguments (like name).
Really longterm would rather iproute2 switched to a cleaner library like libmnl
next prev parent reply other threads:[~2015-11-29 20:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-26 13:26 [iproute PATCH RFC] libnetlink: introduce DECLARE_NLREQ Phil Sutter
2015-11-26 13:56 ` Hannes Frederic Sowa
2015-11-26 14:00 ` Phil Sutter
2015-11-29 20:07 ` Stephen Hemminger [this message]
2015-11-29 21:40 ` Phil Sutter
2015-11-30 15:47 ` Phil Sutter
2015-11-30 17:20 ` Stephen Hemminger
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=20151129120752.73834f50@xeon-e3 \
--to=shemming@brocade.com \
--cc=netdev@vger.kernel.org \
--cc=phil@nwl.cc \
/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).