From: Jason Wang <jasowang@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Eli Cohen <elic@nvidia.com>,
"virtualization@lists.linux-foundation.org"
<virtualization@lists.linux-foundation.org>
Subject: Re: [PATCH linux-next v3 2/6] vdpa: Introduce query of device config layout
Date: Wed, 30 Jun 2021 11:46:59 +0800 [thread overview]
Message-ID: <bfa8915f-d119-91be-bfab-07856947f918@redhat.com> (raw)
In-Reply-To: <20210629153540-mutt-send-email-mst@kernel.org>
在 2021/6/30 上午4:01, Michael S. Tsirkin 写道:
> On Tue, Jun 29, 2021 at 11:41:54AM +0800, Jason Wang wrote:
>> 在 2021/6/29 上午6:39, Michael S. Tsirkin 写道:
>>> On Mon, Jun 28, 2021 at 01:03:20PM +0800, Jason Wang wrote:
>>>> So I think we need solve them all, but netlink is probably the wrong layer,
>>>> we need to solve them at virtio level and let netlink a transport for them
>>>> virtio uAPI/ABI.
>>> I'm not sure I follow. virtio defines VF to driver communication.
>>> This is PF to hypervisor. virtio simply does not cover it ATM.
>>
>> Note that this is not PF to hypervisor but the uAPI from userspace (vDPA
>> tool) to vDPA core.
>>
>> We had two choices.
>>
>> 1) tweak virtio uAPIs
>> 2) invent virtio specific uAPI in netlink
>>
>> 1) seems better.
>>
>> Thanks
>>
> Well things like setting mac aren't virtio specific.
> What are the virtio specific things you have in mind?
E.g max_virtqueue_pairs? Even if mac aren't virtio specific, the idea is
to build the device config which is virtio specific.
And we may have other devices like virtio-blk.
Thanks
>
_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization
next prev parent reply other threads:[~2021-06-30 3:47 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-16 19:11 [PATCH linux-next v3 0/6] vdpa: enable user to set mac, mtu Parav Pandit
2021-06-16 19:11 ` [PATCH linux-next v3 1/6] vdpa: Introduce and use vdpa device get, set config helpers Parav Pandit
2021-06-22 7:08 ` Jason Wang
2021-06-16 19:11 ` [PATCH linux-next v3 2/6] vdpa: Introduce query of device config layout Parav Pandit
2021-06-22 7:20 ` Jason Wang
2021-06-22 14:03 ` Parav Pandit
2021-06-23 4:08 ` Jason Wang
2021-06-23 4:22 ` Parav Pandit
2021-06-24 5:43 ` Jason Wang
2021-06-24 6:29 ` Parav Pandit
2021-06-24 7:05 ` Jason Wang
2021-06-24 7:59 ` Parav Pandit
2021-06-25 3:28 ` Jason Wang
2021-06-25 6:45 ` Parav Pandit
2021-06-28 5:03 ` Jason Wang
2021-06-28 10:56 ` Parav Pandit
2021-06-29 3:52 ` Jason Wang
2021-06-29 9:49 ` Parav Pandit
2021-06-30 4:31 ` Jason Wang
2021-06-30 6:03 ` Parav Pandit
2021-07-01 3:34 ` Jason Wang
2021-07-01 7:00 ` Parav Pandit
2021-07-01 7:43 ` Jason Wang
2021-07-02 6:04 ` Parav Pandit
2021-07-05 4:35 ` Jason Wang
2021-07-06 17:07 ` Parav Pandit
2021-07-07 4:03 ` Jason Wang
2021-06-28 22:39 ` Michael S. Tsirkin
2021-06-29 3:41 ` Jason Wang
2021-06-29 20:01 ` Michael S. Tsirkin
2021-06-30 3:46 ` Jason Wang [this message]
2021-06-16 19:11 ` [PATCH linux-next v3 3/6] vdpa: Enable user to set mac and mtu of vdpa device Parav Pandit
2021-06-22 7:43 ` Jason Wang
2021-06-22 14:09 ` Parav Pandit
2021-06-16 19:11 ` [PATCH linux-next v3 4/6] vdpa_sim_net: Enable user to set mac address and mtu Parav Pandit
2021-06-16 19:11 ` [PATCH linux-next v3 5/6] vdpa/mlx5: Support configuration of MAC Parav Pandit
2021-06-16 19:11 ` [PATCH linux-next v3 6/6] vdpa/mlx5: Forward only packets with allowed MAC address Parav Pandit
2021-08-05 9:57 ` [PATCH linux-next v3 0/6] vdpa: enable user to set mac, mtu Michael S. Tsirkin
2021-08-05 10:13 ` Parav Pandit via Virtualization
2021-08-05 12:05 ` Michael S. Tsirkin
2021-08-06 2:50 ` Jason Wang
2021-08-06 8:42 ` Michael S. Tsirkin
2021-08-06 8:55 ` Parav Pandit via Virtualization
2021-08-09 3:07 ` Jason Wang
2021-08-09 3:13 ` Parav Pandit via Virtualization
2021-08-09 3:29 ` Jason Wang
[not found] ` <20210809052121.GA209158@mtl-vdi-166.wap.labs.mlnx>
2021-08-09 5:42 ` Parav Pandit via Virtualization
[not found] ` <20210809055748.GA210406@mtl-vdi-166.wap.labs.mlnx>
2021-08-09 6:01 ` Parav Pandit via Virtualization
[not found] ` <20210809060746.GA210718@mtl-vdi-166.wap.labs.mlnx>
2021-08-09 6:10 ` Parav Pandit via Virtualization
2021-08-09 7:05 ` Jason Wang
2021-08-16 20:51 ` Michael S. Tsirkin
2021-08-09 9:40 ` Michael S. Tsirkin
2021-08-09 9:51 ` Parav Pandit via Virtualization
2021-08-16 20:54 ` Michael S. Tsirkin
2021-08-18 3:14 ` Parav Pandit via Virtualization
2021-08-18 4:31 ` Jason Wang
2021-08-18 4:36 ` Parav Pandit via Virtualization
2021-08-19 4:18 ` Jason Wang
2021-08-18 17:33 ` Michael S. Tsirkin
2021-08-19 4:22 ` Jason Wang
2021-08-19 5:23 ` Parav Pandit via Virtualization
2021-08-19 7:15 ` Jason Wang
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=bfa8915f-d119-91be-bfab-07856947f918@redhat.com \
--to=jasowang@redhat.com \
--cc=elic@nvidia.com \
--cc=mst@redhat.com \
--cc=virtualization@lists.linux-foundation.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.