mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: =?utf-8?q?St=C3=A9phane_Graber_=3Cstgraber=40ubuntu=2Ecom=3E?=@ci.codeaurora.org
Cc: netdev@vger.kernel.org, pshelar@ovn.org, davem@davemloft.net,
	kuba@kernel.org, pabeni@redhat.com, dev@openvswitch.org,
	linux-kernel@vger.kernel.org, frode.nordahl@canonical.com
Subject: Re: [PATCH] openvswitch: Add recirc_id to recirc warning
Date: Thu, 31 Mar 2022 16:20:11 +0000	[thread overview]
Message-ID: <164874361103.27032.11108416383428430823.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220330194244.3476544-1-stgraber@ubuntu.com>

Hello:

This patch was applied to netdev/net.git (master)
by Jakub Kicinski <kuba@kernel.org>:

On Wed, 30 Mar 2022 15:42:45 -0400 you wrote:
> When hitting the recirculation limit, the kernel would currently log
> something like this:
> 
> [   58.586597] openvswitch: ovs-system: deferred action limit reached, drop recirc action
> 
> Which isn't all that useful to debug as we only have the interface name
> to go on but can't track it down to a specific flow.
> 
> [...]

Here is the summary with links:
  - openvswitch: Add recirc_id to recirc warning
    https://git.kernel.org/netdev/net/c/ea07af2e71cd

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



      parent reply	other threads:[~2022-03-31 16:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-30 19:42 Stéphane Graber
2022-03-31  8:28 ` Eelco Chaudron
2022-03-31 16:20 ` 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=164874361103.27032.11108416383428430823.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc==?utf-8?q?St=C3=A9phane_Graber_=3Cstgraber=40ubuntu=2Ecom=3E?=@ci.codeaurora.org \
    --cc=davem@davemloft.net \
    --cc=dev@openvswitch.org \
    --cc=frode.nordahl@canonical.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=pshelar@ovn.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
all inboxes | Powered by JetHome®