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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Sat, 21 Apr 2012 14:24:12 -0400
From:	Jeff Garzik <>
To:	Theodore Ts'o <>
	Ext4 Developers List <>
Subject: Re: [PATCH, RFC 0/3] Introduce new O_HOT and O_COLD flags

On 04/19/2012 03:20 PM, Theodore Ts'o wrote:
> As I had brought up during one of the lightning talks at the Linux
> Storage and Filesystem workshop, I am interested in introducing two new
> open flags, O_HOT and O_COLD.  These flags are passed down to the
> individual file system's inode operations' create function, and the file
> system can use these flags as a hint regarding whether the file is
> likely to be accessed frequently or not.
> In the future I plan to do further work on how ext4 would use these
> flags, but I want to first get the ability to pass these flags plumbed
> into the VFS layer and the code points for O_HOT and O_COLD reserved.
> Theodore Ts'o (3):
>    fs: add new open flags O_HOT and O_COLD
>    fs: propagate the open_flags structure down to the low-level fs's
>      create()
>    ext4: use the O_HOT and O_COLD open flags to influence inode
>      allocation

Full-file seems awfully coarse-grained.  What about doing this at page 
granularity, and hint via VM as well as block layer?


To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to
More majordomo info at

Powered by blists - more mailing lists