From: Jakub Kicinski <kuba@kernel.org>
To: cgel.zte@gmail.com
Cc: davem@davemloft.net, yoshfuji@linux-ipv6.org, dsahern@kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
xu.xin16@zte.com.cn
Subject: Re: [PATCH v3 0/3] Namespaceify two sysctls related with route
Date: Wed, 31 Aug 2022 12:58:46 -0700 [thread overview]
Message-ID: <20220831125846.6bb2983a@kernel.org> (raw)
In-Reply-To: <20220830091453.286285-1-xu.xin16@zte.com.cn>
On Tue, 30 Aug 2022 09:14:53 +0000 cgel.zte@gmail.com wrote:
> With the rise of cloud native, more and more container applications are
> deployed. The network namespace is one of the foundations of the container.
> The sysctls of error_cost and error_burst are important knobs to control
> the sending frequency of ICMP_DEST_UNREACH packet for ipv4. When different
> containers has requirements on the tuning of error_cost and error_burst,
> for host's security, the sysctls should exist per network namespace.
>
> Different netns has different requirements on the setting of error_cost
> and error_burst, which are related with limiting the frequency of sending
> ICMP_DEST_UNREACH packets. Enable them to be configured per netns.
One last time, if v6 doesn't need it, neither should v4.
Seems like you're just trying to check a box.
I'm dropping these patches from patchwork, please don't repost them
again, unless someone from the community voices support for merging
them.
prev parent reply other threads:[~2022-08-31 19:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-30 9:14 [PATCH v3 0/3] Namespaceify two sysctls related with route cgel.zte
2022-08-30 9:16 ` [PATCH v3 1/3] ipv4: Namespaceify route/error_cost knob cgel.zte
2022-08-30 9:16 ` [PATCH v3 2/3] ipv4: Namespaceify route/error_burst knob cgel.zte
2022-08-30 9:17 ` [PATCH v3 3/3] ipv4: add documentation of two sysctls about icmp cgel.zte
2022-09-02 10:07 ` Nicolas Dichtel
2022-09-11 9:03 ` CGEL
2022-08-31 19:58 ` Jakub Kicinski [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=20220831125846.6bb2983a@kernel.org \
--to=kuba@kernel.org \
--cc=cgel.zte@gmail.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=xu.xin16@zte.com.cn \
--cc=yoshfuji@linux-ipv6.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 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.