netdev - RE: [PATCH v3 01/10] dql: Dynamic queue limits

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: <AE90C24D6B3A694183C094C60CF0A2F6D8AEDD@saturn3.aculab.com>
Date:	Wed, 23 Nov 2011 15:35:39 -0000
From:	"David Laight" <David.Laight@...LAB.COM>
To:	"Eric Dumazet" <eric.dumazet@...il.com>,
	"Tom Herbert" <therbert@...gle.com>
Cc:	<davem@...emloft.net>, <netdev@...r.kernel.org>
Subject: RE: [PATCH v3 01/10] dql: Dynamic queue limits

 
> Another question is : Is DQL planned to work on 32bit arch ?
> 
> A fast interface can probably send more than 2^32 bytes for large
> slack_hold_time values, and wrap around.
> 
> If yes : We can use "unsigned int" instead of "unsigned long" to lower
> memory need on 64bit arch.
> 
> If no, "unsigned long" type is not enough on 32bit, or we 
> need to limit slack_hold_time to small intervals...

Another option would be divide the byte counts by (say) 16.
This would be good enough for the purpose, and increase the
time-to-wrap by a factor of 16.

	David


--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html