Linux virtualization list
 help / color / mirror / Atom feed
From: Stefano Garzarella <sgarzare@redhat.com>
To: Parav Pandit <parav@nvidia.com>
Cc: elic@nvidia.com, mst@redhat.com,
	virtualization@lists.linux-foundation.org
Subject: Re: [PATCH linux-next v7 4/8] vdpa: Enable user to set mac and mtu of vdpa device
Date: Wed, 27 Oct 2021 09:40:23 +0200	[thread overview]
Message-ID: <20211027074023.jt3nppb6cr3wxukf@steredhat> (raw)
In-Reply-To: <20211026175519.87795-5-parav@nvidia.com>

On Tue, Oct 26, 2021 at 08:55:15PM +0300, Parav Pandit via Virtualization wrote:
>$ vdpa dev add name bar mgmtdev vdpasim_net mac 00:11:22:33:44:55 mtu 9000
>
>$ vdpa dev config show
>bar: mac 00:11:22:33:44:55 link up link_announce false mtu 9000
>
>$ vdpa dev config show -jp
>{
>    "config": {
>        "bar": {
>            "mac": "00:11:22:33:44:55",
>            "link ": "up",
>            "link_announce ": false,
>            "mtu": 9000,
>        }
>    }
>}
>
>Signed-off-by: Parav Pandit <parav@nvidia.com>
>Reviewed-by: Eli Cohen <elic@nvidia.com>
>Acked-by: Jason Wang <jasowang@redhat.com>
>
>---
>changelog:
>v5->v6:
> - fixed typo of device
>v4->v5:
> - added comment for checking device capabilities
>v3->v4:
> - provide config attributes during device addition time
>---
> drivers/vdpa/ifcvf/ifcvf_main.c      |  3 ++-
> drivers/vdpa/mlx5/net/mlx5_vnet.c    |  3 ++-
> drivers/vdpa/vdpa.c                  | 38 ++++++++++++++++++++++++++--
> drivers/vdpa/vdpa_sim/vdpa_sim_blk.c |  3 ++-
> drivers/vdpa/vdpa_sim/vdpa_sim_net.c |  3 ++-
> drivers/vdpa/vdpa_user/vduse_dev.c   |  3 ++-
> include/linux/vdpa.h                 | 17 ++++++++++++-
> 7 files changed, 62 insertions(+), 8 deletions(-)

Reviewed-by: Stefano Garzarella <sgarzare@redhat.com>

_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization

  reply	other threads:[~2021-10-27  7:40 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-26 17:55 [PATCH linux-next v7 0/8] vdpa: enable user to set mac, mtu Parav Pandit via Virtualization
2021-10-26 17:55 ` [PATCH linux-next v7 1/8] vdpa: Introduce and use vdpa device get, set config helpers Parav Pandit via Virtualization
2021-10-26 17:55 ` [PATCH linux-next v7 2/8] vdpa: Introduce query of device config layout Parav Pandit via Virtualization
2021-10-26 17:55 ` [PATCH linux-next v7 3/8] vdpa: Use kernel coding style for structure comments Parav Pandit via Virtualization
2021-10-26 17:55 ` [PATCH linux-next v7 4/8] vdpa: Enable user to set mac and mtu of vdpa device Parav Pandit via Virtualization
2021-10-27  7:40   ` Stefano Garzarella [this message]
2021-10-26 17:55 ` [PATCH linux-next v7 5/8] vdpa_sim_net: Enable user to set mac address and mtu Parav Pandit via Virtualization
2021-10-26 17:55 ` [PATCH linux-next v7 6/8] vdpa/mlx5: Fix clearing of VIRTIO_NET_F_MAC feature bit Parav Pandit via Virtualization
2021-10-27  6:04   ` Jason Wang
2021-10-26 17:55 ` [PATCH linux-next v7 7/8] vdpa/mlx5: Support configuration of MAC Parav Pandit via Virtualization
2021-10-26 17:55 ` [PATCH linux-next v7 8/8] vdpa/mlx5: Forward only packets with allowed MAC address Parav Pandit via Virtualization
2021-10-27  6:14   ` 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=20211027074023.jt3nppb6cr3wxukf@steredhat \
    --to=sgarzare@redhat.com \
    --cc=elic@nvidia.com \
    --cc=mst@redhat.com \
    --cc=parav@nvidia.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox