From: Simon Horman <simon.horman@netronome.com>
To: David Miller <davem@davemloft.net>
Cc: jiri@resnulli.us, jhs@mojatatu.com, xiyou.wangcong@gmail.com,
eric.dumazet@gmail.com, netdev@vger.kernel.org
Subject: Re: [PATCH net-next v8 2/3] net sched actions: dump more than TCA_ACT_MAX_PRIO actions per batch
Date: Fri, 28 Apr 2017 14:21:32 +0200 [thread overview]
Message-ID: <20170428122131.GC19353@vergenet.net> (raw)
In-Reply-To: <20170426.104658.547156121898948265.davem@davemloft.net>
On Wed, Apr 26, 2017 at 10:46:58AM -0400, David Miller wrote:
> From: Jiri Pirko <jiri@resnulli.us>
> Date: Wed, 26 Apr 2017 15:05:06 +0200
>
> > Wed, Apr 26, 2017 at 02:46:22PM CEST, jhs@mojatatu.com wrote:
> >>On 17-04-26 07:02 AM, Simon Horman wrote:
> >>> On Tue, Apr 25, 2017 at 06:04:45PM +0200, Jiri Pirko wrote:
> >>[..]
> >>
> >>> > So fix iproute2. It is always first kernel, then iproute2.
> >>>
> >>> Perhaps I am missing the point or somehow misguided but I would expect that
> >>> if the UAPI uses BIT() it also provides BIT().
> >>
> >>There is a user of BIT() already in iproute2 (devlink). We can move
> >>the code to be more generally available for other iproute2 users.
> >>Then this UAPI change makes use of it.
> >
> > Should be part of UAPI as well
> > I see that include/uapi/rdma/vmw_pvrdma-abi.h is using BIT macro.
> > I don't see BIT macro defined in UAPI (I thought it is). So either
> > define it there (not sure where) or just use "<<"
>
> "BIT" is a pretty crazy small simple name to pollute into the global
> namespace, IMHO.
It sounds to me that it would be best to just use "<<" rather than
spending cycles posturing on how to add it to the UAPI. Existing users
of BIT in the UAPI could also be updated to use "<<" to avoid having
a misleading precedence in-tree.
next prev parent reply other threads:[~2017-04-28 12:21 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-25 11:54 [PATCH net-next v8 0/3] net sched actions: improve dump performance Jamal Hadi Salim
2017-04-25 11:54 ` [PATCH net-next v8 1/3] net sched actions: Use proper root attribute table for actions Jamal Hadi Salim
2017-04-25 18:42 ` Simon Horman
2017-04-25 11:54 ` [PATCH net-next v8 2/3] net sched actions: dump more than TCA_ACT_MAX_PRIO actions per batch Jamal Hadi Salim
2017-04-25 12:13 ` Jiri Pirko
2017-04-25 13:01 ` Jamal Hadi Salim
2017-04-25 16:04 ` Jiri Pirko
2017-04-25 20:29 ` Jamal Hadi Salim
2017-04-26 6:19 ` Jiri Pirko
2017-04-26 11:07 ` Simon Horman
2017-04-26 13:00 ` Jamal Hadi Salim
2017-04-26 11:48 ` Jamal Hadi Salim
2017-04-26 12:08 ` Jiri Pirko
2017-04-26 13:14 ` Jamal Hadi Salim
2017-04-26 13:56 ` Jiri Pirko
2017-04-26 20:07 ` Jamal Hadi Salim
2017-04-27 6:30 ` Jiri Pirko
2017-04-28 1:22 ` Jamal Hadi Salim
2017-04-28 7:02 ` Jiri Pirko
2017-04-28 12:30 ` Jamal Hadi Salim
2017-04-28 13:21 ` Jiri Pirko
2017-04-28 13:42 ` Jamal Hadi Salim
2017-04-28 14:02 ` Jiri Pirko
2017-04-30 10:34 ` Jamal Hadi Salim
2017-04-26 11:02 ` Simon Horman
2017-04-26 12:46 ` Jamal Hadi Salim
2017-04-26 13:05 ` Jiri Pirko
2017-04-26 14:46 ` David Miller
2017-04-26 14:58 ` Jiri Pirko
2017-04-28 12:21 ` Simon Horman [this message]
2017-04-28 12:55 ` Jamal Hadi Salim
2017-04-28 13:21 ` Jiri Pirko
2017-04-25 11:54 ` [PATCH net-next v8 3/3] net sched actions: add time filter for action dumping 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=20170428122131.GC19353@vergenet.net \
--to=simon.horman@netronome.com \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--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;
as well as URLs for NNTP newsgroup(s).