public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel•org
To: Philo Lu <lulie@linux•alibaba.com>
Cc: 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 0/4] virtio_net: Make RSS interact properly with queue number
Date: Thu, 07 Nov 2024 11:50:30 +0000	[thread overview]
Message-ID: <173098023002.1629022.1863004983853146136.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241104085706.13872-1-lulie@linux.alibaba.com>

Hello:

This series was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat•com>:

On Mon,  4 Nov 2024 16:57:02 +0800 you wrote:
> With this patch set, RSS updates with queue_pairs changing:
> - When virtnet_probe, init default rss and commit
> - When queue_pairs changes _without_ user rss configuration, update rss
>   with the new queue number
> - When queue_pairs changes _with_ user rss configuration, keep rss as user
>   configured
> 
> [...]

Here is the summary with links:
  - [net,1/4] virtio_net: Support dynamic rss indirection table size
    https://git.kernel.org/netdev/net/c/86a48a00efdf
  - [net,2/4] virtio_net: Add hash_key_length check
    https://git.kernel.org/netdev/net/c/3f7d9c1964fc
  - [net,3/4] virtio_net: Sync rss config to device when virtnet_probe
    https://git.kernel.org/netdev/net/c/dc749b7b0608
  - [net,4/4] virtio_net: Update rss when set queue
    https://git.kernel.org/netdev/net/c/50bfcaedd78e

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2024-11-07 11:50 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
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 [this message]

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=173098023002.1629022.1863004983853146136.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel$(echo .)org \
    --cc=andrew+netdev@lunn$(echo .)ch \
    --cc=andrew@daynix$(echo .)com \
    --cc=davem@davemloft$(echo .)net \
    --cc=edumazet@google$(echo .)com \
    --cc=eperezma@redhat$(echo .)com \
    --cc=jasowang@redhat$(echo .)com \
    --cc=kuba@kernel$(echo .)org \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=lulie@linux$(echo .)alibaba.com \
    --cc=mst@redhat$(echo .)com \
    --cc=netdev@vger$(echo .)kernel.org \
    --cc=pabeni@redhat$(echo .)com \
    --cc=virtualization@lists$(echo .)linux.dev \
    --cc=xuanzhuo@linux$(echo .)alibaba.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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