cluster-devel.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Darrick J. Wong <darrick.wong@oracle.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH 2/3] iomap: support direct I/O to inline data
Date: Tue, 3 Jul 2018 09:06:51 -0700	[thread overview]
Message-ID: <20180703160651.GY5711@magnolia> (raw)
In-Reply-To: <20180702145458.22330-3-hch@lst.de>

On Mon, Jul 02, 2018 at 08:54:57AM -0600, Christoph Hellwig wrote:
> From: Andreas Gruenbacher <agruenba@redhat.com>
> 
> Add support for reading from and writing to inline data to iomap_dio_rw.
> This saves filesystems from having to implement fallback code for this
> case.
> 
> The inline data is actually cached in the inode, so the I/O is only
> direct in the sense that it doesn't go through the page cache.
> 
> Signed-off-by: Andreas Gruenbacher <agruenba@redhat.com>

Looks ok,
Reviewed-by: Darrick J. Wong <darrick.wong@oracle.com>

--D

> ---
>  fs/iomap.c | 29 +++++++++++++++++++++++++++++
>  1 file changed, 29 insertions(+)
> 
> diff --git a/fs/iomap.c b/fs/iomap.c
> index 4d8ff0f5ecc9..98a1fdd5c091 100644
> --- a/fs/iomap.c
> +++ b/fs/iomap.c
> @@ -1450,6 +1450,33 @@ iomap_dio_hole_actor(loff_t length, struct iomap_dio *dio)
>  	return length;
>  }
>  
> +static loff_t
> +iomap_dio_inline_actor(struct inode *inode, loff_t pos, loff_t length,
> +		struct iomap_dio *dio, struct iomap *iomap)
> +{
> +	struct iov_iter *iter = dio->submit.iter;
> +	size_t copied;
> +
> +	BUG_ON(pos + length > PAGE_SIZE - offset_in_page(iomap->inline_data));
> +
> +	if (dio->flags & IOMAP_DIO_WRITE) {
> +		loff_t size = inode->i_size;
> +
> +		if (pos > size)
> +			memset(iomap->inline_data + size, 0, pos - size);
> +		copied = copy_from_iter(iomap->inline_data + pos, length, iter);
> +		if (copied) {
> +			if (pos + copied > size)
> +				i_size_write(inode, pos + copied);
> +			mark_inode_dirty(inode);
> +		}
> +	} else {
> +		copied = copy_to_iter(iomap->inline_data + pos, length, iter);
> +	}
> +	dio->size += copied;
> +	return copied;
> +}
> +
>  static loff_t
>  iomap_dio_actor(struct inode *inode, loff_t pos, loff_t length,
>  		void *data, struct iomap *iomap)
> @@ -1467,6 +1494,8 @@ iomap_dio_actor(struct inode *inode, loff_t pos, loff_t length,
>  		return iomap_dio_bio_actor(inode, pos, length, dio, iomap);
>  	case IOMAP_MAPPED:
>  		return iomap_dio_bio_actor(inode, pos, length, dio, iomap);
> +	case IOMAP_INLINE:
> +		return iomap_dio_inline_actor(inode, pos, length, dio, iomap);
>  	default:
>  		WARN_ON_ONCE(1);
>  		return -EIO;
> -- 
> 2.18.0
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-xfs" in
> the body of a message to majordomo at vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html



  reply	other threads:[~2018-07-03 16:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-02 14:54 [Cluster-devel] more iomap inline enablement Christoph Hellwig
2018-07-02 14:54 ` [Cluster-devel] [PATCH 1/3] iomap: refactor iomap_dio_actor Christoph Hellwig
2018-07-03 16:07   ` Darrick J. Wong
2018-07-02 14:54 ` [Cluster-devel] [PATCH 2/3] iomap: support direct I/O to inline data Christoph Hellwig
2018-07-03 16:06   ` Darrick J. Wong [this message]
2018-07-02 14:54 ` [Cluster-devel] [PATCH 3/3] iomap: add inline data support to iomap_readpage_actor Christoph Hellwig
2018-07-03 16:06   ` Darrick J. Wong

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=20180703160651.GY5711@magnolia \
    --to=darrick.wong@oracle.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).