public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dragos Tatulea <dtatulea@nvidia.com>
To: Carlos Bilbao <cbilbao@digitalocean.com>,
	eli@mellanox.com, mst@redhat.com, jasowang@redhat.com,
	xuanzhuo@linux.alibaba.com
Cc: virtualization@lists.linux-foundation.org,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	kvm@vger.kernel.org, eperezma@redhat.com, sashal@kernel.org,
	yuehaibing@huawei.com, steven.sistare@oracle.com
Subject: Re: [RFC] Why is set_config not supported in mlx5_vnet?
Date: Mon, 26 Aug 2024 11:06:09 +0200	[thread overview]
Message-ID: <afcbf041-7613-48e6-8088-9d52edd907ff@nvidia.com> (raw)
In-Reply-To: <33feec1a-2c5d-46eb-8d66-baa802130d7f@digitalocean.com>



On 23.08.24 18:54, Carlos Bilbao wrote:
> Hello,
> 
> I'm debugging my vDPA setup, and when using ioctl to retrieve the
> configuration, I noticed that it's running in half duplex mode:
> 
> Configuration data (24 bytes):
>   MAC address: (Mac address)
>   Status: 0x0001
>   Max virtqueue pairs: 8
>   MTU: 1500
>   Speed: 0 Mb
>   Duplex: Half Duplex
>   RSS max key size: 0
>   RSS max indirection table length: 0
>   Supported hash types: 0x00000000
> 
> I believe this might be contributing to the underperformance of vDPA.
mlx5_vdpa vDPA devicess currently do not support the VIRTIO_NET_F_SPEED_DUPLEX
feature which reports speed and duplex. You can check the state on the
PF.


> While looking into how to change this option for Mellanox, I read the following
> kernel code in mlx5_vnet.c:
> 
> static void mlx5_vdpa_set_config(struct vdpa_device *vdev, unsigned int offset, const void *buf,
>                  unsigned int len)
> {
>     /* not supported */
> }
> 
> I was wondering why this is the case.
TBH, I don't know why it was not added. But in general, the control VQ is the
better way as it's dynamic.

> Is there another way for me to change
> these configuration settings?
> 
The configuration is done using control VQ for most things (MTU, MAC, VQs,
etc). Make sure that you have the CTRL_VQ feature set (should be on by
default). It should appear in `vdpa mgmtdev show` and `vdpa dev config
show`.

Thanks,
Dragos

  parent reply	other threads:[~2024-08-26  9:06 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-23 16:54 [RFC] Why is set_config not supported in mlx5_vnet? Carlos Bilbao
2024-08-26  1:48 ` Andrew Lunn
2024-08-26  9:06 ` Dragos Tatulea [this message]
2024-08-26 14:24   ` Andrew Lunn
2024-08-26 16:10     ` Dragos Tatulea
2024-08-27  2:03       ` Jason Wang
2024-08-27 16:54         ` Dragos Tatulea
2024-08-28  1:52           ` Jason Wang
2024-08-28 17:28           ` Carlos Bilbao
2024-08-26 14:26   ` Carlos Bilbao
2024-08-26 15:53     ` Dragos Tatulea
2024-08-26 19:22       ` Carlos Bilbao
2024-08-27  2:07         ` Jason Wang
2024-08-27 17:36           ` Carlos Bilbao
2024-08-28 15:16           ` Carlos Bilbao

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=afcbf041-7613-48e6-8088-9d52edd907ff@nvidia.com \
    --to=dtatulea@nvidia.com \
    --cc=cbilbao@digitalocean.com \
    --cc=eli@mellanox.com \
    --cc=eperezma@redhat.com \
    --cc=jasowang@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mst@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=sashal@kernel.org \
    --cc=steven.sistare@oracle.com \
    --cc=virtualization@lists.linux-foundation.org \
    --cc=xuanzhuo@linux.alibaba.com \
    --cc=yuehaibing@huawei.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