From: David Ahern <dsahern@kernel.org>
To: Eric Dumazet <edumazet@google.com>,
"David S . Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>
Cc: Neal Cardwell <ncardwell@google.com>,
Yuchung Cheng <ycheng@google.com>,
netdev@vger.kernel.org, eric.dumazet@gmail.com
Subject: Re: [PATCH net-next 4/4] tcp_metrics: optimize tcp_metrics_flush_all()
Date: Sat, 23 Sep 2023 13:07:46 +0200 [thread overview]
Message-ID: <e7a1d01a-6607-fa6f-33f8-db31a3fb75a8@kernel.org> (raw)
In-Reply-To: <20230922220356.3739090-5-edumazet@google.com>
On 9/22/23 4:03 PM, Eric Dumazet wrote:
> This is inspired by several syzbot reports where
> tcp_metrics_flush_all() was seen in the traces.
>
> We can avoid acquiring tcp_metrics_lock for empty buckets,
> and we should add one cond_resched() to break potential long loops.
>
> Signed-off-by: Eric Dumazet <edumazet@google.com>
> ---
> net/ipv4/tcp_metrics.c | 7 +++++--
> 1 file changed, 5 insertions(+), 2 deletions(-)
>
> diff --git a/net/ipv4/tcp_metrics.c b/net/ipv4/tcp_metrics.c
> index 7aca12c59c18483f42276d01252ed0fac326e5d8..c2a925538542b5d787596b7d76705dda86cf48d8 100644
> --- a/net/ipv4/tcp_metrics.c
> +++ b/net/ipv4/tcp_metrics.c
> @@ -898,11 +898,13 @@ static void tcp_metrics_flush_all(struct net *net)
> unsigned int row;
>
> for (row = 0; row < max_rows; row++, hb++) {
> - struct tcp_metrics_block __rcu **pp;
> + struct tcp_metrics_block __rcu **pp = &hb->chain;
> bool match;
>
> + if (!rcu_access_pointer(*pp))
> + continue;
> +
> spin_lock_bh(&tcp_metrics_lock);
> - pp = &hb->chain;
> for (tm = deref_locked(*pp); tm; tm = deref_locked(*pp)) {
> match = net ? net_eq(tm_net(tm), net) :
> !refcount_read(&tm_net(tm)->ns.count);
> @@ -914,6 +916,7 @@ static void tcp_metrics_flush_all(struct net *net)
> }
> }
> spin_unlock_bh(&tcp_metrics_lock);
> + cond_resched();
I have found cond_resched() can occur some unnecessary overhead if
called too often. Wrap in `if (need_resched)`?
Reviewed-by: David Ahern <dsahern@kernel.org>
next prev parent reply other threads:[~2023-09-23 11:09 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-22 22:03 [PATCH net-next 0/4] tcp_metrics: four fixes Eric Dumazet
2023-09-22 22:03 ` [PATCH net-next 1/4] tcp_metrics: add missing barriers on delete Eric Dumazet
2023-09-23 11:09 ` David Ahern
2023-09-24 16:09 ` Neal Cardwell
2023-09-22 22:03 ` [PATCH net-next 2/4] tcp_metrics: properly set tp->snd_ssthresh in tcp_init_metrics() Eric Dumazet
2023-09-23 11:08 ` David Ahern
2023-09-24 16:09 ` Neal Cardwell
2023-09-22 22:03 ` [PATCH net-next 3/4] tcp_metrics: do not create an entry from tcp_init_metrics() Eric Dumazet
2023-09-23 11:09 ` David Ahern
2023-09-24 16:09 ` Neal Cardwell
2023-09-22 22:03 ` [PATCH net-next 4/4] tcp_metrics: optimize tcp_metrics_flush_all() Eric Dumazet
2023-09-23 11:07 ` David Ahern [this message]
2023-10-03 8:04 ` Paolo Abeni
2023-10-03 14:29 ` David Ahern
2023-09-24 16:08 ` Neal Cardwell
2023-10-03 9:40 ` [PATCH net-next 0/4] tcp_metrics: four fixes patchwork-bot+netdevbpf
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=e7a1d01a-6607-fa6f-33f8-db31a3fb75a8@kernel.org \
--to=dsahern@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=eric.dumazet@gmail.com \
--cc=kuba@kernel.org \
--cc=ncardwell@google.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=ycheng@google.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).