From: patchwork-bot+netdevbpf@kernel.org
To: Aditya Garg <gargaditya@linux.microsoft.com>
Cc: kys@microsoft.com, haiyangz@microsoft.com, wei.liu@kernel.org,
decui@microsoft.com, longli@microsoft.com, andrew+netdev@lunn.ch,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, kotaranov@microsoft.com, horms@kernel.org,
ssengar@linux.microsoft.com, jacob.e.keller@intel.com,
dipayanroy@linux.microsoft.com, ernis@linux.microsoft.com,
shirazsaleem@microsoft.com, kees@kernel.org, sbhatta@marvell.com,
leitao@debian.org, netdev@vger.kernel.org,
linux-hyperv@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-rdma@vger.kernel.org, bpf@vger.kernel.org,
gargaditya@microsoft.com
Subject: Re: [PATCH net-next v3 0/2] net: mana: Avoid queue struct allocation failure under memory fragmentation
Date: Wed, 06 May 2026 02:30:33 +0000 [thread overview]
Message-ID: <177803463304.2357425.6242248508065592109.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260502074552.23857-1-gargaditya@linux.microsoft.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Sat, 2 May 2026 00:45:32 -0700 you wrote:
> The MANA driver can fail to load on systems with high memory
> utilization because several allocations in the queue setup paths
> require large physically contiguous blocks via kmalloc. Under memory
> fragmentation these high-order allocations may fail, preventing the
> driver from creating queues when opening the interface or when
> reconfiguring channels, ring parameters or MTU at runtime.
>
> [...]
Here is the summary with links:
- [net-next,v3,1/2] net: mana: Use per-queue allocation for tx_qp to reduce allocation size
https://git.kernel.org/netdev/net-next/c/d07efe5a6e64
- [net-next,v3,2/2] net: mana: Use kvmalloc for large RX queue and buffer allocations
https://git.kernel.org/netdev/net-next/c/3af0820c878e
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-05-06 2:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-02 7:45 [PATCH net-next v3 0/2] net: mana: Avoid queue struct allocation failure under memory fragmentation Aditya Garg
2026-05-02 7:45 ` [PATCH net-next v3 1/2] net: mana: Use per-queue allocation for tx_qp to reduce allocation size Aditya Garg
2026-05-02 7:45 ` [PATCH net-next v3 2/2] net: mana: Use kvmalloc for large RX queue and buffer allocations Aditya Garg
2026-05-06 2:30 ` 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=177803463304.2357425.6242248508065592109.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=bpf@vger.kernel.org \
--cc=davem@davemloft.net \
--cc=decui@microsoft.com \
--cc=dipayanroy@linux.microsoft.com \
--cc=edumazet@google.com \
--cc=ernis@linux.microsoft.com \
--cc=gargaditya@linux.microsoft.com \
--cc=gargaditya@microsoft.com \
--cc=haiyangz@microsoft.com \
--cc=horms@kernel.org \
--cc=jacob.e.keller@intel.com \
--cc=kees@kernel.org \
--cc=kotaranov@microsoft.com \
--cc=kuba@kernel.org \
--cc=kys@microsoft.com \
--cc=leitao@debian.org \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=longli@microsoft.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sbhatta@marvell.com \
--cc=shirazsaleem@microsoft.com \
--cc=ssengar@linux.microsoft.com \
--cc=wei.liu@kernel.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