From: Jason Wang <jasowang@redhat.com>
To: Adrian Moreno <amorenoz@redhat.com>,
Parav Pandit <parav@nvidia.com>,
virtualization@lists.linux-foundation.org,
netdev@vger.kernel.org, dsahern@gmail.com,
stephen@networkplumber.org, mst@redhat.com
Subject: Re: [PATCH iproute2-next v3 0/5] Add vdpa device management tool
Date: Fri, 5 Feb 2021 11:40:36 +0800 [thread overview]
Message-ID: <0017c3d7-9b04-d26c-94e2-485e4da6a778@redhat.com> (raw)
In-Reply-To: <1d1ff638-d498-6675-ead5-6e09213af3a8@redhat.com>
On 2021/2/4 下午7:15, Adrian Moreno wrote:
> Sorry I have not followed this work as close as I would have wanted.
> Some questions below.
>
> On 2/4/21 4:16 AM, Jason Wang wrote:
>> On 2021/2/2 下午6:35, Parav Pandit wrote:
>>> Linux vdpa interface allows vdpa device management functionality.
>>> This includes adding, removing, querying vdpa devices.
>>>
>>> vdpa interface also includes showing supported management devices
>>> which support such operations.
>>>
>>> This patchset includes kernel uapi headers and a vdpa tool.
>>>
>>> examples:
>>>
>>> $ vdpa mgmtdev show
>>> vdpasim:
>>> supported_classes net
>>>
>>> $ vdpa mgmtdev show -jp
>>> {
>>> "show": {
>>> "vdpasim": {
>>> "supported_classes": [ "net" ]
>>> }
>>> }
>>> }
>>>
> How can a user establish the relationship between a mgmtdev and it's parent
> device (pci vf, sf, etc)?
Parav should know more but I try to answer.
I think there should be BDF information in the mgmtdev show command if
the parent is a PCI device, or we can simply show the parent here?
>
>>> Create a vdpa device of type networking named as "foo2" from
>>> the management device vdpasim_net:
>>>
>>> $ vdpa dev add mgmtdev vdpasim_net name foo2
>>>
> I guess this command will accept a 'type' parameter once more supported_classes
> are added?
This could be extended in the future.
>
> Also, will this tool also handle the vdpa driver binding or will the user handle
> that through the vdpa bus' sysfs interface?
I think not, it's the configuration below the vdpa bus. The sysfs should
be the only interface for managing driver binding.
Thanks
>
>>> Show the newly created vdpa device by its name:
>>> $ vdpa dev show foo2
>>> foo2: type network mgmtdev vdpasim_net vendor_id 0 max_vqs 2 max_vq_size 256
>>>
>>> $ vdpa dev show foo2 -jp
>>> {
>>> "dev": {
>>> "foo2": {
>>> "type": "network",
>>> "mgmtdev": "vdpasim_net",
>>> "vendor_id": 0,
>>> "max_vqs": 2,
>>> "max_vq_size": 256
>>> }
>>> }
>>> }
>>>
>>> Delete the vdpa device after its use:
>>> $ vdpa dev del foo2
>>>
>>> Patch summary:
>>> Patch-1 adds kernel headers for vdpa subsystem
>>> Patch-2 adds library routines for indent handling
>>> Patch-3 adds library routines for generic socket communication
>>> PAtch-4 adds library routine for number to string mapping
>>> Patch-5 adds vdpa tool
>>>
>>> Kernel headers are from the vhost kernel tree [1] from branch linux-next.
>>>
>>> [1] https://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git
>>>
>>> ---
>>
>> Adding Adrian to see if this looks good for k8s integration.
>>
>> Thanks
>>
> Thanks
_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization
next prev parent reply other threads:[~2021-02-05 3:40 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-22 11:26 [PATCH iproute2-next 0/2] Add vdpa device management tool Parav Pandit
2021-01-22 11:26 ` [PATCH iproute2-next 1/2] Add kernel headers Parav Pandit
2021-01-22 11:26 ` [PATCH iproute2-next 2/2] vdpa: Add vdpa tool Parav Pandit
2021-01-26 4:22 ` David Ahern
2021-01-26 13:26 ` Parav Pandit
2021-01-28 18:43 ` [PATCH iproute2-next v2 0/2] Add vdpa device management tool Parav Pandit
2021-01-28 18:43 ` [PATCH iproute2-next v2 1/2] Add kernel headers Parav Pandit
2021-01-28 18:43 ` [PATCH iproute2-next v2 2/2] vdpa: Add vdpa tool Parav Pandit
2021-01-29 3:23 ` Parav Pandit
2021-02-02 10:35 ` [PATCH iproute2-next v3 0/5] Add vdpa device management tool Parav Pandit
2021-02-02 10:35 ` [PATCH iproute2-next v3 1/5] Add kernel headers Parav Pandit
2021-02-04 1:37 ` David Ahern
2021-02-05 17:54 ` Parav Pandit
2021-02-02 10:35 ` [PATCH iproute2-next v3 2/5] utils: Add helper routines for indent handling Parav Pandit
2021-02-02 10:35 ` [PATCH iproute2-next v3 3/5] utils: Add generic socket helpers Parav Pandit
2021-02-02 10:35 ` [PATCH iproute2-next v3 4/5] utils: Add helper to map string to unsigned int Parav Pandit
2021-02-02 10:35 ` [PATCH iproute2-next v3 5/5] vdpa: Add vdpa tool Parav Pandit
2021-02-04 3:16 ` [PATCH iproute2-next v3 0/5] Add vdpa device management tool Jason Wang
2021-02-04 11:15 ` Adrian Moreno
2021-02-05 3:40 ` Jason Wang [this message]
2021-02-05 17:53 ` Parav Pandit
2021-02-05 18:06 ` Adrian Moreno
2021-02-05 18:07 ` Adrian Moreno
2021-02-05 18:10 ` [PATCH iproute2-next v4 " Parav Pandit
2021-02-05 18:10 ` [PATCH iproute2-next v4 1/5] Add kernel headers Parav Pandit
2021-02-08 15:47 ` David Ahern
2021-02-10 18:28 ` Parav Pandit
2021-02-05 18:10 ` [PATCH iproute2-next v4 2/5] utils: Add helper routines for indent handling Parav Pandit
2021-02-05 18:10 ` [PATCH iproute2-next v4 3/5] utils: Add generic socket helpers Parav Pandit
2021-02-05 18:10 ` [PATCH iproute2-next v4 4/5] utils: Add helper to map string to unsigned int Parav Pandit
2021-02-05 18:10 ` [PATCH iproute2-next v4 5/5] vdpa: Add vdpa tool Parav Pandit
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=0017c3d7-9b04-d26c-94e2-485e4da6a778@redhat.com \
--to=jasowang@redhat.com \
--cc=amorenoz@redhat.com \
--cc=dsahern@gmail.com \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=parav@nvidia.com \
--cc=stephen@networkplumber.org \
--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 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 NNTP newsgroup(s).