From: Stephen Hemminger <shemminger@vyatta.com>
To: Greg Rose <gregory.v.rose@intel.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net
Subject: Re: [RFC PATCH] iproute2: Add flag to indicate extended dump info
Date: Fri, 10 Feb 2012 08:41:21 -0800 [thread overview]
Message-ID: <20120210084121.3b922f1d@nehalam.linuxnetplumber.net> (raw)
In-Reply-To: <20120210151804.4175.12859.stgit@gitlad.jf.intel.com>
On Fri, 10 Feb 2012 07:18:05 -0800
Greg Rose <gregory.v.rose@intel.com> wrote:
> Add flag to the ip link dump command to indicate to the kernel that
> the application is requesting the extended interface information such
> as VFs. The kernel will take this flag as an implicit indication that
> the application has allocated a 16K or larger buffer, which is what
> the 'ip' command in fact does.
>
> Signed-off-by: Greg Rose <gregory.v.rose@intel.com>
> ---
>
> include/linux/netlink.h | 1 +
> lib/libnetlink.c | 2 +-
> 2 files changed, 2 insertions(+), 1 deletions(-)
>
> diff --git a/include/linux/netlink.h b/include/linux/netlink.h
> index 5c4f087..f913797 100644
> --- a/include/linux/netlink.h
> +++ b/include/linux/netlink.h
> @@ -59,6 +59,7 @@ struct nlmsghdr {
> #define NLM_F_MATCH 0x200 /* return all matching */
> #define NLM_F_ATOMIC 0x400 /* atomic GET */
> #define NLM_F_DUMP (NLM_F_ROOT|NLM_F_MATCH)
> +#define NLM_F_EXT 0x800 /* Get extended interface info such as VFs */
>
> /* Modifiers to NEW request */
> #define NLM_F_REPLACE 0x100 /* Override existing */
> diff --git a/lib/libnetlink.c b/lib/libnetlink.c
> index c581e11..f29da3d 100644
> --- a/lib/libnetlink.c
> +++ b/lib/libnetlink.c
> @@ -99,7 +99,7 @@ int rtnl_wilddump_request(struct rtnl_handle *rth, int family, int type)
> memset(&req, 0, sizeof(req));
> req.nlh.nlmsg_len = sizeof(req);
> req.nlh.nlmsg_type = type;
> - req.nlh.nlmsg_flags = NLM_F_DUMP|NLM_F_REQUEST;
> + req.nlh.nlmsg_flags = NLM_F_DUMP|NLM_F_REQUEST|NLM_F_EXT;
> req.nlh.nlmsg_pid = 0;
> req.nlh.nlmsg_seq = rth->dump = ++rth->seq;
> req.g.rtgen_family = family;
>
Make sure and test backwards compatibility with older kernels.
It should be fine as long as the flag is ignored now.
next prev parent reply other threads:[~2012-02-10 16:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-10 15:18 [RFC PATCH] iproute2: Add flag to indicate extended dump info Greg Rose
2012-02-10 16:41 ` Stephen Hemminger [this message]
2012-02-10 16:43 ` Rose, Gregory V
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=20120210084121.3b922f1d@nehalam.linuxnetplumber.net \
--to=shemminger@vyatta.com \
--cc=davem@davemloft.net \
--cc=gregory.v.rose@intel.com \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).