From: Hangbin Liu <liuhangbin@gmail.com>
To: Jamal Hadi Salim <jhs@mojatatu.com>
Cc: David Ahern <dsahern@kernel.org>,
Jakub Kicinski <kuba@kernel.org>,
netdev@vger.kernel.org, Cong Wang <xiyou.wangcong@gmail.com>,
Jiri Pirko <jiri@resnulli.us>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>,
Vlad Buslov <vladbu@nvidia.com>
Subject: Re: [PATCHv2 net-next] sched: multicast sched extack messages
Date: Tue, 27 Dec 2022 11:58:23 +0800 [thread overview]
Message-ID: <Y6ptX6Sq+F+tE+Ru@Laptop-X1> (raw)
In-Reply-To: <CAM0EoMndCfTkTBhG4VJKCmZG3c58eLRai71KzHG-FfzyzSwbew@mail.gmail.com>
Hi Jamal,
On Mon, Dec 26, 2022 at 11:31:24AM -0500, Jamal Hadi Salim wrote:
> My only concern is this is not generic enough i.e can other objects
> outside of filters do this?
> You are still doing it only for the filter (in tfilter_set_nl_ext() -
> sitting in cls_api)
> As i mentioned earlier, actions can also be offloaded independently;
> would this work with actions extack?
> If it wont work then perhaps we should go the avenue of using
> per-object(in this case filter) specific attributes
> to carry the extack as suggested by Jakub earlier.
Yes, I think we can do it on action objects, e.g. call tfilter_set_nl_ext()
in tca_get_fill:
tcf_add_notify() - tca_get_fill()
I will rename tfilter_set_nl_ext() to tc_set_nl_ext(). BTW, should we also
do it in qdisc/ class?
tclass_notify() - tc_fill_tclass()
qdisc_notify() - tc_fill_qdisc()
Thanks
Hangbin
next prev parent reply other threads:[~2022-12-27 3:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-21 9:39 [PATCHv2 net-next] sched: multicast sched extack messages Hangbin Liu
2022-12-22 1:28 ` Jakub Kicinski
2022-12-22 7:48 ` Hangbin Liu
2022-12-22 16:26 ` David Ahern
2022-12-23 2:35 ` Hangbin Liu
2022-12-26 16:31 ` Jamal Hadi Salim
2022-12-27 3:58 ` Hangbin Liu [this message]
2022-12-27 16:23 ` Jamal Hadi Salim
2022-12-28 8:41 ` Hangbin Liu
2022-12-31 13:48 ` 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=Y6ptX6Sq+F+tE+Ru@Laptop-X1 \
--to=liuhangbin@gmail.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=marcelo.leitner@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=vladbu@nvidia.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