Re: [PATCH v6 4/9] iomap: Generic inline data handling

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: Andreas Grünbacher <andreas.gruenbacher@xxxxxxxxx>
Subject: Re: [PATCH v6 4/9] iomap: Generic inline data handling
From: Christoph Hellwig <hch@xxxxxx>
Date: Mon, 4 Jun 2018 14:12:35 +0200
Cc: Christoph Hellwig <hch@xxxxxx>, Andreas Gruenbacher <agruenba@xxxxxxxxxx>, cluster-devel <cluster-devel@xxxxxxxxxx>, Linux FS-devel Mailing List <linux-fsdevel@xxxxxxxxxxxxxxx>
In-reply-to: <CAHpGcM+MSwt3VG=D4fyC6mqPPXf=Ne1vpctJubfGTjbB+GjQ-w@mail.gmail.com>
User-agent: Mutt/1.5.17 (2007-11-01)

On Mon, Jun 04, 2018 at 02:02:10PM +0200, Andreas Grünbacher wrote:
> For gfs2, passing a private pointer from iomap_begin to iomap_end (for
> the buffer head holding the inode) would help as well, but it's not
> critical.

A private pointer is fine with me.

Follow-Ups:
- Re: [PATCH v6 4/9] iomap: Generic inline data handling
  - From: Andreas Grünbacher

References:
- [PATCH v6 0/9] gfs2 iomap write support
  - From: Andreas Gruenbacher
- [PATCH v6 4/9] iomap: Generic inline data handling
  - From: Andreas Gruenbacher
- Re: [PATCH v6 4/9] iomap: Generic inline data handling
  - From: Christoph Hellwig
- Re: [PATCH v6 4/9] iomap: Generic inline data handling
  - From: Andreas Grünbacher

Prev by Date: Re: [PATCH v6 5/9] iomap: Add write_end iomap operation
Next by Date: Re: [PATCH 08/21] xfs: don't use XFS_BMAPI_IGSTATE in xfs_map_blocks
Previous by thread: Re: [PATCH v6 4/9] iomap: Generic inline data handling
Next by thread: Re: [PATCH v6 4/9] iomap: Generic inline data handling
Index(es):
- Date
- Thread

[Index of Archives] [Linux Ext4 Filesystem] [Union Filesystem] [Filesystem Testing] [Ceph Users] [Ecryptfs] [AutoFS] [Kernel Newbies] [Share Photos] [Security] [Netfilter] [Bugtraq] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux Cachefs] [Reiser Filesystem] [Linux RAID] [Samba] [Device Mapper] [CEPH Development]