[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1512167066.19682.47.camel@gmail.com>
Date: Fri, 01 Dec 2017 14:24:26 -0800
From: Eric Dumazet <eric.dumazet@...il.com>
To: Martin KaFai Lau <kafai@...com>, netdev <netdev@...r.kernel.org>
Cc: "David S . Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>,
Kernel Team <kernel-team@...com>
Subject: Re: [PATCH v2 net-next 3/4] inet: Add a 2nd listener hashtable
(port+addr)
On Fri, 2017-12-01 at 12:52 -0800, Martin KaFai Lau wrote:
> The current listener hashtable is hashed by port only.
> When a process is listening at many IP addresses with the same port
> (e.g.
> [IP1]:443, [IP2]:443... [IPN]:443), the inet[6]_lookup_listener()
> performance is degraded to a link list. It is prone to syn attack.
>
> UDP had a similar issue and a second hashtable was added to resolve
> it.
>
> This patch adds a second hashtable for the listener's sockets.
> The second hashtable is hashed by port and address.
>
> It cannot reuse the existing skc_portaddr_node which is shared
> with skc_bind_node. TCP listener needs to use skc_bind_node.
> Instead, this patch adds a hlist_node 'icsk_listen_portaddr_node' to
> the inet_connection_sock which the listener (like TCP) also belongs
> to.
>
> The new portaddr hashtable may need two lookup (First by IP:PORT.
> Second by INADDR_ANY:PORT if the IP:PORT is a not found). Hence,
> it implements a similar cut off as UDP such that it will only consult
> the
> new portaddr hashtable if the current port-only hashtable has >10
> sk in the link-list.
>
> lhash2 and lhash2_mask are added to 'struct inet_hashinfo'. I take
> this chance to plug a 4 bytes hole. It is done by first moving
> the existing bind_bucket_cachep up and then add the new
> (int lhash2_mask, *lhash2) after the existing bhash_size.
>
> Signed-off-by: Martin KaFai Lau <kafai@...com>
Nice work, thanks Martin !
Reviewed-by: Eric Dumazet <edumazet@...gle.com>
Powered by blists - more mailing lists