linux-ext4 - Re: [RFC] fadvise: add more flags to provide a hint for block allocation

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: <4F5591DB.4060807@oracle.com>
Date:	Mon, 05 Mar 2012 20:26:03 -0800
From:	Sunil Mushran <sunil.mushran@...cle.com>
To:	linux-fsdevel@...r.kernel.org, linux-ext4@...r.kernel.org
Subject: Re: [RFC] fadvise: add more flags to provide a hint for block allocation

On 3/5/2012 6:35 PM, Zheng Liu wrote:
> No, _RANDOM means that file system doesn't need to try its best to find
> a proper position to allocate some blocks for this file.  Furthermore,
> currently random IOs seem that they are not obviously slower than
> sequential IOs in Flash/SSD device.  For example, when users know a file
> that is accessed infrequently, they can put this file in a corner, such
> as in some discontinuously blocks.  Then sequential blocks are reserved
> for the file that needs to be accessed frequently and users can obtain
> the better performance.

Then FADV_ALLOC_HOT_REGION and FADV_ALLOC_COLD_REGION are
probably better terms.

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