From: Roman Mashak <mrv@mojatatu•com>
To: Eric Dumazet <eric.dumazet@gmail•com>
Cc: Jamal Hadi Salim <jhs@mojatatu•com>,
Jiri Pirko <jiri@resnulli•us>,
davem@davemloft•net, netdev@vger•kernel.org,
xiyou.wangcong@gmail•com
Subject: Re: [PATCH net-next 1/1] net sched actions: dump more than TCA_ACT_MAX_PRIO actions per batch
Date: Mon, 17 Apr 2017 13:51:32 -0400 [thread overview]
Message-ID: <851ssqq5wb.fsf@mojatatu.com> (raw)
In-Reply-To: <1492448905.10587.109.camel@edumazet-glaptop3.roam.corp.google.com> (Eric Dumazet's message of "Mon, 17 Apr 2017 10:08:25 -0700")
Eric Dumazet <eric.dumazet@gmail•com> writes:
> On Mon, 2017-04-17 at 12:46 -0400, Jamal Hadi Salim wrote:
>
>> Of course it is trivial to add this as attributes and 32 bits
>> for this case is not a big deal because it is done once. I want to talk
>> about the pads instead ;-> What do you suggest we do with pads?
>
> We do nothing with pads. Just leave them.
>
> Or, you need something to make sure to not break old user applications.
>
> Something like a version.
Would be a new NLM_F_* modifier for GET request an option for large
dumps implementation? Looks like there are extract bits and Johannes'
patches for extended ACK do not use it.
next prev parent reply other threads:[~2017-04-17 17:51 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-16 12:34 [PATCH net-next 1/1] net sched actions: dump more than TCA_ACT_MAX_PRIO actions per batch Jamal Hadi Salim
2017-04-17 8:19 ` Jiri Pirko
2017-04-17 11:01 ` Jamal Hadi Salim
2017-04-17 13:10 ` Eric Dumazet
2017-04-17 14:02 ` Jamal Hadi Salim
2017-04-17 14:58 ` Eric Dumazet
2017-04-17 16:40 ` Jamal Hadi Salim
2017-04-17 15:31 ` Jiri Pirko
2017-04-17 16:46 ` Jamal Hadi Salim
2017-04-17 17:04 ` Jiri Pirko
2017-04-17 17:08 ` Eric Dumazet
2017-04-17 17:51 ` Roman Mashak [this message]
2017-04-18 12:48 ` Case for reusing netlink PADs WAS(Re: " Jamal Hadi Salim
2017-04-18 13:16 ` Jiri Pirko
2017-04-18 15:29 ` David Miller
2017-04-18 14:19 ` Eric Dumazet
2017-04-18 15:25 ` David Miller
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=851ssqq5wb.fsf@mojatatu.com \
--to=mrv@mojatatu$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=eric.dumazet@gmail$(echo .)com \
--cc=jhs@mojatatu$(echo .)com \
--cc=jiri@resnulli$(echo .)us \
--cc=netdev@vger$(echo .)kernel.org \
--cc=xiyou.wangcong@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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