All of lore.kernel.org
 help / color / mirror / Atom feed
From: Honglei Wang <redsky110@gmail.com>
To: Eric Dumazet <edumazet@google.com>
Cc: David Miller <davem@davemloft.net>, netdev <netdev@vger.kernel.org>
Subject: Re: [PATCH] tcp: avoid unnecessary loop if even ports are used up
Date: Mon, 22 Feb 2021 19:09:55 +0800	[thread overview]
Message-ID: <CA+kCZ7-AeEHrOo18DMzF1zOGC=b-GrP3XFj5QhPeOoM3U0j6Ow@mail.gmail.com> (raw)
In-Reply-To: <CANn89iKw_GCU6QeDHx31zcjFzqhzjaR2KrSNRON=KbohswHhmg@mail.gmail.com>

On Mon, Feb 22, 2021 at 3:47 PM Eric Dumazet <edumazet@google.com> wrote:
>
> On Sat, Feb 20, 2021 at 12:04 PM Honglei Wang <redsky110@gmail.com> wrote:
> >
> > We are getting port for connect() from even ports firstly now. This
> > makes bind() users have more available slots at odd part. But there is a
> > problem here when the even ports are used up. This happens when there
> > is a flood of short life cycle connections. In this scenario, it starts
> > getting ports from the odd part, but each requirement has to walk all of
> > the even port and the related hash buckets (it probably gets nothing
> > before the workload pressure's gone) before go to the odd part. This
> > makes the code path __inet_hash_connect()->__inet_check_established()
> > and the locks there hot.
> >
> > This patch tries to improve the strategy so we can go faster when the
> > even part is used up. It'll record the last gotten port was odd or even,
> > if it's an odd one, it means there is no available even port for us and
> > we probably can't get an even port this time, neither. So we just walk
> > 1/16 of the whole even ports. If we can get one in this way, it probably
> > means there are more available even part, we'll go back to the old
> > strategy and walk all of them when next connect() comes. If still can't
> > get even port in the 1/16 part, we just go to the odd part directly and
> > avoid doing unnecessary loop.
>
>
> Your patch trades correctness for speed.
>
> Sorry, but adding yet another static (and thus shared) variable
> assuming only one process
> on the physical host attempts a series of connect() is a non starter for me.
>
Actually, the very first start point makes me go into this problem is a
multiple-processes scenario and the hottest point in perf is the spin_lock()
in __inet_check_established(). It spends too much time on buckets walking
which is the critical section of spin_lock().

> Just scanning 1/8 of even ports to decide if none of them is available
> is potentially going to
> not see 7/16 of potential free 4-tuple, and an application needing
> 28,000 4-tuple with SRCIP,DSTIP,DSTPORT being fixed
> might not be able to run anymore.
>
After a bit more deeping based on the case above, I found most of the cpu
cycles spent at INET_MATCH() and it always 'goto not_unique' at last. This
became a bit better when tcp_tw_reuse set to 1, but the code path was still
hot. The 4-tuple were almost not matched when tcp_tw_reuse is 2 in this
workload.

This made me start thinking if we can go faster when walking the ports and
buckets. And in my original opinion, we should be able to scan most of the
even ports in several odd ports touching...

> If you do not care about bind() being able to find a free port, I
> would suggest you add
> a sysctl to simply relax the even/odd strategy that Google has been using
> to avoid all these port exhaustion bugs we had in the past.
> (Although now we use one netns per job, jobs are now isolated and only
> can hurt themselves)
>

Thanks a lot for giving this good suggestion.

Yes, this was the very first idea when I thought about the fix. But before do
more work on this idea, I saw the code of this patch give some performance
improvement. So I think it's not bad as well.. If you think it's not graceful to
just speed up by scanning less ports, it's good for me to do more digging
and work on adding a sysctl to fix the problem completely.

>
>
> >
> >
> > Signed-off-by: Honglei Wang <redsky110@gmail.com>
> > ---
> >  net/ipv4/inet_hashtables.c | 21 +++++++++++++++++++--
> >  1 file changed, 19 insertions(+), 2 deletions(-)
> >
> > diff --git a/net/ipv4/inet_hashtables.c b/net/ipv4/inet_hashtables.c
> > index 45fb450b4522..c95bf5cf9323 100644
> > --- a/net/ipv4/inet_hashtables.c
> > +++ b/net/ipv4/inet_hashtables.c
> > @@ -721,9 +721,10 @@ int __inet_hash_connect(struct inet_timewait_death_row *death_row,
> >         struct net *net = sock_net(sk);
> >         struct inet_bind_bucket *tb;
> >         u32 remaining, offset;
> > -       int ret, i, low, high;
> > +       int ret, i, low, high, span;
> >         static u32 hint;
>
>
> This is an old tree, current kernels do not have this 'static u32 hint' anymore.
>

Really? I just came to the latest 5.11 including Linus' tree and
net-next, seems it's still here at line
725 of inet_hashtables.c.. Do I miss something?

Honglei

>
> >
> >         int l3mdev;
> > +       static bool last_port_is_odd;
> >
> >         if (port) {
> >                 head = &hinfo->bhash[inet_bhashfn(net, port,
> > @@ -756,8 +757,19 @@ int __inet_hash_connect(struct inet_timewait_death_row *death_row,
> >          */
> >         offset &= ~1U;
> >  other_parity_scan:
> > +       /* If the last available port is odd, it means
> > +        * we walked all of the even ports, but got
> > +        * nothing last time. It's telling us the even
> > +        * part is busy to get available port. In this
> > +        * case, we can go a bit faster.
> > +        */
> > +       if (last_port_is_odd && !(offset & 1) && remaining > 32)
> > +               span = 32;
> > +       else
> > +               span = 2;
> > +
> >         port = low + offset;
> > -       for (i = 0; i < remaining; i += 2, port += 2) {
> > +       for (i = 0; i < remaining; i += span, port += span) {
> >                 if (unlikely(port >= high))
> >                         port -= remaining;
> >                 if (inet_is_local_reserved_port(net, port))
> > @@ -806,6 +818,11 @@ int __inet_hash_connect(struct inet_timewait_death_row *death_row,
> >  ok:
> >         hint += i + 2;
> >
> > +       if (offset & 1)
> > +               last_port_is_odd = true;
> > +       else
> > +               last_port_is_odd = false;
> > +
> >         /* Head lock still held and bh's disabled */
> >         inet_bind_hash(sk, tb, port);
> >         if (sk_unhashed(sk)) {
> > --
> > 2.14.1
> >

  reply	other threads:[~2021-02-22 11:11 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-20 11:03 [PATCH] tcp: avoid unnecessary loop if even ports are used up Honglei Wang
2021-02-20 21:44 ` David Miller
2021-02-20 22:06   ` Jeremy Sowden
2021-02-22  1:11     ` Honglei Wang
2021-02-22  7:47 ` Eric Dumazet
2021-02-22 11:09   ` Honglei Wang [this message]
2021-02-22 11:29     ` Eric Dumazet
2021-02-22 11:57       ` Honglei Wang
2021-03-03  9:00 ` [tcp] ff0d41306d: stress-ng.sockmany.ops_per_sec 338.2% improvement kernel test robot
2021-03-03  9:00   ` kernel test robot

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='CA+kCZ7-AeEHrOo18DMzF1zOGC=b-GrP3XFj5QhPeOoM3U0j6Ow@mail.gmail.com' \
    --to=redsky110@gmail.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.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 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.