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
Subject: Re: [PATCH net-next v10 3/4] net sched actions: dump more than TCA_ACT_MAX_PRIO actions per batch
Date: Mon, 12 Jun 2017 13:47:51 +0200 [thread overview]
Message-ID: <20170612114751.GC1993@nanopsycho> (raw)
In-Reply-To: <fbf09ea1-36ee-69b1-74b0-ac436fff86ad@mojatatu.com>
Mon, Jun 12, 2017 at 01:16:05PM CEST, jhs@mojatatu.com wrote:
>On 17-06-11 10:13 AM, Jiri Pirko wrote:
>> Sun, Jun 11, 2017 at 01:53:45PM CEST, jhs@mojatatu.com wrote:
>[..]
>> > @@ -1168,14 +1185,24 @@ static int tc_dump_action(struct sk_buff *skb, struct netlink_callback *cb)
>> > if (a_o == NULL)
>> > return 0;
>> >
>> > + if (tb[TCA_ROOT_FLAGS])
>> > + nla_memcpy(&select_flags, tb[TCA_ROOT_FLAGS],
>> > + sizeof(select_flags));
>>
>> Please introduce a helper for this attr type in patch 1:
>>
>> u32 select_flags;
>>
>> select_flags = nla_get_flag_bits_values(tb[TCA_ROOT_FLAGS])
>>
>
>This also is not useful.
>It happens to be ok for this use case but not for the
>general case. i.e.
>We need to get the whole struct not just the values
>and use the selector to pick what bits are affected.
>Example if bit X is set to 1 in selector and bit X in value
>is 0, then we set the kernel's bit X to 0.
Sure, have another helper for selector then.
Or, you can have:
struct nla_flag_bits *fb;
fb = nla_get_flag_bits(tb[TCA_ROOT_FLAGS]);
Or all 3 helpers. My point is, it is a specific netlink attribute with
specific format, it should have get/put helpers.
next prev parent reply other threads:[~2017-06-12 11:47 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
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 [this message]
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=20170612114751.GC1993@nanopsycho \
--to=jiri@resnulli.us \
--cc=davem@davemloft.net \
--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 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.