From: Jakub Kicinski <kuba@kernel.org>
To: Jamal Hadi Salim <jhs@mojatatu.com>
Cc: Jiri Pirko <jiri@resnulli.us>,
Victor Nogueira <victor@mojatatu.com>,
xiyou.wangcong@gmail.com, davem@davemloft.net, pabeni@redhat.com,
edumazet@google.com, mleitner@redhat.com, vladbu@nvidia.com,
simon.horman@corigine.com, pctammela@mojatatu.com,
netdev@vger.kernel.org, kernel@mojatatu.com
Subject: Re: [PATCH net-next v4 0/3] net/sched: Introduce tc block ports tracking and use
Date: Fri, 6 Oct 2023 15:25:16 -0700 [thread overview]
Message-ID: <20231006152516.5ff2aeca@kernel.org> (raw)
In-Reply-To: <CAM0EoMn1rNX=A3Gd81cZrnutpuch-ZDsSgXdG72uPQ=N2fGoAg@mail.gmail.com>
On Fri, 6 Oct 2023 15:06:45 -0400 Jamal Hadi Salim wrote:
> > I don't understand the need for configuration less here. You don't have
> > it for the rest of the actions. Why this is special?
+1, FWIW
> It is not needed really. Think of an L2 switch - the broadcast action
> is to send to all ports but self.
We do have an implementation of an L2 switch already, what's the use
case which necessitates this new action / functionality?
next prev parent reply other threads:[~2023-10-06 22:25 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-05 18:42 [PATCH net-next v4 0/3] net/sched: Introduce tc block ports tracking and use Victor Nogueira
2023-10-05 18:42 ` [PATCH net-next v4 1/3] net/sched: Introduce tc block netdev tracking infra Victor Nogueira
2023-10-05 18:42 ` [PATCH net-next v4 2/3] net/sched: cls_api: Expose tc block to the datapath Victor Nogueira
2023-10-05 18:42 ` [PATCH net-next v4 3/3] net/sched: act_blockcast: Introduce blockcast tc action Victor Nogueira
2023-10-06 12:59 ` [PATCH net-next v4 0/3] net/sched: Introduce tc block ports tracking and use Jiri Pirko
2023-10-06 15:37 ` Jamal Hadi Salim
2023-10-06 16:50 ` Jiri Pirko
2023-10-06 19:06 ` Jamal Hadi Salim
2023-10-06 22:25 ` Jakub Kicinski [this message]
2023-10-06 23:00 ` Jamal Hadi Salim
2023-10-07 10:20 ` Jiri Pirko
2023-10-07 11:06 ` Jamal Hadi Salim
2023-10-07 12:43 ` Jiri Pirko
2023-10-07 14:09 ` Jamal Hadi Salim
2023-10-07 17:20 ` Jiri Pirko
2023-10-08 12:38 ` Jamal Hadi Salim
2023-10-09 20:54 ` Marcelo Ricardo Leitner
2023-10-10 7:41 ` Jiri Pirko
2023-10-10 11:54 ` Marcelo Ricardo Leitner
2023-10-07 10:22 ` Jiri Pirko
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=20231006152516.5ff2aeca@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=kernel@mojatatu.com \
--cc=mleitner@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pctammela@mojatatu.com \
--cc=simon.horman@corigine.com \
--cc=victor@mojatatu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.