From: Xuan Zhuo <xuanzhuo@linux.alibaba.com>
To: Parav Pandit <parav@nvidia.com>
Cc: Jason Wang <jasowang@redhat.com>,
"Zhu, Lingshan" <lingshan.zhu@intel.com>,
"virtio-comment@lists.oasis-open.org"
<virtio-comment@lists.oasis-open.org>,
"Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: RE: [virtio-comment] About the plan of Admin Queue
Date: Wed, 5 Jul 2023 12:38:47 +0800 [thread overview]
Message-ID: <1688531927.09141-3-xuanzhuo@linux.alibaba.com> (raw)
In-Reply-To: <PH0PR12MB5481F6EA4699382DB041A880DC2EA@PH0PR12MB5481.namprd12.prod.outlook.com>
On Tue, 4 Jul 2023 13:15:23 +0000, Parav Pandit <parav@nvidia.com> wrote:
>
> > From: Xuan Zhuo <xuanzhuo@linux.alibaba.com>
> > Sent: Tuesday, July 4, 2023 8:14 AM
>
> > But in the scenario I mentioned, the vendor's management software runs on
> > the DPU, and all hosts belong to the user.
> >
> How did vendor management software configure the parameters on the src side?
> Same channel can be used on destination side, right?
Yes.
>
> > The problem we want to solve is that this user may want 1000 network cards. So
> > it must use VFs as a network cards. It cannot and will not configure detailed NIC
> > properties based on the admin queue.
> >
> Sure.
> It will not.
> The idea is to use same out of band channel as what is used on the src side, also on the destination side.
Sure.
Thanks.
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/
prev parent reply other threads:[~2023-07-05 4:39 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-20 6:44 [virtio-comment] About the plan of Admin Queue Xuan Zhuo
2023-06-20 8:11 ` Zhu, Lingshan
2023-06-30 5:54 ` Xuan Zhuo
2023-06-30 6:19 ` Zhu, Lingshan
2023-06-30 7:46 ` Xuan Zhuo
2023-06-30 7:54 ` Zhu, Lingshan
2023-06-30 7:56 ` Xuan Zhuo
2023-06-30 8:32 ` Zhu, Lingshan
2023-06-30 9:07 ` Zhu, Lingshan
2023-06-30 9:14 ` Xuan Zhuo
2023-06-30 10:33 ` Zhu, Lingshan
2023-06-30 11:35 ` Parav Pandit
2023-07-03 4:29 ` Zhu, Lingshan
2023-07-03 5:54 ` Xuan Zhuo
2023-07-03 8:01 ` Zhu, Lingshan
2023-07-03 8:21 ` Xuan Zhuo
2023-07-03 8:23 ` Zhu, Lingshan
2023-07-27 2:30 ` Xuan Zhuo
2023-07-27 3:56 ` Zhu, Lingshan
2023-07-27 6:09 ` Xuan Zhuo
2023-07-27 6:17 ` Zhu, Lingshan
2023-07-27 6:20 ` Xuan Zhuo
2023-07-27 8:03 ` Jason Wang
2023-07-27 8:07 ` Xuan Zhuo
2023-07-27 8:28 ` Jason Wang
2023-07-27 8:30 ` Xuan Zhuo
2023-07-27 8:56 ` Jason Wang
2023-07-27 9:01 ` Xuan Zhuo
[not found] ` <aafe1885-0ec2-66ca-4511-f2606bc881ee@gmail.com>
2023-08-02 6:13 ` Xuan Zhuo
2023-08-02 6:15 ` Jason Wang
2023-08-02 6:34 ` Xuan Zhuo
2023-08-02 6:53 ` Jason Wang
2023-08-02 6:55 ` Xuan Zhuo
2023-07-28 6:09 ` Xuan Zhuo
2023-07-31 1:20 ` Jason Wang
2023-07-31 2:02 ` Parav Pandit
2023-07-03 8:10 ` Jason Wang
2023-07-03 8:20 ` Xuan Zhuo
2023-07-03 13:05 ` Michael S. Tsirkin
2023-07-03 13:06 ` Parav Pandit
2023-07-03 20:38 ` Parav Pandit
2023-07-04 3:48 ` Zhu, Lingshan
2023-07-04 12:11 ` Xuan Zhuo
2023-07-04 12:14 ` Xuan Zhuo
2023-07-04 13:15 ` Parav Pandit
2023-07-05 4:30 ` Xuan Zhuo
2023-07-05 4:35 ` Parav Pandit
2023-07-05 4:36 ` Xuan Zhuo
2023-07-05 4:38 ` Xuan Zhuo [this message]
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=1688531927.09141-3-xuanzhuo@linux.alibaba.com \
--to=xuanzhuo@linux.alibaba.com \
--cc=jasowang@redhat.com \
--cc=lingshan.zhu@intel.com \
--cc=mst@redhat.com \
--cc=parav@nvidia.com \
--cc=virtio-comment@lists.oasis-open.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.