From: Zheng Liu <gnehzuil.liu@gmail.com>
To: Theodore Ts'o <tytso@mit.edu>
Cc: linux-ext4@vger.kernel.org, Zheng Liu <wenqing.lz@taobao.com>
Subject: Re: [PATCH 1/2 v2] libext2fs: introduce lseek SEEK_DATA/HOLE
Date: Fri, 18 Jan 2013 18:07:11 +0800 [thread overview]
Message-ID: <20130118100711.GC20442@gmail.com> (raw)
In-Reply-To: <20130116145918.GC6052@thunk.org>
On Wed, Jan 16, 2013 at 09:59:18AM -0500, Theodore Ts'o wrote:
> On Wed, Jan 16, 2013 at 08:04:56PM +0800, Zheng Liu wrote:
> > Yeah, it allows us to skip to the next data/hole directly if the extents
> > interface is used. But if we do that, we will need to handle
> > extent-based file and indirect-based file resptively like this.
> >
> > if (inode->i_flags & EXT4_EXTENTS_FL) {
> > ext2fs_file_ext_llseek_data();
> > ...
> > } else {
> > ext2fs_file_ind_llseek_data();
> > ...
> > }
> >
> > I am not sure whether it is too complicated or not for us. What do you
> > think?
>
> I'm not too worried about the performance issues for debugfs. But for
> clients who are accessing ext[234] using libext2fs and FUSE, they
> would probably notice in at least some circumstances. I'm not that
> worried about the complexity, but it's also not a high priority thing,
> either --- it's a "nice to have", not a "must have".
Understood. Let me try it.
Thanks,
- Zheng
prev parent reply other threads:[~2013-01-18 9:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-14 14:18 [PATCH 1/2 v2] libext2fs: introduce lseek SEEK_DATA/HOLE Zheng Liu
2013-01-14 14:18 ` [PATCH 2/2 v2] debugfs: dump a sparse file Zheng Liu
2013-01-15 3:23 ` [PATCH 1/2 v2] libext2fs: introduce lseek SEEK_DATA/HOLE Theodore Ts'o
2013-01-15 13:02 ` Zheng Liu
2013-01-15 18:55 ` Theodore Ts'o
2013-01-16 12:04 ` Zheng Liu
2013-01-16 14:59 ` Theodore Ts'o
2013-01-18 10:07 ` Zheng Liu [this message]
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=20130118100711.GC20442@gmail.com \
--to=gnehzuil.liu@gmail.com \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
--cc=wenqing.lz@taobao.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;
as well as URLs for NNTP newsgroup(s).