From: Philo Lu <lulie@linux.alibaba.com>
To: Joe Damato <jdamato@fastly.com>,
netdev@vger.kernel.org, mst@redhat.com, jasowang@redhat.com,
xuanzhuo@linux.alibaba.com, eperezma@redhat.com,
andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, andrew@daynix.com,
virtualization@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net 4/4] virtio_net: Update rss when set queue
Date: Wed, 6 Nov 2024 09:28:01 +0800 [thread overview]
Message-ID: <a10d6eda-d03f-42ea-af89-be0d798b5608@linux.alibaba.com> (raw)
In-Reply-To: <ZyqAovoIOYkNvtys@LQ3V64L9R2>
On 2024/11/6 04:31, Joe Damato wrote:
> On Mon, Nov 04, 2024 at 04:57:06PM +0800, Philo Lu wrote:
>> RSS configuration should be updated with queue number. In particular, it
>> should be updated when (1) rss enabled and (2) default rss configuration
>> is used without user modification.
>>
>> During rss command processing, device updates queue_pairs using
>> rss.max_tx_vq. That is, the device updates queue_pairs together with
>> rss, so we can skip the sperate queue_pairs update
>> (VIRTIO_NET_CTRL_MQ_VQ_PAIRS_SET below) and return directly.
>>
>> Also remove the `vi->has_rss ?` check when setting vi->rss.max_tx_vq,
>> because this is not used in the other hash_report case.
>>
>> Fixes: c7114b1249fa ("drivers/net/virtio_net: Added basic RSS support.")
>> Signed-off-by: Philo Lu <lulie@linux.alibaba.com>
>> Signed-off-by: Xuan Zhuo <xuanzhuo@linux.alibaba.com>
>> ---
>> drivers/net/virtio_net.c | 65 +++++++++++++++++++++++++++++++---------
>> 1 file changed, 51 insertions(+), 14 deletions(-)
>>
>> diff --git a/drivers/net/virtio_net.c b/drivers/net/virtio_net.c
>> index 59d9fdf562e0..189afad3ffaa 100644
>> --- a/drivers/net/virtio_net.c
>> +++ b/drivers/net/virtio_net.c
>> @@ -3394,15 +3394,59 @@ static void virtnet_ack_link_announce(struct virtnet_info *vi)
>> dev_warn(&vi->dev->dev, "Failed to ack link announce.\n");
>> }
>>
>> +static bool virtnet_commit_rss_command(struct virtnet_info *vi);
>> +
>> +static void virtnet_rss_update_by_qpairs(struct virtnet_info *vi, u16 queue_pairs)
>> +{
>> + u32 indir_val = 0;
>> + int i = 0;
>> +
>> + for (; i < vi->rss_indir_table_size; ++i) {
>> + indir_val = ethtool_rxfh_indir_default(i, queue_pairs);
>> + vi->rss.indirection_table[i] = indir_val;
>> + }
>> + vi->rss.max_tx_vq = queue_pairs;
>> +}
>> +
>> static int virtnet_set_queues(struct virtnet_info *vi, u16 queue_pairs)
>> {
>> struct virtio_net_ctrl_mq *mq __free(kfree) = NULL;
>> - struct scatterlist sg;
>> + struct virtio_net_ctrl_rss old_rss;
>> struct net_device *dev = vi->dev;
>> + struct scatterlist sg;
>>
>> if (!vi->has_cvq || !virtio_has_feature(vi->vdev, VIRTIO_NET_F_MQ))
>> return 0;
>>
>> + /* Firstly check if we need update rss. Do updating if both (1) rss enabled and
>> + * (2) no user configuration.
>> + *
>> + * During rss command processing, device updates queue_pairs using rss.max_tx_vq. That is,
>> + * the device updates queue_pairs together with rss, so we can skip the sperate queue_pairs
>> + * update (VIRTIO_NET_CTRL_MQ_VQ_PAIRS_SET below) and return directly.
>> + */
>> + if (vi->has_rss && !netif_is_rxfh_configured(dev)) {
>
> Does there need to be an error case when:
>
> vi->has_rss && netif_is_rxfh_configured(dev)
>
> to return EINVAL? I noted that other drivers don't let users adjust
> the queue count and return error in this case.
>
In fact, there are 2 possible cases if users have adjusted rss,
depending on the total queue pairs used in the indirection table (x),
and the requested new queue count (y).
Case A: If y < x, it's illegal and will be rejected by
ethtool_check_max_channel().
Case B: If x <= y, we only adjust the queue number without touching the
rss configuration set by users.
So I don't think it necessary to add the check (if the above processing
is agreed).
Thanks for your review, Joe.
--
Philo
next prev parent reply other threads:[~2024-11-06 1:28 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-04 8:57 [PATCH net 0/4] virtio_net: Make RSS interact properly with queue number Philo Lu
2024-11-04 8:57 ` [PATCH net 1/4] virtio_net: Support dynamic rss indirection table size Philo Lu
2024-11-05 20:27 ` Joe Damato
2024-11-04 8:57 ` [PATCH net 2/4] virtio_net: Add hash_key_length check Philo Lu
2024-11-05 20:28 ` Joe Damato
2024-11-04 8:57 ` [PATCH net 3/4] virtio_net: Sync rss config to device when virtnet_probe Philo Lu
2024-11-05 20:29 ` Joe Damato
2024-11-04 8:57 ` [PATCH net 4/4] virtio_net: Update rss when set queue Philo Lu
2024-11-05 20:31 ` Joe Damato
2024-11-06 1:28 ` Philo Lu [this message]
2024-11-07 11:39 ` Paolo Abeni
2024-11-06 8:58 ` [PATCH net 0/4] virtio_net: Make RSS interact properly with queue number Xuan Zhuo
2024-11-11 1:30 ` Jason Wang
2024-11-06 9:31 ` Michael S. Tsirkin
2024-11-07 11:50 ` patchwork-bot+netdevbpf
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=a10d6eda-d03f-42ea-af89-be0d798b5608@linux.alibaba.com \
--to=lulie@linux.alibaba.com \
--cc=andrew+netdev@lunn.ch \
--cc=andrew@daynix.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=eperezma@redhat.com \
--cc=jasowang@redhat.com \
--cc=jdamato@fastly.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=virtualization@lists.linux.dev \
--cc=xuanzhuo@linux.alibaba.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;
as well as URLs for NNTP newsgroup(s).