linux-kernel - Re: Filesystem hints to storage

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: <20100722191541.GA12376@mail.oracle.com>
Date:	Thu, 22 Jul 2010 12:15:41 -0700
From:	Joel Becker <Joel.Becker@...cle.com>
To:	Matthew Wilcox <matthew@....cx>
Cc:	linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: Filesystem hints to storage

On Thu, Jul 22, 2010 at 12:08:54PM -0600, Matthew Wilcox wrote:
> For Enterprise NVMHCI, the working group is looking at refining these
> hints.  Are there any hints that people would like to see added or
> removed from the list in NVMHCI 1.0?
> 
> I think there are some hints that are hard for the filesystem to know
> itself, never mind pass down, so it'd be good to remove them to reduce
> the complexity.  Contrariwise, there are some hints I think the filesystem
> could pass down that aren't in the spec today, such as the flags from
> madvise (random access vs sequential access) and whether the access is
> for fs metadata or application data.

	If we're looking at the filesystem interface to all of this, I
would think these hints could be used by non-SSD storage as well.
Not only would a storage array benefit from knowing about random vs
sequential access, but expected redundancy hints would be huge in
managing utilization.

Joel

-- 

Life's Little Instruction Book #396

	"Never give anyone a fruitcake."

Joel Becker
Consulting Software Developer
Oracle
E-mail: joel.becker@...cle.com
Phone: (650) 506-8127
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/