From: Christoph Hellwig <hch@lst.de>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] gfs2 iomap dealock, IOMAP_F_UNBALANCED
Date: Tue, 9 Apr 2019 14:15:09 +0200 [thread overview]
Message-ID: <20190409121508.GA9532@lst.de> (raw)
In-Reply-To: <20190408134405.GA15023@quack2.suse.cz>
On Mon, Apr 08, 2019 at 03:44:05PM +0200, Jan Kara wrote:
> > We won't be able to do a log flush while another transaction is
> > active, but that's what's needed to clean dirty pages. iomap doesn't
> > allow us to put the block allocation into a separate transaction from
> > the page writes; for that, the opposite to the page_done hook would
> > probably be needed.
>
> I agree that a ->page_prepare() hook would be probably the cleanest
> solution for this.
That doesn't sound too bad to me.
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de>
To: Jan Kara <jack@suse.cz>
Cc: "Andreas Gruenbacher" <agruenba@redhat.com>,
"Christoph Hellwig" <hch@lst.de>,
cluster-devel <cluster-devel@redhat.com>,
"Dave Chinner" <david@fromorbit.com>,
"Ross Lagerwall" <ross.lagerwall@citrix.com>,
"Mark Syms" <Mark.Syms@citrix.com>,
"Edwin Török" <edvin.torok@citrix.com>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
linux-mm@kvack.org
Subject: Re: gfs2 iomap dealock, IOMAP_F_UNBALANCED
Date: Tue, 9 Apr 2019 14:15:09 +0200 [thread overview]
Message-ID: <20190409121508.GA9532@lst.de> (raw)
In-Reply-To: <20190408134405.GA15023@quack2.suse.cz>
On Mon, Apr 08, 2019 at 03:44:05PM +0200, Jan Kara wrote:
> > We won't be able to do a log flush while another transaction is
> > active, but that's what's needed to clean dirty pages. iomap doesn't
> > allow us to put the block allocation into a separate transaction from
> > the page writes; for that, the opposite to the page_done hook would
> > probably be needed.
>
> I agree that a ->page_prepare() hook would be probably the cleanest
> solution for this.
That doesn't sound too bad to me.
next prev parent reply other threads:[~2019-04-09 12:15 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-21 13:13 [Cluster-devel] gfs2 iomap dealock, IOMAP_F_UNBALANCED Andreas Gruenbacher
2019-03-21 13:13 ` Andreas Gruenbacher
2019-03-21 21:43 ` [Cluster-devel] " Dave Chinner
2019-03-21 21:43 ` Dave Chinner
2019-03-21 23:01 ` [Cluster-devel] " Andreas Gruenbacher
2019-03-21 23:01 ` Andreas Gruenbacher
2019-03-22 0:21 ` [Cluster-devel] " Andreas Gruenbacher
2019-03-22 0:21 ` Andreas Gruenbacher
2019-03-27 16:49 ` [Cluster-devel] " Ross Lagerwall
2019-03-27 16:49 ` Ross Lagerwall
2019-03-28 16:51 ` [Cluster-devel] " Christoph Hellwig
2019-03-28 16:51 ` Christoph Hellwig
2019-03-29 22:13 ` [Cluster-devel] " Andreas Gruenbacher
2019-03-29 22:13 ` Andreas Gruenbacher
2019-04-07 7:32 ` [Cluster-devel] " Christoph Hellwig
2019-04-07 7:32 ` Christoph Hellwig
2019-04-08 8:53 ` [Cluster-devel] " Andreas Gruenbacher
2019-04-08 8:53 ` Andreas Gruenbacher
2019-04-08 13:44 ` [Cluster-devel] " Jan Kara
2019-04-08 13:44 ` Jan Kara
2019-04-09 12:15 ` Christoph Hellwig [this message]
2019-04-09 12:15 ` Christoph Hellwig
2019-04-09 12:27 ` [Cluster-devel] " Andreas Gruenbacher
2019-04-09 12:27 ` 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=20190409121508.GA9532@lst.de \
--to=hch@lst.de \
/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.