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:57:07 +0800	[thread overview]
Message-ID: <CA+kCZ7-oL9hXNjRuAEFR0=JpYr=xgU4eo9-WFt-gJm=QgRGp7g@mail.gmail.com> (raw)
In-Reply-To: <CANn89i+mkQ31=dV+VcJNg-ChJrBOSC41L9+RqdO3Tkf_NtwSgA@mail.gmail.com>

On Mon, Feb 22, 2021 at 7:29 PM Eric Dumazet <edumazet@google.com> wrote:
>
> On Mon, Feb 22, 2021 at 12:10 PM Honglei Wang <redsky110@gmail.com> wrote:
>
> > 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?
>
> 5.11 is old already.  inet_hashtables.c has been changed for upcoming 5.12
>
> You always must look at current trees before submitting a patch.
>
> Read Documentation/networking/netdev-FAQ.rst for additional hints.

Got it, thanks, Eric!

  reply	other threads:[~2021-02-22 11:58 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
2021-02-22 11:29     ` Eric Dumazet
2021-02-22 11:57       ` Honglei Wang [this message]
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-oL9hXNjRuAEFR0=JpYr=xgU4eo9-WFt-gJm=QgRGp7g@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.