All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: netdev@vger.kernel.org, davem@davemloft.net, kuba@kernel.org,
	tglx@linutronix.de
Subject: Re: [PATCH net-next] net/core: disable NET_RX_BUSY_POLL on PREEMPT_RT
Date: Fri, 01 Oct 2021 22:50:07 +0000	[thread overview]
Message-ID: <163312860747.19403.5188764825013993670.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20211001145841.2308454-1-bigeasy@linutronix.de>

Hello:

This patch was applied to netdev/net-next.git (refs/heads/master):

On Fri,  1 Oct 2021 16:58:41 +0200 you wrote:
> napi_busy_loop() disables preemption and performs a NAPI poll. We can't acquire
> sleeping locks with disabled preemption which would be required while
> __napi_poll() invokes the callback of the driver.
> 
> A threaded interrupt performing the NAPI-poll can be preempted on PREEMPT_RT.
> A RT thread on another CPU may observe NAPIF_STATE_SCHED bit set and busy-spin
> until it is cleared or its spin time runs out. Given it is the task with the
> highest priority it will never observe the NEED_RESCHED bit set.
> In this case the time is better spent by simply sleeping.
> 
> [...]

Here is the summary with links:
  - [net-next] net/core: disable NET_RX_BUSY_POLL on PREEMPT_RT
    https://git.kernel.org/netdev/net-next/c/20ab39d13e2e

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



      reply	other threads:[~2021-10-01 22:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-01 14:58 [PATCH net-next] net/core: disable NET_RX_BUSY_POLL on PREEMPT_RT Sebastian Andrzej Siewior
2021-10-01 22: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=163312860747.19403.5188764825013993670.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=bigeasy@linutronix.de \
    --cc=davem@davemloft.net \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=tglx@linutronix.de \
    /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.