All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Dumazet <eric.dumazet@gmail.com>
To: Jamal Hadi Salim <jhs@mojatatu.com>
Cc: 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 10:08:25 -0700	[thread overview]
Message-ID: <1492448905.10587.109.camel@edumazet-glaptop3.roam.corp.google.com> (raw)
In-Reply-To: <0bd1e885-cdf3-60fc-783b-a075b777560b@mojatatu.com>

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.

  parent reply	other threads:[~2017-04-17 17:08 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 [this message]
2017-04-17 17:51             ` Roman Mashak
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=1492448905.10587.109.camel@edumazet-glaptop3.roam.corp.google.com \
    --to=eric.dumazet@gmail.com \
    --cc=davem@davemloft.net \
    --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 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.