From: Jiri Pirko <jiri@resnulli.us>
To: Jamal Hadi Salim <jhs@mojatatu.com>
Cc: davem@davemloft.net, xiyou.wangcong@gmail.com,
eric.dumazet@gmail.com, netdev@vger.kernel.org,
Simon Horman <simon.horman@netronome.com>,
Benjamin LaHaise <bcrl@kvack.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 15:21:15 +0200 [thread overview]
Message-ID: <20170428132115.GD1886@nanopsycho.orion> (raw)
In-Reply-To: <09120c61-cbdc-f048-d7bb-268e5af3e92d@mojatatu.com>
Fri, Apr 28, 2017 at 02:30:17PM CEST, jhs@mojatatu.com wrote:
>On 17-04-28 03:02 AM, Jiri Pirko wrote:
>> Fri, Apr 28, 2017 at 03:22:53AM CEST, jhs@mojatatu.com wrote:
>
>[..]
>> > Maybe I am misunderstanding:
>> > Recall, this is what it looks like with this patchset:
>> > <nlh><subsytem-header>[TCA_ROOT_XXXX]
>> >
>> > TCA_ROOT_XXX is very subsystem specific. classifiers, qdiscs and many
>> > subsystems defined their own semantics for that TLV level. This specific
>> > "dump max" is very very specific to actions. They were crippled by the
>> > fact you could only send 32 at a time - this allows more to be sent.
>> >
>> > I thought initially you meant:
>> > <nlh>[NLA_XXX]<subsytem-header>[TCA_ROOT_XXXX]
>> >
>> > I think at the NLA_XXX you could fit netlink wide TLVs - but if i said
>> > "do a large dump" it is of no use to any other subsystem.
>>
>> Okay, I'm sorry, I had couple of beers yesterday so that might be
>> the cause why your msg makes me totally confused :O
>>
>> All I suggest is to replace NLA_U32 flags you want that does not
>> have any semantics with NLA_FLAGS flags, which eventually will carry
>> the exact same u32, but with predefined semantics, helpers, everything.
>>
>
>I didnt understand fully Jiri. Are you suggesting a new type called
>NLA_FLAGS which is re-usable elsewhere?
Exactly. That's what I'm saying.
next prev parent reply other threads:[~2017-04-28 13: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 [this message]
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
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=20170428132115.GD1886@nanopsycho.orion \
--to=jiri@resnulli.us \
--cc=bcrl@kvack.org \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=jhs@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;
as well as URLs for NNTP newsgroup(s).