From: Stephen Hemminger <stephen@networkplumber.org>
To: Dave Taht <dave.taht@gmail.com>
Cc: Andrew Lunn <andrew@lunn.ch>, Jian Shen <shenjian15@huawei.com>,
"David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
Linux Kernel Network Developers <netdev@vger.kernel.org>,
linuxarm@openeuler.org
Subject: Re: [RFC net-next] net: extend netdev features
Date: Sat, 10 Jul 2021 13:32:27 -0700 [thread overview]
Message-ID: <20210710133227.348899f8@hermes.local> (raw)
In-Reply-To: <CAA93jw4uhezgu05uM2xohoPMbDvbMAVmivSf2wgPiO4OzScwRg@mail.gmail.com>
On Sat, 10 Jul 2021 08:35:52 -0700
Dave Taht <dave.taht@gmail.com> wrote:
> On Sat, Jul 10, 2021 at 8:18 AM Andrew Lunn <andrew@lunn.ch> wrote:
> >
> > > Infrastructure changes must be done as part of the patch that
> > > needs the new feature bit. It might be that your feature bit is
> > > not accepted as part of the review cycle, or a better alternative
> > > is proposed.
> >
> > Hi Stephan
> >
> > I agree with what you are saying, but i also think there is no way to
> > avoid needing more feature bits. So even if the new feature bit itself
> > is rejected, the code to allow it could be useful.
>
> I would rather passionately like to expand several old currently 16
> bit fields in tc and iptables to 32 bits,
> and break the 1000 user limitation we have in things like this:
>
> https://github.com/rchac/LibreQoS
Unfortunately, no one has stepped up to the heavy lifting of having a UAPI
compatibility layer for this.
next prev parent reply other threads:[~2021-07-10 20:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-10 9:40 [RFC net-next] net: extend netdev features Jian Shen
2021-07-10 15:11 ` Stephen Hemminger
2021-07-10 15:16 ` Andrew Lunn
2021-07-10 15:35 ` Dave Taht
2021-07-10 20:32 ` Stephen Hemminger [this message]
2021-07-12 2:43 ` shenjian (K)
2021-07-10 15:29 ` Andrew Lunn
[not found] ` <2b6bc8a7-6fe3-b42e-070d-f9a81560ecda@huawei.com>
2021-07-13 13:53 ` Andrew Lunn
2021-07-15 6:34 ` shenjian (K)
2021-07-10 19:05 ` Heiner Kallweit
2021-07-12 3:41 ` shenjian (K)
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=20210710133227.348899f8@hermes.local \
--to=stephen@networkplumber.org \
--cc=andrew@lunn.ch \
--cc=dave.taht@gmail.com \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=linuxarm@openeuler.org \
--cc=netdev@vger.kernel.org \
--cc=shenjian15@huawei.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).