linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@redhat.com>
To: Akira Fujita <a-fujita@rs.jp.nec.com>
Cc: Andreas Dilger <adilger@sun.com>,
	cmm@us.ibm.com, tytso@mit.edu, linux-ext4@vger.kernel.org,
	linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 1/5] ext4 online defrag header file changes
Date: Mon, 24 Mar 2008 10:00:42 -0500	[thread overview]
Message-ID: <47E7C21A.10208@redhat.com> (raw)
In-Reply-To: <47E789E6.6000806@rs.jp.nec.com>

Akira Fujita wrote:

> Is EXT4_IOC_FIEMAP going to be added to the ext4 patch queue?
> I will try to use EXT4_IOC_FIEMAP instead of EXT4_IOC_EXTENTS_INFO
> in ext4 online defrag when kernel supports it.

It's not, yet, but I could probably put it there.

It is not ready for upstream yet at all, but it does have a good amount
of functionality.

I'll try to get something submitted for the patch queue soon...

(I decided to slow down a bit on the fiemap work, and concentrate on
helping to get e2fsprogs ready with ext4 support)

-Eric

  parent reply	other threads:[~2008-03-24 15:00 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-14 12:02 [PATCH 1/5] ext4 online defrag header file changes Akira Fujita
2008-03-14 12:58 ` Andreas Dilger
2008-03-17  6:28   ` Akira Fujita
2008-03-17 17:08     ` Andreas Dilger
2008-03-24 11:00       ` Akira Fujita
2008-03-24 11:16         ` Aneesh Kumar K.V
2008-03-24 15:00         ` Eric Sandeen [this message]
2008-03-25  2:21           ` Akira Fujita
  -- strict thread matches above, loose matches on Subject: below --
2008-03-31  8:46 Akira Fujita
2008-03-24 12:34 Akira Fujita
2008-03-24 12:31 Akira Fujita
2008-03-25 17:48 ` Aneesh Kumar K.V
2008-03-27 10:15   ` Akira Fujita
2008-03-29  0:49     ` Mingming Cao
     [not found] <1204931337.14884.43.camel@localhost.localdomain>
2008-03-08  0:18 ` Mingming Cao

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=47E7C21A.10208@redhat.com \
    --to=sandeen@redhat.com \
    --cc=a-fujita@rs.jp.nec.com \
    --cc=adilger@sun.com \
    --cc=cmm@us.ibm.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 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).