All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bob Peterson <rpeterso@redhat.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: linux-fsdevel@vger.kernel.org, Jan Kara <jack@suse.cz>,
	Al Viro <viro@ZenIV.linux.org.uk>,
	Dave Chinner <david@fromorbit.com>
Subject: Re: [vfs PATCH v3 1/4] VFS: move iomap from exportfs.h to iomap.h
Date: Mon, 28 Mar 2016 15:53:04 -0400 (EDT)	[thread overview]
Message-ID: <690524895.44280573.1459194784327.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <20160315072912.GE11669@infradead.org>

----- Original Message -----
> On Fri, Mar 04, 2016 at 03:11:37PM -0500, Bob Peterson wrote:
> > This patch moves the iomap declares from its current location in
> > exportfs.h to a new iomap.h. This will facilitate future improvements
> > such as a more efficient fiemap for holey files. Hopefully it will
> > one day be used for multipage writes as well.
> 
> Still not a plain move.  This adds the fspriv member, but also reduces
> the size of length which will probably break pnfs exporting in some
> cases.
> 
> I have done a plain move in this series:
> http://thread.gmane.org/gmane.comp.file-systems.xfs.general/73804
> 
> might make sense to grab this for both possible tree that could be used
> for the infrastructure.
> 
Hi Christoph,

Thanks for the link. I'm very pleased to see you're working on the
multi-page write and iomap stuff. I'd like to see these patches go
forward and I'll build my fiemap stuff off of them.

Does it make sense to split the first two vfs-related patches from the
others that are more xfs related? I didn't see these patches appear on
linux-fsdevel or lkml, so I assume they're only on the xfs list currently?

It would be nice to see them on linux-fsdevel, since I'm not subscribed to
that xfs list. It would also be useful to get them into some place more
central like Al's vfs tree.

Regards,

Bob Peterson
Red Hat File Systems

  reply	other threads:[~2016-03-28 19:53 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-04 20:11 [vfs PATCH v3 0/4] vfs: Expand iomap interface to fiemap Bob Peterson
2016-03-04 20:11 ` [vfs PATCH v3 1/4] VFS: move iomap from exportfs.h to iomap.h Bob Peterson
2016-03-15  7:29   ` Christoph Hellwig
2016-03-28 19:53     ` Bob Peterson [this message]
2016-03-29  7:40       ` Christoph Hellwig
2016-03-29 22:20         ` Dave Chinner
2016-03-30  6:47           ` Christoph Hellwig
2016-04-07 19:58             ` Bob Peterson
2016-04-07 20:42               ` Christoph Hellwig
2016-04-10 17:15           ` Christoph Hellwig
2016-04-11  6:17             ` Dave Chinner
2016-04-12 18:29               ` Christoph Hellwig
2016-04-13  0:22                 ` Dave Chinner
2016-03-04 20:11 ` [vfs PATCH v3 2/4] VFS: Add new __generic_iomap_fiemap interface Bob Peterson
2016-03-07 10:18   ` Jan Kara
2016-03-15  7:33   ` Christoph Hellwig
2016-03-04 20:11 ` [vfs PATCH v3 3/4] GFS2: Add function gfs2_get_iomap Bob Peterson
2016-03-04 20:11 ` [vfs PATCH v3 4/4] GFS2: Use new iomap interface for fiemap Bob Peterson
2016-03-15  7:33   ` Christoph Hellwig

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=690524895.44280573.1459194784327.JavaMail.zimbra@redhat.com \
    --to=rpeterso@redhat.com \
    --cc=david@fromorbit.com \
    --cc=hch@infradead.org \
    --cc=jack@suse.cz \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=viro@ZenIV.linux.org.uk \
    /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.