From: Jakub Kicinski <kuba@kernel.org>
To: Zheng Li <lizheng043@gmail.com>
Cc: netdev@vger.kernel.org, bpf@vger.kernel.org, davem@davemloft.net,
jmorris@namei.org, James.Z.Li@Dell.com
Subject: Re: [PATCH] neighbour: guarantee the localhost connections be established successfully even the ARP table is full
Date: Mon, 15 Apr 2024 11:07:52 -0700 [thread overview]
Message-ID: <20240415110752.30f6733b@kernel.org> (raw)
In-Reply-To: <20240412122538.51-1-lizheng043@gmail.com>
On Fri, 12 Apr 2024 20:25:38 +0800 Zheng Li wrote:
> Inter-process communication on localhost should be established successfully even the ARP table is full,
> many processes on server machine use the localhost to communicate such as command-line interface (CLI),
> servers hope all CLI commands can be executed successfully even the arp table is full.
> Right now CLI commands got timeout when the arp table is full.
> Set the parameter of exempt_from_gc to be true for LOOPBACK net device to
> keep localhost neigh in arp table, not removed by gc.
>
> the steps of reproduced:
> server with "gc_thresh3 = 1024" setting, ping server from more than 1024 IPv4 addresses,
> run "ssh localhost" on console interface, then the command will get timeout.
Please repost this and CC appropriate maintainers.
scripts/get_maintainer doesn't bite.
--
pw-bot: cr
next prev parent reply other threads:[~2024-04-15 18:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-12 12:25 [PATCH] neighbour: guarantee the localhost connections be established successfully even the ARP table is full Zheng Li
2024-04-15 18:07 ` Jakub Kicinski [this message]
2024-04-15 18:15 ` Simon Horman
-- strict thread matches above, loose matches on Subject: below --
2024-04-16 9:53 Zheng Li
2024-04-16 10:02 ` Eric Dumazet
2024-04-16 10:36 ` Li, James Zheng
2024-04-18 9:33 ` Paolo Abeni
2024-04-18 9:45 ` Eric Dumazet
2024-04-18 10:20 ` patchwork-bot+netdevbpf
2024-03-11 12:24 Zheng Li
2024-03-11 13:51 ` Ratheesh Kannoth
2024-03-18 8:39 ` James Lee
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=20240415110752.30f6733b@kernel.org \
--to=kuba@kernel.org \
--cc=James.Z.Li@Dell.com \
--cc=bpf@vger.kernel.org \
--cc=davem@davemloft.net \
--cc=jmorris@namei.org \
--cc=lizheng043@gmail.com \
--cc=netdev@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).