[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230109114306.07d81e76@kernel.org>
Date: Mon, 9 Jan 2023 11:43:06 -0800
From: Jakub Kicinski <kuba@...nel.org>
To: Jamal Hadi Salim <jhs@...atatu.com>
Cc: Hangbin Liu <liuhangbin@...il.com>, netdev@...r.kernel.org,
Cong Wang <xiyou.wangcong@...il.com>,
Jiri Pirko <jiri@...nulli.us>,
"David S. Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>,
Paolo Abeni <pabeni@...hat.com>,
David Ahern <dsahern@...nel.org>,
Marcelo Ricardo Leitner <marcelo.leitner@...il.com>
Subject: Re: [PATCHv3 net-next] sched: multicast sched extack messages
On Mon, 9 Jan 2023 10:56:00 -0500 Jamal Hadi Salim wrote:
> IMO the feature is useful. The idea of using a single tool to get the
> details improves the operational experience.
> And in this case this is a valid event (someone tried to add an entry to
> hardware and s/ware and it worked for
> one and not the other).
> I think Jakub's objection is in the approach.
Right.
> Jakub, would using specific attributes restricted to
> just QDISC/FILTER/ACTION work for you?
Yes, specific attr to wrap the extack seems acceptable.
Powered by blists - more mailing lists