From: patchwork-bot+netdevbpf@kernel.org
To: Lukas Wunner <lukas@wunner.de>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, netdev@vger.kernel.org,
p.rosenberger@kunbus.com, hanzhi09@gmail.com
Subject: Re: [PATCH net-next] net: enc28j60: Use threaded interrupt instead of workqueue
Date: Fri, 12 May 2023 01:10:21 +0000 [thread overview]
Message-ID: <168385382182.13567.17908827053703617655.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <342380d989ce26bc49f0e5d45fbb0416a5f7809f.1683606193.git.lukas@wunner.de>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 9 May 2023 06:28:56 +0200 you wrote:
> From: Philipp Rosenberger <p.rosenberger@kunbus.com>
>
> The Microchip ENC28J60 SPI Ethernet driver schedules a work item from
> the interrupt handler because accesses to the SPI bus may sleep.
>
> On PREEMPT_RT (which forces interrupt handling into threads) this
> old-fashioned approach unnecessarily increases latency because an
> interrupt results in first waking the interrupt thread, then scheduling
> the work item. So, a double indirection to handle an interrupt.
>
> [...]
Here is the summary with links:
- [net-next] net: enc28j60: Use threaded interrupt instead of workqueue
https://git.kernel.org/netdev/net-next/c/995585ecdf42
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:[~2023-05-12 1:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-09 4:28 [PATCH net-next] net: enc28j60: Use threaded interrupt instead of workqueue Lukas Wunner
2023-05-09 8:06 ` Leon Romanovsky
2023-05-09 13:36 ` Lukas Wunner
2023-05-09 13:56 ` Leon Romanovsky
2023-05-11 2:05 ` Jakub Kicinski
2023-05-11 6:36 ` Paolo Abeni
2023-05-11 6:59 ` Leon Romanovsky
2023-05-11 15:51 ` Jakub Kicinski
2023-05-11 18:48 ` Leon Romanovsky
2023-05-09 9:22 ` Piotr Raczynski
2023-05-12 1: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=168385382182.13567.17908827053703617655.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hanzhi09@gmail.com \
--cc=kuba@kernel.org \
--cc=lukas@wunner.de \
--cc=netdev@vger.kernel.org \
--cc=p.rosenberger@kunbus.com \
--cc=pabeni@redhat.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).