public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Jiri Pirko <jiri@resnulli.us>
To: Jamal Hadi Salim <jhs@mojatatu.com>
Cc: davem@davemloft.net, netdev@vger.kernel.org,
	xiyou.wangcong@gmail.com, eric.dumazet@gmail.com,
	simon.horman@netronome.com, mrv@mojatatu.com, dsahern@gmail.com
Subject: Re: [PATCH net-next v10 1/4] net netlink: Add new type NLA_FLAG_BITS
Date: Mon, 12 Jun 2017 16:14:50 +0200	[thread overview]
Message-ID: <20170612141450.GD1993@nanopsycho> (raw)
In-Reply-To: <22f33fa9-1759-57b7-6aea-898f89c9f61f@mojatatu.com>

Mon, Jun 12, 2017 at 03:51:19PM CEST, jhs@mojatatu.com wrote:
>On 17-06-12 07:43 AM, Jiri Pirko wrote:
>> Mon, Jun 12, 2017 at 01:10:56PM CEST, jhs@mojatatu.com wrote:
>> > On 17-06-12 06:34 AM, Jiri Pirko wrote:
>> > > Sun, Jun 11, 2017 at 08:37:25PM CEST, jhs@mojatatu.com wrote:
>> > > > On 17-06-11 01:38 PM, Jamal Hadi Salim wrote:
>> > > > > On 17-06-11 09:49 AM, Jiri Pirko wrote:
>> > > > > > Sun, Jun 11, 2017 at 01:53:43PM CEST, jhs@mojatatu.com wrote:
>> > > > > > > From: Jamal Hadi Salim <jhs@mojatatu.com>
>> > > > > 
>> > > > > 
>> > > > > > > This patch also provides an extra feature: a validation callback
>> > > > > > > that could be speaciliazed for other types.
>> > > > > > 
>> > > > > > s/speaciliazed/speciliazed/
>> > > > > > 
>> > > > > 
>> > > > > Will fix.
>> > > > > 
>> > > > > 
>> > > > > > > 
>> > > > > > > [ATTR_GOO] = { .type = MYTYPE,
>> > > > > > >              .validation_data = &myvalidation_data,
>> > > > > > >                  .validate_content = mycontent_validator },
>> > > > > > 
>> > > > > > Indent is wrong. (Does not matter really in desc, but anyway)
>> > > > > > 
>> > > > > 
>> > > > > I cant find out how it got indented that way; my source
>> > > > > or email dont show it as such (but really doesnt matter).
>> > > > > 
>> > > > > 
>> > > > > > Suggested-by: Jiri Pirko <jiri@mellanox.com>
>> > > > > > 
>> > > > > 
>> > > > > Will add.
>> > > > > 
>> > > > > > 
>
>> > > I believe that this struct should go into:
>> > > include/uapi/linux/netlink.h
>> > > 
>> > > struct nla_flag_bits {
>> > > 	__u32 nla_flag_bits_values;
>> > > 	__u32 nla_flag_bits_selector;
>> > > };
>> > > 
>> > > Then you can use it from userspace and everywhere in kernel.
>> > > 
>> > That file seems to be very out of place for this stuff.
>> 
>> Howcome? It is a common netlink api.
>> 
>
>Take a look at that file's content. It talks about what goes in
>the netlink header. Adding types in it seems out of place.

Bit less than rtnetlink.h. But I agree it is not optimal. Re optimal,
please see below.


>
>
>> > NLA_XXX are kernel side types.  They are part of net/netlink.h which is
>> > not uapi accessible.
>> > David Ahern has submitted a patch to move all those defines to iproute2.
>> > Will make sense to move these to a uapi/linux/netlink-types.h but that
>> > is waay beyond the scope of this patch set.
>> 
>> Well, I don't think so :)
>> 
>> The thing is, struct nla_flag_bits is tightly coupled with NLA_FLAG_BITS
>> enum value. They should be in the same uapi file. That makes sense to me.
>> 
>
>Sure - they should be in the same file. But is it uapi/linux/netlink.h?

Might be the netlink-types.h you mentioned above.

ccing DavidA.

  reply	other threads:[~2017-06-12 14:14 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-11 11:53 [PATCH net-next v10 0/4] net sched actions: improve dump performance Jamal Hadi Salim
2017-06-11 11:53 ` [PATCH net-next v10 1/4] net netlink: Add new type NLA_FLAG_BITS Jamal Hadi Salim
2017-06-11 13:49   ` Jiri Pirko
2017-06-11 17:38     ` Jamal Hadi Salim
2017-06-11 18:37       ` Jamal Hadi Salim
2017-06-12 10:34         ` Jiri Pirko
2017-06-12 11:10           ` Jamal Hadi Salim
2017-06-12 11:43             ` Jiri Pirko
2017-06-12 13:51               ` Jamal Hadi Salim
2017-06-12 14:14                 ` Jiri Pirko [this message]
2017-06-12 15:00                   ` David Ahern
2017-06-12 19:22                     ` Jiri Pirko
2017-06-12 19:58                       ` David Ahern
2017-06-13  5:32                         ` Jiri Pirko
2017-06-13 10:53                           ` Jamal Hadi Salim
2017-06-13 11:25                             ` Jiri Pirko
2017-06-13 13:58                               ` David Ahern
2017-06-11 11:53 ` [PATCH net-next v10 2/4] net sched actions: Use proper root attribute table for actions Jamal Hadi Salim
2017-06-11 13:55   ` Jiri Pirko
2017-06-11 11:53 ` [PATCH net-next v10 3/4] net sched actions: dump more than TCA_ACT_MAX_PRIO actions per batch Jamal Hadi Salim
2017-06-11 14:13   ` Jiri Pirko
2017-06-11 17:45     ` Jamal Hadi Salim
2017-06-12 11:16     ` Jamal Hadi Salim
2017-06-12 11:47       ` Jiri Pirko
2017-06-12 13:57         ` Jamal Hadi Salim
2017-06-12 14:16           ` Jiri Pirko
2017-06-11 11:53 ` [PATCH net-next v10 4/4] net sched actions: add time filter for action dumping Jamal Hadi Salim
2017-06-11 12:06 ` [PATCH net-next v10 0/4] net sched actions: improve dump performance Jamal Hadi Salim

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=20170612141450.GD1993@nanopsycho \
    --to=jiri@resnulli.us \
    --cc=davem@davemloft.net \
    --cc=dsahern@gmail.com \
    --cc=eric.dumazet@gmail.com \
    --cc=jhs@mojatatu.com \
    --cc=mrv@mojatatu.com \
    --cc=netdev@vger.kernel.org \
    --cc=simon.horman@netronome.com \
    --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