From: Christoph Hellwig <hch@lst.de>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH 11/34] iomap: move IOMAP_F_BOUNDARY to gfs2
Date: Wed, 30 May 2018 12:10:03 +0200 [thread overview]
Message-ID: <20180530101003.GA31419@lst.de> (raw)
In-Reply-To: <e14b3cfb-73ca-e712-e1e9-4ceabc8c7b6d@redhat.com>
On Wed, May 30, 2018 at 11:02:08AM +0100, Steven Whitehouse wrote:
> In that case,? maybe it would be simpler to drop it for GFS2. Unless we
> are getting a lot of benefit from it, then we should probably just follow
> the generic pattern here. Eventually we'll move everything to iomap, so
> that the bh mapping interface will be gone. That implies that we might be
> able to drop it now, to avoid this complication during the conversion.
>
> Andreas, do you see any issues with that?
I suspect it actually is doing the wrong thing today. It certainly
does for SSDs, and it probably doesn't do a useful thing for modern
disks with intelligent caches either.
next prev parent reply other threads:[~2018-05-30 10:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180523144357.18985-1-hch@lst.de>
[not found] ` <20180523144357.18985-10-hch@lst.de>
2018-05-30 5:49 ` [Cluster-devel] [PATCH 09/34] iomap: inline data should be an iomap type, not a flag Darrick J. Wong
[not found] ` <20180523144357.18985-12-hch@lst.de>
2018-05-30 5:50 ` [Cluster-devel] [PATCH 11/34] iomap: move IOMAP_F_BOUNDARY to gfs2 Darrick J. Wong
2018-05-30 9:30 ` Steven Whitehouse
2018-05-30 9:59 ` Christoph Hellwig
2018-05-30 10:02 ` Steven Whitehouse
2018-05-30 10:10 ` Christoph Hellwig [this message]
2018-05-30 10:12 ` Steven Whitehouse
2018-05-30 11:03 ` 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=20180530101003.GA31419@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 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).