> -----Original Message-----
> From: [email protected] <[email protected]>
> On Behalf Of Parav Pandit
> Sent: Monday, August 7, 2023 9:11 PM
> To: Xuan Zhuo <[email protected]>
> Cc: [email protected]; [email protected]
> open.org; Michael S. Tsirkin <[email protected]>; Jason Wang
> <[email protected]>
> Subject: [EXT] [virtio-dev] RE: RE: RE: RE: RE: RE: [virtio-comment] RE:
> RE: RE: RE: [RFC] virtio-net: support access and control the member
> devices
>
> External Email
>
> ----------------------------------------------------------------------
>
>
> > From: Xuan Zhuo <[email protected]>
> > Sent: Tuesday, August 8, 2023 9:31 AM
> >
> > On Tue, 8 Aug 2023 03:16:44 +0000, Parav Pandit <[email protected]>
> wrote:
> > >
> > >
> > > > From: Jason Wang <[email protected]>
> > > > Sent: Tuesday, August 8, 2023 8:39 AM
> > >
> > > >
> > > > Yes, but even for TX, would it be better to filter the IP as early
> > > > as possible in the TX path other than depend on the switch to do
> that?
> > >
> > > The idea is to introduce filters on the new virtio switch object for
> tx and rx
> > both.
> >
> > Filters for tx?
> >
> Yes. the regular switchdev model that exists in Linux kernel for several
> years now.
This is what representors would be used for. The Tx of representee is the
RX of representor. Hence one can install RX L4/L3/L2 filters of choice
on representor using tc flower, offload to device if need be,
these would then be applied on the tx path of representee. Similarly the
owner device can also have rx filters installed to direct traffic to the
the representee.
> And similar in another hypervisor.
>
> > Are there other use cases?
> >
>
> >
> > > A virtio switch object can be part of a existing virtio device or a
> new virtio
> > device type in itself.
> > >
> > > Xuan,
> > > As we discussed, since the owner device packets also needs to be
> > > filtered, potentially outside of the owner device itself,
> > >
> > > Do you see the need to introduce virtio switch object now, or can it
> wait?
> >
> > For virtio switch, I am ok.
> >
> I didn't follow your answer "I am ok".
> Do you see the need now or can it wait?
>
> > But for me, I just have this requirement that needs the switch.
>
> > So if we do this in the device, then that is not need for me.
> >
> Device meaning outside of the virtio domain, for example dpu or
> something else, yes?
>
> > Now, you think we should introduce the rx/tx filter to the virtio
> switch.
> >
> I am asking to _not_ introduce currently.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
