linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Fasheh <mfasheh@suse.com>
To: Josef Bacik <jbacik@redhat.com>
Cc: Andreas Dilger <adilger@sun.com>, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 1/5] vfs: vfs-level fiemap interface
Date: Wed, 28 May 2008 13:12:40 -0700	[thread overview]
Message-ID: <20080528201240.GE8325@wotan.suse.de> (raw)
In-Reply-To: <20080528195429.GC23090@unused.rdu.redhat.com>

On Wed, May 28, 2008 at 03:54:29PM -0400, Josef Bacik wrote:
> > > Btw, how many block-based file systems that don't return multiple blocks via
> > > get_blocks() are there that we actually care about enough to write this
> > > code?
> > 
> > That I have no clue about.  Joseph?
> > 
> >
> 
> Well I can't comment on the "care enough about" part, but looking at it I don't
> think reiserfs does, it just maps the one block we ask for.  Just cursory
> looking through stuff it looks like most other stuff does map as much as it can,
> even FAT does.  Thanks much,

Josef, thanks for looking.

Isn't reiserfs extent based anyway? So really, it should (eventually) get a
real ->fiemap callback.
	--Mark

--
Mark Fasheh

  reply	other threads:[~2008-05-28 20:12 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-25  0:01 [PATCH 1/5] vfs: vfs-level fiemap interface Mark Fasheh
2008-05-25  7:28 ` Andreas Dilger
2008-05-27 18:31   ` Mark Fasheh
2008-05-28 16:09     ` Andreas Dilger
2008-05-28 17:24       ` Joel Becker
2008-05-29 23:46         ` Andreas Dilger
2008-05-30  0:15           ` Mark Fasheh
2008-05-30 17:24             ` Andreas Dilger
2008-05-28 19:42 ` Andreas Dilger
2008-05-28 19:54   ` Josef Bacik
2008-05-28 20:12     ` Mark Fasheh [this message]
2008-05-28 20:19       ` Josef Bacik
2008-05-28 21:23   ` Mark Fasheh
2008-05-29  1:24   ` Dave Chinner
2008-05-29 13:04     ` Christoph Hellwig
2008-05-29 17:02       ` Andreas Dilger
2008-05-31  8:16         ` Christoph Hellwig
2008-05-29 13:03   ` Christoph Hellwig
2008-06-05  5:18 ` Andreas Dilger
2008-06-05 21:35   ` jim owens

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=20080528201240.GE8325@wotan.suse.de \
    --to=mfasheh@suse.com \
    --cc=adilger@sun.com \
    --cc=jbacik@redhat.com \
    --cc=linux-fsdevel@vger.kernel.org \
    /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).