public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: xfs mailing list <xfs@oss.sgi.com>
Subject: Re: [PATCH 1/2, RFC] convert xfs_getbmap to take formatter functions
Date: Tue, 21 Oct 2008 04:07:37 -0400	[thread overview]
Message-ID: <20081021080737.GA4193@infradead.org> (raw)
In-Reply-To: <48FD0503.3090203@sandeen.net>

On Mon, Oct 20, 2008 at 05:24:03PM -0500, Eric Sandeen wrote:
> Preliminary work to hook up fiemap, this allows us to pass in an
> arbitrary formatter to copy extent data back to userspace.
> 
> The formatter takes info for 1 extent, a pointer to the user "thing*"
> and a pointer to a "filled" variable to indicate whether a userspace
> buffer did get filled in (for fiemap, hole "extents" are skipped).
> 
> I'm just using the getbmapx struct as a "common denominator" because
> as far as I can see, it holds all info that any formatters will care
> about.
> 
> ("*thing" because fiemap doesn't pass the user pointer around, but rather
> has a pointer to a fiemap info structure, and helpers associated with it)
> 
> I'm still working on the fiemap hookup but wanted to put this out for comment.

This looks good to me.

>  /*
> - * Fcntl interface to xfs_bmapi.
> + * ioctl interface to xfs_bmapi.
>   */

>  /*
> - * Fcntl interface to xfs_bmapi.
> + * ioctl interface to xfs_bmapi.
>   */

Well, it will be for fiemap, too.  And the comment doesn't make much
sense either.  Either remove it completely or replace it by something
that makes sense.

  reply	other threads:[~2008-10-21  8:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-20 22:24 [PATCH 1/2, RFC] convert xfs_getbmap to take formatter functions Eric Sandeen
2008-10-21  8:07 ` Christoph Hellwig [this message]
2008-10-21 13:22   ` Eric Sandeen
2008-10-21 13:31     ` Christoph Hellwig
2008-10-21 15:10       ` Eric Sandeen

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=20081021080737.GA4193@infradead.org \
    --to=hch@infradead.org \
    --cc=sandeen@sandeen.net \
    --cc=xfs@oss.sgi.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