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

Xuan Zhuo
2023-08-03T11:46:54Z

On Thu, 3 Aug 2023 11:39:20 +0000, Parav Pandit <parav@nvidia.com> wrote:
>
> > From: Xuan Zhuo <xuanzhuo@linux.alibaba.com>
> > Sent: Thursday, August 3, 2023 5:00 PM
>
>
> > > Admin command is what is suitable for device management, including
> > features and configspace fields setup.
> >
> > I agree.
> >
> > But some configuration such as mac, ip(eswitch rule) for vfs that are suitable
> > for the admin queue?
> Mac, why not.

Mac is the concept of the virtio-net.
How do abstract it? Or a admin queue command VIRTIO_ADMIN_CMD_NET_MAC_SET?

>
> Eswith rules should be programmed through the flow vq, that we are working with Heng, Satananda and David.

I know you are doing for the n-tuple receive flow filters.

Here I mean we want to limit the ip of the VF. In the cloud case, the vm is
untrust, we should force the vm that it just can use the specified ip.

Then can we configure the ip of the vfs via the admin queue?

Thanks.

> So, a PF or a switching device (new virtio device type) will have the flowvq as well.
>
>
> This publicly archived list offers a means to provide input to the
> OASIS Virtual I/O Device (VIRTIO) TC.
>
> In order to verify user consent to the Feedback License terms and
> to minimize spam in the list archive, subscription is required
> before posting.
>
> Subscribe: virtio-comment-subscribe@lists.oasis-open.org
> Unsubscribe: virtio-comment-unsubscribe@lists.oasis-open.org
> List help: virtio-comment-help@lists.oasis-open.org
> List archive: https://lists.oasis-open.org/archives/virtio-comment/
> Feedback License: https://www.oasis-open.org/who/ipr/feedback_license.pdf
> List Guidelines: https://www.oasis-open.org/policies-guidelines/mailing-lists
> Committee: https://www.oasis-open.org/committees/virtio/
> Join OASIS: https://www.oasis-open.org/join/