linux-ext4 - Re: [RFC][PATCH 0/3] ext4: inode preferred 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: <20100419223938.GJ5439@quack.suse.cz>
Date:	Tue, 20 Apr 2010 00:39:38 +0200
From:	Jan Kara <jack@...e.cz>
To:	Greg Freemyer <greg.freemyer@...il.com>
Cc:	Kazuya Mio <k-mio@...jp.nec.com>,
	ext4 <linux-ext4@...r.kernel.org>, Theodore Tso <tytso@....edu>,
	linux-fsdevel@...r.kernel.org,
	OHSM-DEV <ohsm-devel@...ts.sourceforge.net>,
	Dmitry Monakhov <dmonakhov@...nvz.org>
Subject: Re: [RFC][PATCH 0/3] ext4: inode preferred block allocation

On Thu 15-04-10 12:22:38, Greg Freemyer wrote:
<snip>
> fyi: Creating locality groups is the use case I see for Dmitry's
> Project ID patchset.  A collection of files that are used together can
> be assigned a unique ProjectID and then e4defrag can grow the
> knowledge to place them within a locality area on the disk.
> 
> But I also can see that new files within a directory would inherit the
> ProjectID from the directory, and the data blocks allocated from the
> correct locality area from the get go.
> 
> Dmitry, I haven't studied your patchset, but does it allow for
> ProjectID inheritance from the parent directory?
  Yes, ProjectID should be inherited from the parent directory.

								Honza
-- 
Jan Kara <jack@...e.cz>
SUSE Labs, CR
--
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