From: Theodore Tso <tytso@MIT.EDU>
To: a-fujita@rs.jp.nec.com
Cc: Takashi Sato <t-sato@yk.jp.nec.com>, linux-ext4@vger.kernel.org
Subject: Re: Review of ext4-online-defrag-check-for-freespace-fragmentation.patch
Date: Sat, 13 Sep 2008 22:10:24 -0400 [thread overview]
Message-ID: <20080914021024.GB30537@mit.edu> (raw)
In-Reply-To: <E1KedQ2-0004sG-Py@closure.thunk.org>
On Sat, Sep 13, 2008 at 06:16:42PM -0400, Theodore Ts'o wrote:
>
> Secondly, some of the ioctl numbers chosen by the defrag patches overlap
> other, already existing patches. This is something we will need to fix,
> long term. For now, folks should know that we can't count on the ioctl
> numbers being stable, since we will probably need to move them.
Note: I have done this in the version of the defrag patches in the
ext4 patch queue, where all of the ioctl's introduced by the defrag
patches have been renumbered starting at 15, to avoid conflicts with
other ioctls that either exist already or could be introduced in the
future.
If you don't mind, we can also merge up some of the patches that have
been inserted in the patch queue, and then you can start working from
the modified version in the patch queue. The other way to move
forward is that we can start creating new ioctl's that are more
general and have carefully designed interfaces, and then as the
replacement ioctl's are created, the defrag patches can be shortened
and the on-line defrag command modified to use the new ioctl's.
- Ted
next prev parent reply other threads:[~2008-09-14 2:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-13 22:16 Review of ext4-online-defrag-check-for-freespace-fragmentation.patch Theodore Ts'o
2008-09-14 2:10 ` Theodore Tso [this message]
2008-09-17 6:46 ` Akira Fujita
2008-09-17 6:43 ` Akira Fujita
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=20080914021024.GB30537@mit.edu \
--to=tytso@mit.edu \
--cc=a-fujita@rs.jp.nec.com \
--cc=linux-ext4@vger.kernel.org \
--cc=t-sato@yk.jp.nec.com \
/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