All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Ronak Doshi <doshir@vmware.com>
Cc: netdev@vger.kernel.org, pv-drivers@vmware.com,
	davem@davemloft.net, kuba@kernel.org, gyang@vmware.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next] vmxnet3: fix minimum vectors alloc issue
Date: Thu, 09 Dec 2021 02:10:09 +0000	[thread overview]
Message-ID: <163901580943.22374.8688111636911326175.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20211207081737.14000-1-doshir@vmware.com>

Hello:

This patch was applied to netdev/net.git (master)
by Jakub Kicinski <kuba@kernel.org>:

On Tue, 7 Dec 2021 00:17:37 -0800 you wrote:
> 'Commit 39f9895a00f4 ("vmxnet3: add support for 32 Tx/Rx queues")'
> added support for 32Tx/Rx queues. Within that patch, value of
> VMXNET3_LINUX_MIN_MSIX_VECT was updated.
> 
> However, there is a case (numvcpus = 2) which actually requires 3
> intrs which matches VMXNET3_LINUX_MIN_MSIX_VECT which then is
> treated as failure by stack to allocate more vectors. This patch
> fixes this issue.
> 
> [...]

Here is the summary with links:
  - [net-next] vmxnet3: fix minimum vectors alloc issue
    https://git.kernel.org/netdev/net/c/f71ef02f1a4a

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



      reply	other threads:[~2021-12-09  2:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-07  8:17 [PATCH net-next] vmxnet3: fix minimum vectors alloc issue Ronak Doshi
2021-12-09  2:10 ` 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=163901580943.22374.8688111636911326175.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=doshir@vmware.com \
    --cc=gyang@vmware.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pv-drivers@vmware.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.