All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Judy Hsiao <judyhsiao@chromium.org>
Cc: edumazet@google.com, dsahern@kernel.org, horms@kernel.org,
	dianders@chromium.org, haleyb.dev@gmail.com, davem@davemloft.net,
	kuba@kernel.org, joel.granados@gmail.com, ja@ssi.bg,
	leon@kernel.org, pabeni@redhat.com, linux-kernel@vger.kernel.org,
	netdev@vger.kernel.org
Subject: Re: [PATCH v2] neighbour: Don't let neigh_forced_gc() disable preemption for long
Date: Fri, 08 Dec 2023 10:50:23 +0000	[thread overview]
Message-ID: <170203262380.21119.9612861289100953455.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231206033913.1290566-1-judyhsiao@chromium.org>

Hello:

This patch was applied to netdev/net.git (main)
by David S. Miller <davem@davemloft.net>:

On Wed,  6 Dec 2023 03:38:33 +0000 you wrote:
> We are seeing cases where neigh_cleanup_and_release() is called by
> neigh_forced_gc() many times in a row with preemption turned off.
> When running on a low powered CPU at a low CPU frequency, this has
> been measured to keep preemption off for ~10 ms. That's not great on a
> system with HZ=1000 which expects tasks to be able to schedule in
> with ~1ms latency.
> 
> [...]

Here is the summary with links:
  - [v2] neighbour: Don't let neigh_forced_gc() disable preemption for long
    https://git.kernel.org/netdev/net/c/e5dc5afff62f

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



      parent reply	other threads:[~2023-12-08 10:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-06  3:38 [PATCH v2] neighbour: Don't let neigh_forced_gc() disable preemption for long Judy Hsiao
2023-12-06  3:43 ` David Ahern
2023-12-06  7:34 ` Eric Dumazet
2023-12-06 17:21 ` Doug Anderson
2023-12-06 17:39 ` Stephen Hemminger
2023-12-06 17:51   ` David Ahern
2023-12-06 18:49     ` Doug Anderson
2023-12-06 19:15       ` David Ahern
2023-12-08 10: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=170203262380.21119.9612861289100953455.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=dianders@chromium.org \
    --cc=dsahern@kernel.org \
    --cc=edumazet@google.com \
    --cc=haleyb.dev@gmail.com \
    --cc=horms@kernel.org \
    --cc=ja@ssi.bg \
    --cc=joel.granados@gmail.com \
    --cc=judyhsiao@chromium.org \
    --cc=kuba@kernel.org \
    --cc=leon@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --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 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.