[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230601103742.71285cf1@hermes.local>
Date: Thu, 1 Jun 2023 10:37:42 -0700
From: Stephen Hemminger <stephen@...workplumber.org>
To: Matthieu Baerts <matthieu.baerts@...sares.net>
Cc: mptcp@...ts.linux.dev, "David S. Miller" <davem@...emloft.net>, Eric
Dumazet <edumazet@...gle.com>, Jakub Kicinski <kuba@...nel.org>, Paolo
Abeni <pabeni@...hat.com>, David Ahern <dsahern@...nel.org>, Mat Martineau
<martineau@...nel.org>, Hideaki YOSHIFUJI <yoshfuji@...ux-ipv6.org>,
netdev@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH net-next RFC] net: skip printing "link become ready" v6
msg
On Thu, 01 Jun 2023 16:34:36 +0200
Matthieu Baerts <matthieu.baerts@...sares.net> wrote:
> This following message is printed in the console each time a network
> device configured with an IPv6 addresses is ready to be used:
>
> ADDRCONF(NETDEV_CHANGE): <iface>: link becomes ready
>
> When netns are being extensively used -- e.g. by re-creating netns with
> veth to discuss with each other for testing purposes like mptcp_join.sh
> selftest does -- it generates a lot of messages: more than 700 when
> executing mptcp_join.sh with the latest version.
Don't add yet another network nerd knob.
Just change message from pr_info to pr_debug.
Powered by blists - more mailing lists