OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

virtio-comment message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: Re: RE: RE: RE: RE: [virtio-comment] RE: RE: RE: RE: [RFC] virtio-net: support access and control the member devices

On Tue, Aug 8, 2023 at 11:16âAM Parav Pandit <parav@nvidia.com> wrote:
> > From: Jason Wang <jasowang@redhat.com>
> > 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.

It can be done in this way for sure but the question is why it must be
done in this way. A drawback of using switch is that it introduces

> A virtio switch object can be part of a existing virtio device or a new virtio device type in itself.

That's fine.

> Xuan,
> As we discussed, since the owner device packets also needs to be filtered, potentially outside of the owner device itself,

This seems the admin request out of the scope of virtio.


> Do you see the need to introduce virtio switch object now, or can it wait?

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]