From: Jan Kara <jack@suse.cz>
To: Greg Freemyer <greg.freemyer@gmail.com>
Cc: Kazuya Mio <k-mio@sx.jp.nec.com>,
ext4 <linux-ext4@vger.kernel.org>, Theodore Tso <tytso@mit.edu>,
linux-fsdevel@vger.kernel.org,
OHSM-DEV <ohsm-devel@lists.sourceforge.net>,
Dmitry Monakhov <dmonakhov@openvz.org>
Subject: Re: [RFC][PATCH 0/3] ext4: inode preferred block allocation
Date: Tue, 20 Apr 2010 00:39:38 +0200 [thread overview]
Message-ID: <20100419223938.GJ5439@quack.suse.cz> (raw)
In-Reply-To: <g2q87f94c371004150922qb636f468t9cf3b6cb8cfd7b03@mail.gmail.com>
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@suse.cz>
SUSE Labs, CR
next prev parent reply other threads:[~2010-04-19 22:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-14 8:17 [RFC][PATCH 0/3] ext4: inode preferred block allocation Kazuya Mio
2010-04-15 15:11 ` Andi Kleen
2010-04-16 8:23 ` Kazuya Mio
2010-04-15 16:22 ` Greg Freemyer
2010-04-19 22:39 ` Jan Kara [this message]
2010-04-20 8:40 ` Kazuya Mio
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100419223938.GJ5439@quack.suse.cz \
--to=jack@suse.cz \
--cc=dmonakhov@openvz.org \
--cc=greg.freemyer@gmail.com \
--cc=k-mio@sx.jp.nec.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=ohsm-devel@lists.sourceforge.net \
--cc=tytso@mit.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).