From: Parav Pandit <parav@nvidia.com>
To: Xuan Zhuo <xuanzhuo@linux.alibaba.com>
Cc: "virtio-dev@lists.oasis-open.org"
<virtio-dev@lists.oasis-open.org>,
"virtio-comment@lists.oasis-open.org"
<virtio-comment@lists.oasis-open.org>,
"Michael S. Tsirkin" <mst@redhat.com>,
Jason Wang <jasowang@redhat.com>
Subject: RE: RE: RE: RE: RE: RE: [virtio-comment] RE: RE: RE: RE: [RFC] virtio-net: support access and control the member devices
Date: Tue, 8 Aug 2023 06:56:59 +0000 [thread overview]
Message-ID: <PH0PR12MB5481E384B9D13E1B0B37D335DC0DA@PH0PR12MB5481.namprd12.prod.outlook.com> (raw)
In-Reply-To: <1691477071.6894073-9-xuanzhuo@linux.alibaba.com>
> From: Xuan Zhuo <xuanzhuo@linux.alibaba.com>
> Sent: Tuesday, August 8, 2023 12:15 PM
> > At that point, there may be two functions, PF and switching PF, switching PF
> filters the traffic of the PF.
> >
> > Anyways, I am just not finding it useful enough at current point in time for us
> as far mature alternatives exist that users are comfortable with.
> > I would like to listen to Xuan if they really have use case for having switching
> PF as virtio object or not.
>
> So the switching PF is that there is a switch under all devices?
>
Right. Switching PF controls the ports of the PF and VFs.
> If we use the switch rx/tx filter for the ip restriction, the PF with switch is
> enough, we do not need the ip restirction for the PF.
I understood that you for some reason do not need restrictions for the PF.
I do not know why you don't need it. :)
Most cloud setups that I came across so far, needs it, but ok...
The design for the switch object needs to cover the PF as well, even though it may not be done initially.
(hint: an abstraction of switch port to be done, instead of doing things directly on the group member id).
We are seeing use cases reducing of having switch located on the PF for its VFs.
So please reconsider.
I remember you mentioned in past in other thread, that mac etc is controlled from the infrastructure side.
So, I repeatedly ask if you _really_ need to have the switch object as part of the owner PF or not.
Which sort of contradicts with locating the administrative switch on the owner PF.
If it does, flow filters vq that is being worked with Heng, Satananda, David and others seems right direction to implement simple->complex switch object progressively.
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/
next prev parent reply other threads:[~2023-08-08 6:57 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-03 8:31 [virtio-comment] [RFC] virtio-net: support access and control the member devices Xuan Zhuo
2023-08-03 9:44 ` [virtio-comment] " Michael S. Tsirkin
2023-08-03 9:45 ` [virtio-comment] " Parav Pandit
2023-08-03 10:52 ` [virtio-comment] " Xuan Zhuo
2023-08-03 10:59 ` [virtio-comment] " Parav Pandit
2023-08-03 11:04 ` [virtio-comment] " Xuan Zhuo
2023-08-03 11:15 ` [virtio-comment] " Parav Pandit
2023-08-03 11:18 ` [virtio-comment] " Xuan Zhuo
2023-08-03 11:25 ` [virtio-comment] " Parav Pandit
2023-08-03 11:30 ` [virtio-comment] " Xuan Zhuo
2023-08-03 11:39 ` [virtio-comment] " Parav Pandit
2023-08-03 11:41 ` Xuan Zhuo
2023-08-03 13:15 ` Parav Pandit
2023-08-03 17:03 ` Satananda Burla
2023-08-04 3:29 ` Jason Wang
2023-08-04 4:22 ` Parav Pandit
2023-08-04 6:18 ` Xuan Zhuo
2023-08-04 6:37 ` Parav Pandit
2023-08-04 6:54 ` Xuan Zhuo
2023-08-04 7:26 ` Parav Pandit
2023-08-04 7:44 ` Xuan Zhuo
2023-08-04 10:33 ` Michael S. Tsirkin
2023-08-04 12:49 ` Parav Pandit
2023-08-04 14:07 ` Michael S. Tsirkin
2023-08-04 14:12 ` Parav Pandit
2023-08-06 10:32 ` Michael S. Tsirkin
2023-08-07 6:02 ` Xuan Zhuo
2023-08-08 2:18 ` Jason Wang
2023-08-08 2:36 ` Xuan Zhuo
2023-08-08 3:09 ` Jason Wang
2023-08-08 3:13 ` Xuan Zhuo
2023-08-08 3:16 ` Parav Pandit
2023-08-08 3:50 ` Jason Wang
2023-08-08 4:16 ` Parav Pandit
2023-08-08 4:33 ` Jason Wang
2023-08-08 4:37 ` Parav Pandit
2023-08-08 5:21 ` Jason Wang
2023-08-08 6:16 ` Xuan Zhuo
2023-08-08 6:44 ` Xuan Zhuo
2023-08-08 6:56 ` Parav Pandit [this message]
2023-08-08 4:00 ` Xuan Zhuo
2023-08-08 4:11 ` Parav Pandit
2023-08-08 4:16 ` Xuan Zhuo
2023-08-08 4:34 ` Parav Pandit
2023-08-08 6:02 ` Xuan Zhuo
2023-08-08 4:18 ` Satananda Burla
2023-08-04 3:31 ` [virtio-comment] " Jason Wang
2023-08-04 4:05 ` [virtio-comment] " Parav Pandit
2023-08-08 2:30 ` [virtio-comment] " Jason Wang
2023-08-03 10:23 ` [virtio-comment] " Parav Pandit
2023-08-03 11:05 ` [virtio-comment] " Xuan Zhuo
2023-08-03 11:13 ` [virtio-comment] " Parav Pandit
2023-08-03 11:15 ` [virtio-comment] " Xuan Zhuo
2023-08-03 11:21 ` [virtio-comment] " Parav Pandit
2023-08-03 11:27 ` [virtio-comment] " Xuan Zhuo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=PH0PR12MB5481E384B9D13E1B0B37D335DC0DA@PH0PR12MB5481.namprd12.prod.outlook.com \
--to=parav@nvidia.com \
--cc=jasowang@redhat.com \
--cc=mst@redhat.com \
--cc=virtio-comment@lists.oasis-open.org \
--cc=virtio-dev@lists.oasis-open.org \
--cc=xuanzhuo@linux.alibaba.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).