From: Jakub Kicinski <kuba@kernel.org>
To: Samiullah Khawaja <skhawaja@google.com>
Cc: "David S . Miller " <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
almasrymina@google.com, netdev@vger.kernel.org
Subject: Re: [PATCH net-next v2 0/4] Add support to do threaded napi busy poll
Date: Thu, 23 Jan 2025 17:24:25 -0800 [thread overview]
Message-ID: <20250123172425.63279bda@kernel.org> (raw)
In-Reply-To: <20250123231236.2657321-1-skhawaja@google.com>
On Thu, 23 Jan 2025 23:12:32 +0000 Samiullah Khawaja wrote:
> Extend the already existing support of threaded napi poll to do continuous
> busy polling.
## Form letter - net-next-closed
The merge window for v6.14 has begun and we have already posted our pull
request. Therefore net-next is closed for new drivers, features, code
refactoring and optimizations. We are currently accepting bug fixes only.
Please repost when net-next reopens after Feb 3rd.
RFC patches sent for review only are obviously welcome at any time.
See: https://www.kernel.org/doc/html/next/process/maintainer-netdev.html#development-cycle
--
pw-bot: defer
pv-bot: closed
next prev parent reply other threads:[~2025-01-24 1:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-23 23:12 [PATCH net-next v2 0/4] Add support to do threaded napi busy poll Samiullah Khawaja
2025-01-23 23:12 ` [PATCH net-next v2 1/4] Add support to set napi threaded for individual napi Samiullah Khawaja
2025-01-23 23:12 ` [PATCH net-next v2 2/4] net: Create separate gro_flush helper function Samiullah Khawaja
2025-01-23 23:12 ` [PATCH net-next v2 3/4] Extend napi threaded polling to allow kthread based busy polling Samiullah Khawaja
2025-01-24 13:18 ` kernel test robot
2025-01-23 23:12 ` [PATCH net-next v2 4/4] selftests: Add napi threaded busy poll test in `busy_poller` Samiullah Khawaja
2025-01-24 1:24 ` Jakub Kicinski [this message]
2025-01-27 17:06 ` [PATCH net-next v2 0/4] Add support to do threaded napi busy poll Joe Damato
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=20250123172425.63279bda@kernel.org \
--to=kuba@kernel.org \
--cc=almasrymina@google.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=skhawaja@google.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.