From: Daejun Park <daejun7.park@samsung.com>
To: Christoph Hellwig <hch@lst.de>
Cc: Chuck Lever <cel@kernel.org>, Jeff Layton <jlayton@kernel.org>,
NeilBrown <neil@brown.name>,
Olga Kornievskaia <okorniev@redhat.com>,
Dai Ngo <Dai.Ngo@oracle.com>, Tom Talpey <tom@talpey.com>,
"Darrick J. Wong" <djwong@kernel.org>,
Sergey Bashirov <sergeybashirov@gmail.com>,
Carlos Maiolino <cem@kernel.org>,
Amir Goldstein <amir73il@gmail.com>,
"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>,
"linux-xfs@vger.kernel.org" <linux-xfs@vger.kernel.org>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Daejun Park <daejun7.park@samsung.com>
Subject: RE:(2) [PATCH] nfsd: do not return overlapping extents in a block layout
Date: Thu, 08 Oct 2026 10:43:59 +0900 [thread overview]
Message-ID: <20261008014359epcms2p81ce38cf0091bc8f75b88980e9c3f1717@epcms2p8> (raw)
In-Reply-To: <20261007131133.GB30647@lst.de>
On Wed, Oct 07, 2026 at 03:11:33PM +0200, Christoph Hellwig wrote:
> But given that you're pretty active in this part of nfsd now, can you
> also look into my earlier suggestion to allow a single map_blocks
> return multiple mappings? That solves more of the root cause of
> creating incoherencies.
I posted it here:
https://lore.kernel.org/r/20261008-xfs-nfsd-map-blocks-v1-0-560026cdccb6@samsung.com
->map_blocks now fills an array of mappings. XFS maps the whole range
of a layout under one hold of the iolock and the invalidate lock (the
latter as Darrick pointed out in the earlier thread), with one flush and
at most one log force, and nfsd checks that the extents follow each
other instead of trimming them. The window between ->map_blocks and
nfsd4_insert_layout() is narrower but still there.
next prev parent reply other threads:[~2026-10-08 1:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-07 2:03 Daejun Park via B4 Relay
2026-10-07 13:11 ` Christoph Hellwig
2026-10-07 14:58 ` Chuck Lever
2026-10-07 16:51 ` Darrick J. Wong
[not found] ` <CGME20261007131141epcas2p46e1bc1592a0789298bc9f7e13c7ad393@epcms2p8>
2026-10-08 1:43 ` Daejun Park [this message]
[not found] ` <CGME20261007165105epcas2p264fc1fd07bab1fb877a6695062f48322@epcms2p7>
2026-10-08 1:47 ` Daejun Park
2026-10-08 14:14 ` (2) " Chuck Lever
2026-10-12 2:52 ` Daejun Park
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=20261008014359epcms2p81ce38cf0091bc8f75b88980e9c3f1717@epcms2p8 \
--to=daejun7.park@samsung.com \
--cc=Dai.Ngo@oracle.com \
--cc=amir73il@gmail.com \
--cc=cel@kernel.org \
--cc=cem@kernel.org \
--cc=djwong@kernel.org \
--cc=hch@lst.de \
--cc=jlayton@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=neil@brown.name \
--cc=okorniev@redhat.com \
--cc=sergeybashirov@gmail.com \
--cc=tom@talpey.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
all inboxes | Powered by JetHome®