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: [virtio-comment] RE: RE: RE: RE: [RFC] virtio-net: support access and control the member devices


On Fri, 4 Aug 2023 07:26:01 +0000, Parav Pandit <parav@nvidia.com> wrote:
>
>
> > From: Xuan Zhuo <xuanzhuo@linux.alibaba.com>
> > Sent: Friday, August 4, 2023 12:24 PM
>
> > I know the gap. For us, the switch is under all devices(including the owner
> > device).
> > So we need to control the switch separately.
> >
> Right. Same for other devices too, including ours.
> Hence, it is also located outside of the owner device (on a different system).
>
> If the switch is not a virtio device, does it really need to be exposed as virtio object?
>
> > In your structure, the owner device works as the switch. It has port to connect
> > to the vf devices.
> >
> Right. I just put owner device as switch for simplicity of the discussion.
>
> At this point to have port for owner device requires creating a dedicated switching object, to be located sometimes side by side inside the owner, sometimes outside.
> All of these cases to be crafted, please rethink if this is _really_ needed as virtio object or not.


YES.

We can hear others.

@Jason @Michael


Thanks


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