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: <yq1k42xhulg.fsf@sermon.lab.mkp.net>
Date:	Wed, 07 Mar 2012 00:02:19 -0500
From:	"Martin K. Petersen" <martin.petersen@...cle.com>
To:	Andreas Dilger <aedilger@...il.com>
Cc:	Dave Chinner <david@...morbit.com>, linux-fsdevel@...r.kernel.org,
	linux-ext4@...r.kernel.org
Subject: Re: [RFC] fadvise: add more flags to provide a hint for block allocation

>>>>> "Andreas" == Andreas Dilger <aedilger@...il.com> writes:

Andreas> This proposal definitely needs to have some clear explanation
Andreas> of how the flags are intended to be used by applications, and
Andreas> why they will help filesystems to improve allocation. 

This goes a bit deeper than just filesystem block allocation strategy.

With SMR drives lurking on the horizon it is becoming increasingly
important for us to classify anticipated future access patterns as we
send I/Os out to storage. We'll need something much smarter than just
REQ_META for these devices. Tiered storage arrays and tiered flash also
benefit from this information.

There's lots of work going on in the standards space in this department
right now and I was hoping we could spend some time discussing the
current proposals in one of the plenary sessions at LSF. Ideally we'd
tie fadvise() and any filesystem internal knowledge into appropriate
storage hints at the bottom of the stack.

-- 
Martin K. Petersen	Oracle Linux Engineering
--
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