Thread (20 messages) 20 messages, 5 authors, 2023-10-10

Re: [PATCH net-next v4 0/3] net/sched: Introduce tc block ports tracking and use

From: Jamal Hadi Salim <jhs@mojatatu.com>
Date: 2023-10-06 23:00:14

On Fri, Oct 6, 2023 at 6:25 PM Jakub Kicinski [off-list ref] wrote:
On Fri, 6 Oct 2023 15:06:45 -0400 Jamal Hadi Salim wrote:
quoted
quoted
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
We dont have any rule that says all actions MUST have parameters ;->
There is nothing speacial about any action that doesnt have a
parameter.
quoted
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?
It is not an L2 switch - the L2 example switch was what came to mind
of something that does a broadcast (it doesnt depend on MAC addresses
for example). Could have called it a hub. Ex: you could match on many
different header fields or skb metadata, then first modify the packet
using NAT, etc and then "blockcast" it.

cheers,
jamal
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help