Netdev List
 help / color / mirror / Atom feed
From: Cong Wang <xiyou.wangcong@gmail.com>
To: Simon Horman <horms@kernel.org>
Cc: Vinicius Costa Gomes <vinicius.gomes@intel.com>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>,
	Jamal Hadi Salim <jhs@mojatatu.com>,
	Jiri Pirko <jiri@resnulli.us>,
	Maher Azzouzi <maherazz04@gmail.com>,
	Paolo Abeni <pabeni@redhat.com>,
	Vladimir Oltean <vladimir.oltean@nxp.com>,
	netdev@vger.kernel.org
Subject: Re: [PATCH net-next] net/sched: taprio: align entry index attr validation with mqprio
Date: Fri, 25 Jul 2025 15:35:09 -0700	[thread overview]
Message-ID: <aIQGnbRbTRihh6ii@pop-os.localdomain> (raw)
In-Reply-To: <20250725-taprio-idx-parse-v1-1-b582fffcde37@kernel.org>

On Fri, Jul 25, 2025 at 10:56:47AM +0100, Simon Horman wrote:
> Both taprio and mqprio have code to validate respective entry index
> attributes. The validation is indented to ensure that the attribute is
> present, and that it's value is in range, and that each value is only
> used once.
> 
> The purpose of this patch is to align the implementation of taprio with
> that of mqprio as there seems to be no good reason for them to differ.
> For one thing, this way, bugs will be present in both or neither.
> 
> As a follow-up some consideration could be given to a common function
> used by both sch.
> 
> No functional change intended.
> 
> Except of tdc run: the results of the taprio tests
> 
>   # ok 81 ba39 - Add taprio Qdisc to multi-queue device (8 queues)
>   # ok 82 9462 - Add taprio Qdisc with multiple sched-entry
>   # ok 83 8d92 - Add taprio Qdisc with txtime-delay
>   # ok 84 d092 - Delete taprio Qdisc with valid handle
>   # ok 85 8471 - Show taprio class
>   # ok 86 0a85 - Add taprio Qdisc to single-queue device
>   # ok 87 6f62 - Add taprio Qdisc with too short interval
>   # ok 88 831f - Add taprio Qdisc with too short cycle-time
>   # ok 89 3e1e - Add taprio Qdisc with an invalid cycle-time
>   # ok 90 39b4 - Reject grafting taprio as child qdisc of software taprio
>   # ok 91 e8a1 - Reject grafting taprio as child qdisc of offloaded taprio
>   # ok 92 a7bf - Graft cbs as child of software taprio
>   # ok 93 6a83 - Graft cbs as child of offloaded taprio
> 
> Cc: Vladimir Oltean <vladimir.oltean@nxp.com>
> Cc: Maher Azzouzi <maherazz04@gmail.com>
> Link: https://lore.kernel.org/netdev/20250723125521.GA2459@horms.kernel.org/
> Signed-off-by: Simon Horman <horms@kernel.org>

Reviewed-by: Cong Wang <xiyou.wangcong@gmail.com>

Thanks.

  reply	other threads:[~2025-07-25 22:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-25  9:56 [PATCH net-next] net/sched: taprio: align entry index attr validation with mqprio Simon Horman
2025-07-25 22:35 ` Cong Wang [this message]
2025-07-26  0:10 ` Vinicius Costa Gomes
2025-07-26 18:40 ` patchwork-bot+netdevbpf

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=aIQGnbRbTRihh6ii@pop-os.localdomain \
    --to=xiyou.wangcong@gmail.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=maherazz04@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=vinicius.gomes@intel.com \
    --cc=vladimir.oltean@nxp.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