All of lore.kernel.org
 help / color / mirror / Atom feed
From: Akira Fujita <a-fujita@rs.jp.nec.com>
To: Andreas Dilger <adilger@sun.com>
Cc: 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, 17 Mar 2008 15:28:29 +0900	[thread overview]
Message-ID: <47DE0F8D.2060106@rs.jp.nec.com> (raw)
In-Reply-To: <20080314125848.GE3542@webber.adilger.int>

Hi Andreas,
>> How about renaming this structure from ext4_extent_data to
>> ext4_extent_info which used the extent in-core structure
>> and put it into ext4_fs_extents.h? 
>> Because in-core super_block is ext4_sb_info.
>>
>> /*
>>  * This is the extent in-core structure.
>>  */
>> struct ext4_extent_info {
>> 	ext4_lblk_t	ee_block;	/* first logical block extent covers */
>> 	int		ee_len;		/* number of blocks covered by extent */
>> 	ext4_fsblk_t	ee_start;	/* first physical block extent covers */
>> };      
>>     
>
> Would it be possible to use the FIEMAP interface to get the file mapping
> data to userspace?  That would avoid the need to have a second ioctl
> with nearly the same data.
>   
Reducing ioctl makes sense.
But EXT4_EXTENTS_INFO needs to get the file mapping data
with inode number not file name.
So we should keep ext4_extents_info structure
or put ino entry in fiemap structure.

Regards, Akira


  reply	other threads:[~2008-03-17  6:30 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 [this message]
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
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=47DE0F8D.2060106@rs.jp.nec.com \
    --to=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 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.