netdev - RE: [net-next PATCH 2/3] net: fix enforcing of fragment queue hash list depth

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <AE90C24D6B3A694183C094C60CF0A2F6026B71EB@saturn3.aculab.com>
Date:	Fri, 19 Apr 2013 11:41:19 +0100
From:	"David Laight" <David.Laight@...LAB.COM>
To:	"Eric Dumazet" <eric.dumazet@...il.com>,
	"Jesper Dangaard Brouer" <brouer@...hat.com>
Cc:	"David S. Miller" <davem@...emloft.net>,
	"Hannes Frederic Sowa" <hannes@...essinduktion.org>,
	<netdev@...r.kernel.org>
Subject: RE: [net-next PATCH 2/3] net: fix enforcing of fragment queue hash list depth

> The 64 slots hash table was chosen years ago, when machines had 3 order
> of magnitude less ram than today.
> 
> Before hash resizing, I would just bump hash size to something more
> reasonable like 1024.

While that is true of many systems, there are embedded systems
with much less ram than the typical x86 desktop or server.

There seem to be quite a lot of large hash tables appearing
that on many small systems will never contain a significant
number of entries and just waste precious memory.

	David