From: patchwork-bot+netdevbpf@kernel.org
To: Thomas Zeitlhofer <thomas.zeitlhofer+lkml@ze-it.at>
Cc: pabeni@redhat.com, davem@davemloft.net,
alexander.mikhalitsyn@virtuozzo.com, den@openvz.org,
edumazet@google.com, kuba@kernel.org, dsahern@kernel.org,
daniel@iogearbox.net, yangyingliang@huawei.com,
songmuchun@bytedance.com, vasily.averin@linux.dev,
wangyuweihx@gmail.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] net: neigh: decrement the family specific qlen
Date: Fri, 18 Nov 2022 10:40:16 +0000 [thread overview]
Message-ID: <166876801608.1818.5528288792107220995.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <Y3QNGHkhvWnxo2LD@x1.ze-it.at>
Hello:
This patch was applied to netdev/net.git (master)
by David S. Miller <davem@davemloft.net>:
On Tue, 15 Nov 2022 23:09:41 +0100 you wrote:
> Commit 0ff4eb3d5ebb ("neighbour: make proxy_queue.qlen limit
> per-device") introduced the length counter qlen in struct neigh_parms.
> There are separate neigh_parms instances for IPv4/ARP and IPv6/ND, and
> while the family specific qlen is incremented in pneigh_enqueue(), the
> mentioned commit decrements always the IPv4/ARP specific qlen,
> regardless of the currently processed family, in pneigh_queue_purge()
> and neigh_proxy_process().
>
> [...]
Here is the summary with links:
- [v2] net: neigh: decrement the family specific qlen
https://git.kernel.org/netdev/net/c/8207f253a097
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:[~2022-11-18 10:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-12 10:48 [PATCH] net: neigh: decrement the family specific qlen Thomas Zeitlhofer
2022-11-15 9:56 ` Paolo Abeni
2022-11-15 22:09 ` [PATCH v2] " Thomas Zeitlhofer
2022-11-18 10:40 ` 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=166876801608.1818.5528288792107220995.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alexander.mikhalitsyn@virtuozzo.com \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=den@openvz.org \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=songmuchun@bytedance.com \
--cc=thomas.zeitlhofer+lkml@ze-it.at \
--cc=vasily.averin@linux.dev \
--cc=wangyuweihx@gmail.com \
--cc=yangyingliang@huawei.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).