linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andreas Gruenbacher <agruenba@redhat.com>
To: Christoph Hellwig <hch@lst.de>
Cc: cluster-devel@redhat.com, linux-ext4@vger.kernel.org,
	linux-fsdevel@vger.kernel.org,
	Andreas Gruenbacher <agruenba@redhat.com>
Subject: [PATCH 0/1] iomap: Direct I/O for inline data
Date: Wed, 27 Jun 2018 02:39:05 +0200	[thread overview]
Message-ID: <20180627003906.15571-1-agruenba@redhat.com> (raw)

Here's a patch that implements direct I/O for inline data.  Direct I/O
to inline data is a bit weird because it's not direct in the usual
sense, but since Christoph's been asking for it ...

The usual alignment restrictions to the logical block size of the
underlying block device still apply.  I don't see a reason for changing
that; the resulting behavior would only become very weird for no
benefit.

I've tested this against a hacked-up version of gfs2.  However, the
"real" gfs2 will keep falling back to buffered I/O for writes to inline
data: gfs2 takes a shared lock during direct I/O, and writing to the
inode under that shared lock is not allowed.  Ext4 may become the first
actual user of this part of the patch.

Thanks,
Andreas

Andreas Gruenbacher (1):
  iomap: Direct I/O to inline data

 fs/iomap.c | 28 ++++++++++++++++++++++++++++
 1 file changed, 28 insertions(+)

-- 
2.17.1

             reply	other threads:[~2018-06-27  0:39 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-27  0:39 Andreas Gruenbacher [this message]
2018-06-27  0:39 ` [PATCH 1/1] iomap: Direct I/O for inline data Andreas Gruenbacher
2018-06-27  1:44   ` kbuild test robot
2018-06-29  8:56   ` Christoph Hellwig
2018-06-29 14:40     ` Andreas Gruenbacher
2018-06-29 16:01       ` Christoph Hellwig
2018-06-29 17:02         ` Andreas Gruenbacher
2018-07-01  6:13           ` Christoph Hellwig
2018-07-01  6:29       ` Christoph Hellwig
2018-07-01 21:44         ` Andreas Gruenbacher
2018-06-27 11:14 ` [PATCH 0/1] " Andreas Gruenbacher
2018-06-29  8:43   ` Christoph Hellwig
2018-06-29 11:01     ` Andreas Gruenbacher

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=20180627003906.15571-1-agruenba@redhat.com \
    --to=agruenba@redhat.com \
    --cc=cluster-devel@redhat.com \
    --cc=hch@lst.de \
    --cc=linux-ext4@vger.kernel.org \
    --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).