From: David Miller <davem@davemloft.net>
To: jhs@mojatatu.com
Cc: eric.dumazet@gmail.com, jiri@resnulli.us,
xiyou.wangcong@gmail.com, netdev@vger.kernel.org
Subject: Re: [PATCH net-next v6 2/3] net sched actions: dump more than TCA_ACT_MAX_PRIO actions per batch
Date: Fri, 21 Apr 2017 12:07:19 -0400 (EDT) [thread overview]
Message-ID: <20170421.120719.110454615745765701.davem@davemloft.net> (raw)
In-Reply-To: <6b26ef20-972f-24bf-22bf-8462606ce16d@mojatatu.com>
From: Jamal Hadi Salim <jhs@mojatatu.com>
Date: Fri, 21 Apr 2017 11:40:00 -0400
> Eric: Your are speaking in generalities and you starting premise is
> wrong.
I disagree.
If we never checked, it is our problem and our issue. Not that of
the user.
If you want to start checking and verifying new attribute bitmasks
now, great! But we are stuck in the case of existing bitmasks
and pads because we did not do so at the time we released them
into the wild.
next prev parent reply other threads:[~2017-04-21 17:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-21 10:55 [PATCH net-next v6 0/3] net sched actions: improve dump performance Jamal Hadi Salim
2017-04-21 10:55 ` [PATCH net-next v6 1/3] net sched actions: User proper root attribute table for actions Jamal Hadi Salim
2017-04-21 13:08 ` Jiri Pirko
2017-04-21 14:50 ` Jamal Hadi Salim
2017-04-21 10:55 ` [PATCH net-next v6 2/3] net sched actions: dump more than TCA_ACT_MAX_PRIO actions per batch Jamal Hadi Salim
2017-04-21 13:12 ` Jiri Pirko
2017-04-21 15:12 ` Jamal Hadi Salim
2017-04-21 15:20 ` Eric Dumazet
2017-04-21 15:40 ` Jamal Hadi Salim
2017-04-21 16:07 ` David Miller [this message]
2017-04-21 16:10 ` Eric Dumazet
2017-04-21 10:55 ` [PATCH net-next v6 3/3] net sched actions: add time filter for action dumping Jamal Hadi Salim
2017-04-21 13:13 ` Jiri Pirko
2017-04-21 15:13 ` 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=20170421.120719.110454615745765701.davem@davemloft.net \
--to=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