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  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]
Date:	Sat, 4 Nov 2006 11:53:02 +0100
From:	Jörn Engel <>
To:	dean gaudet <>
Cc:	Mikulas Patocka <>,
Subject: Re: New filesystem for Linux

On Fri, 3 November 2006 11:00:58 -0800, dean gaudet wrote:
> it seems to me that you only need to be able to represent a range of the 
> most recent 65536 crashes... and could have an online process which goes 
> about "refreshing" old objects to move them forward to the most recent 
> crash state.  as long as you know the minimm on-disk crash count you can 
> use it as an offset.

You really don't want to go down that path.  Doubling the storage size
will double the work necessary to move old objects - hard to imagine a
design that scales worse.

CPU schedulers, btw, take this approach.  But they cheat, as they know
the maximum lifetime of their objects (in-flight instructions, rename
registers,...) is bounded to n.  Old objects are refreshed for free.


A defeated army first battles and then seeks victory.
-- Sun Tzu
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists