From: Kazuya Mio <k-mio@sx.jp.nec.com>
To: ext4 <linux-ext4@vger.kernel.org>, Theodore Tso <tytso@mit.edu>
Cc: linux-fsdevel@vger.kernel.org
Subject: [RFC][PATCH 0/3] ext4: inode preferred block allocation
Date: Wed, 14 Apr 2010 17:17:33 +0900 [thread overview]
Message-ID: <4BC57A1D.9080105@sx.jp.nec.com> (raw)
Hi,
We implemented new two ioctls to allocate preferred blocks using inode PA.
The old implementation idea is the following (b).
http://marc.info/?l=linux-ext4&m=124962738211206&w=4
One is EXT4_IOC_CONTROL_PA that is to create or discard inode PA, and the
other is EXT4_IOC_GET_PA that is to get inode PA information.
1. EXT4_IOC_CONTROL_PA
EXT4_IOC_CONTROL_PA is used to create new inode PA, or to discard all inode
PAs in the target inode. This means that we will be able to allocate
the blocks we want.
We have a plan to add a new feature to e4defrag with these ioctls. This
feature improves read throughput when we read the files in the same
directory by reallocating target files near their parent directory.
2. EXT4_IOC_GET_PA
EXT4_IOC_GET_PA is used to get inode PA information.
Moreover, when we create an inode PA, ext4_mb_new_inode_pa() merges
contiguous inode PA if possible.
This patch set consists of the following three patches. They can be applied to
the ext4 patch queue:
commit: 1dea5b6f540ad056d51d11cda71fa757cb44cbc4
[RFC][PATCH 0/3] ext4: inode preferred block allocation
[RFC][PATCH 1/3] ext4: add EXT4_IOC_CONTROL_PA to create/discard inode PA
[RFC][PATCH 2/3] ext4: sort and merge inode PA
[RFC][PATCH 3/3] ext4: add EXT4_IOC_GET_PA to get inode PA information
Any comments are very welcome.
Best regards,
Kazuya Mio
next reply other threads:[~2010-04-14 8:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-14 8:17 Kazuya Mio [this message]
2010-04-15 15:11 ` [RFC][PATCH 0/3] ext4: inode preferred block allocation Andi Kleen
2010-04-16 8:23 ` Kazuya Mio
2010-04-15 16:22 ` Greg Freemyer
2010-04-19 22:39 ` Jan Kara
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=4BC57A1D.9080105@sx.jp.nec.com \
--to=k-mio@sx.jp.nec.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.