linux-xfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <djwong@kernel.org>
To: Christoph Hellwig <hch@lst.de>
Cc: linux-xfs@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	avi@scylladb.com, Dave Chinner <david@fromorbit.com>
Subject: Re: reduce sub-block DIO serialisation v4
Date: Mon, 1 Feb 2021 09:51:17 -0800	[thread overview]
Message-ID: <20210201175117.GA7190@magnolia> (raw)
In-Reply-To: <20210201165825.GB9858@lst.de>

On Mon, Feb 01, 2021 at 05:58:25PM +0100, Christoph Hellwig wrote:
> On Sat, Jan 23, 2021 at 10:57:06AM -0800, Darrick J. Wong wrote:
> > On Fri, Jan 22, 2021 at 05:20:32PM +0100, Christoph Hellwig wrote:
> > > This takes the approach from Dave, but adds a new flag instead of abusing
> > > the nowait one, and keeps a simpler calling convention for iomap_dio_rw.
> > 
> > Hm.  I realized while putting together for-next branches that I really
> > would have preferred the three iomap patches at the start so that I
> > could push those parts through the iomap tree.  The changes required to
> > resequence the series is minor and the iomap changes (AFAICT) are inert
> > if the calling fs doesn't set IOMAP_DIO_OVERWRITE_ONLY, so I think it's
> > low risk to push the iomap changes into iomap-for-next as a 5.12 thing.
> > 
> > The rest of the xfs patches in this series would form the basis of a
> > second week pull request (or not) since I think I ought to evaluate the
> > effects on performance for a little longer.
> 
> So that is the reason why they aren't in for-next yet?  Or do you want
> the remaining patches resent on top of the iomap branch?

Assuming they haven't changed, I'll just push the (slightly reordered)
series out to for-next tomorrow.  Sorry, I got totally sidetracked last
week with the quota retry series nearly tripling in size with all the
requested changes... :(

--D

      reply	other threads:[~2021-02-01 17:52 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-22 16:20 reduce sub-block DIO serialisation v4 Christoph Hellwig
2021-01-22 16:20 ` [PATCH 01/11] xfs: factor out a xfs_ilock_iocb helper Christoph Hellwig
2021-01-22 16:20 ` [PATCH 02/11] xfs: make xfs_file_aio_write_checks IOCB_NOWAIT-aware Christoph Hellwig
2021-01-22 16:20 ` [PATCH 03/11] xfs: cleanup the read/write helper naming Christoph Hellwig
2021-01-22 16:20 ` [PATCH 04/11] xfs: remove the buffered I/O fallback assert Christoph Hellwig
2021-01-22 16:20 ` [PATCH 05/11] xfs: simplify the read/write tracepoints Christoph Hellwig
2021-01-22 16:20 ` [PATCH 06/11] xfs: improve the reflink_bounce_dio_write tracepoint Christoph Hellwig
2021-01-22 16:20 ` [PATCH 07/11] xfs: split the unaligned DIO write code out Christoph Hellwig
2021-01-22 16:20 ` [PATCH 08/11] iomap: rename the flags variable in __iomap_dio_rw Christoph Hellwig
2021-01-22 16:20 ` [PATCH 09/11] iomap: pass a flags argument to iomap_dio_rw Christoph Hellwig
2021-01-22 16:20 ` [PATCH 10/11] iomap: add a IOMAP_DIO_OVERWRITE_ONLY flag Christoph Hellwig
2021-01-22 16:20 ` [PATCH 11/11] xfs: reduce exclusive locking on unaligned dio Christoph Hellwig
2021-01-22 17:24   ` Darrick J. Wong
2021-01-23 18:57 ` reduce sub-block DIO serialisation v4 Darrick J. Wong
2021-02-01 16:58   ` Christoph Hellwig
2021-02-01 17:51     ` Darrick J. Wong [this message]

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=20210201175117.GA7190@magnolia \
    --to=djwong@kernel.org \
    --cc=avi@scylladb.com \
    --cc=david@fromorbit.com \
    --cc=hch@lst.de \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-xfs@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).