From: Vladimir Oltean <vladimir.oltean@nxp.com>
To: Jamal Hadi Salim <jhs@mojatatu.com>
Cc: Paul Moses <p@1g4.org>,
netdev@vger.kernel.org, xiyou.wangcong@gmail.com,
jiri@resnulli.us, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, horms@kernel.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org,
Vinicius Costa Gomes <vinicius.gomes@intel.com>
Subject: Re: [PATCH net] net: sched: act_api: size RTM_GETACTION reply by fill size
Date: Fri, 6 Feb 2026 00:11:55 +0200 [thread overview]
Message-ID: <20260205221155.na4qrsuuuzpqo4hg@skbuf> (raw)
In-Reply-To: <CAM0EoMnUm497YUZYbrYeqecF6JYzFbjauV8ACf-h8pjgOd2jdg@mail.gmail.com>
On Thu, Feb 05, 2026 at 04:30:06PM -0500, Jamal Hadi Salim wrote:
> Yes, this kinda answers the question: we are looking for something
> that serves as an upper bound for the control list.
> Does the standard explicitly specify that it is arbitrary - or is that
> deduced by lack of mention of an upper bound.
> Either way imo we need to have a "reasonable" upper bound in the code.
>
> cheers,
> jamal
It doesn't specifically use the word "arbitrary" but it describes a
mechanism to indicate what the arbitrarily chosen upper bound is, if
there is one.
Specifically, clause 12.31.1.4 talks of a managed object for PSFP called
SupportedListMax. This is supposed to report the maximum values that the
AdminControlListLength and OperControlListLength parameters can hold in
this particular implementation.
There is no intrinsic or universally reasonable limit on their count.
It depends on the required schedule complexity.
next prev parent reply other threads:[~2026-02-05 22:12 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-30 13:43 Paul Moses
2026-01-30 16:05 ` Jamal Hadi Salim
2026-01-30 17:22 ` Paul Moses
2026-01-30 17:53 ` Jamal Hadi Salim
2026-01-30 20:47 ` Paul Moses
2026-01-31 16:51 ` Jamal Hadi Salim
2026-01-31 17:14 ` Jamal Hadi Salim
2026-01-31 17:18 ` Paul Moses
2026-01-31 17:34 ` Jamal Hadi Salim
2026-02-01 9:57 ` Paul Moses
2026-02-02 14:33 ` Jamal Hadi Salim
2026-02-02 20:49 ` Paul Moses
2026-02-05 15:13 ` Paul Moses
2026-02-05 19:23 ` Jamal Hadi Salim
2026-02-05 20:36 ` Vladimir Oltean
2026-02-05 21:30 ` Jamal Hadi Salim
2026-02-05 22:11 ` Vladimir Oltean [this message]
2026-02-06 13:33 ` 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=20260205221155.na4qrsuuuzpqo4hg@skbuf \
--to=vladimir.oltean@nxp.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=p@1g4.org \
--cc=pabeni@redhat.com \
--cc=stable@vger.kernel.org \
--cc=vinicius.gomes@intel.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
all inboxes | Powered by JetHome®