From: Eric Dumazet <eric.dumazet@gmail.com>
To: Daniel Baluta <dbaluta@ixiacom.com>
Cc: Alexandru Copot <alex.mihai.c@gmail.com>,
davem@davemloft.net, gerrit@erg.abdn.ac.uk, kuznet@ms2.inr.ac.ru,
jmorris@namei.org, yoshfuji@linux-ipv6.org, kaber@trash.net,
netdev@vger.kernel.org,
Lucian Grijincu <lucian.grijincu@gmail.com>
Subject: Re: [RFC PATCH 0/4] inet: add second hash table
Date: Wed, 30 May 2012 14:41:02 +0200 [thread overview]
Message-ID: <1338381662.2760.172.camel@edumazet-glaptop> (raw)
In-Reply-To: <CAEnQRZD3o_+fRnnbd74VeFuNvjAVVyq-rE241J96iRXWFDAEPQ@mail.gmail.com>
On Wed, 2012-05-30 at 15:32 +0300, Daniel Baluta wrote:
> Hi Eric,
>
> Usually our tests use a huge number of virtual interfaces.
> Using this patch we get a massive improvement when there are many sockets
> bound to the same port, but different addresses for both bind() and
> listen() system calls (both call inet_csk_get_port).
>
> We provided some data points in the fourth patch:
>
> For 16.000 interfaces each with a distinct IPv4 address, doing bind
> and then listen we get:
>
>
> If I understood it correctly, a similar patch was introduced
> for UDP some time ago. [2]
>
> thanks,
> Daniel.
>
> [1] http://ixlabs.cs.pub.ro/gitweb/?p=port-allocation.git;a=tree;f=testbind;h=687e4452101e13cb5995b43c1351d76786d98fdd;hb=HEAD
> [2] http://www.spinics.net/lists/netdev/msg112056.html
UDP case was a bit different, since production machine could really have
thousand of UDP flows for tunnel terminations.
But for TCP, unless your very specific needs I don't see the real need
to review 400 lines of patches ?
Nobody but you ever complained of listen() being performance critical
with 16.000 IP on a machime...
next prev parent reply other threads:[~2012-05-30 12:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-30 7:36 [RFC PATCH 0/4] inet: add second hash table Alexandru Copot
2012-05-30 7:36 ` [RFC PATCH 1/4] inet: add counter to inet_bind_hashbucket Alexandru Copot
2012-05-30 8:00 ` Eric Dumazet
2012-05-30 7:36 ` [RFC PATCH 2/4] inet: add a second bind hash Alexandru Copot
2012-05-30 7:36 ` [RFC PATCH 3/4] inet: add/remove inet buckets in the " Alexandru Copot
2012-05-30 7:36 ` [RFC PATCH 4/4] inet: use second hash in inet_csk_get_port Alexandru Copot
2012-05-30 16:42 ` Eric Dumazet
2012-05-30 17:20 ` Eric Dumazet
2012-05-30 19:11 ` Alexandru Copot
2012-05-30 7:57 ` [RFC PATCH 0/4] inet: add second hash table Eric Dumazet
2012-05-30 12:32 ` Daniel Baluta
2012-05-30 12:41 ` Eric Dumazet [this message]
2012-05-30 16:27 ` Ben Greear
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=1338381662.2760.172.camel@edumazet-glaptop \
--to=eric.dumazet@gmail.com \
--cc=alex.mihai.c@gmail.com \
--cc=davem@davemloft.net \
--cc=dbaluta@ixiacom.com \
--cc=gerrit@erg.abdn.ac.uk \
--cc=jmorris@namei.org \
--cc=kaber@trash.net \
--cc=kuznet@ms2.inr.ac.ru \
--cc=lucian.grijincu@gmail.com \
--cc=netdev@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox