From: Carlos Maiolino <cem@kernel.org>
To: linux-xfs@vger.kernel.org, Daejun Park <daejun7.park@samsung.com>
Cc: dai.ngo@oracle.com, hch@lst.de, djwong@kernel.org,
dgc@kernel.org, sergeybashirov@gmail.com, cel@kernel.org,
jlayton@kernel.org, linux-nfs@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] xfs: map pNFS layouts to the end of the extent again
Date: Thu, 08 Oct 2026 15:32:44 +0200 [thread overview]
Message-ID: <179146636404.378461.1931859114820869361.b4-ty@kernel.org> (raw)
In-Reply-To: <20261006003425epcms2p586728e55ff5f9bbabc506b672fc4a421@epcms2p5>
On Tue, 06 Oct 2026 09:34:25 +0900, Daejun Park wrote:
> Since commit 36ca6f11424a ("xfs: fix overlapping extents returned for
> pNFS LAYOUTGET"), xfs_fs_map_blocks() maps only the range that nfsd asks
> for. For O_DIRECT, the Linux block layout client asks for the range of
> the I/O at hand, so it now needs a LAYOUTGET for every O_DIRECT read or
> write to a part of a file it has no layout for yet, where the first
> LAYOUTGET used to return the whole extent. Each LAYOUTGET is a round
> trip, and xfs_fs_map_blocks() takes the iolock exclusively and writes
> back and invalidates the page cache of the file for it.
>
> [...]
Applied to for-next, thanks!
[1/1] xfs: map pNFS layouts to the end of the extent again
commit: e3c682dd11303a95ff82ea63b9172dce788578d4
Best regards,
--
Carlos Maiolino <cem@kernel.org>
prev parent reply other threads:[~2026-10-08 13:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20261006003425epcms2p586728e55ff5f9bbabc506b672fc4a421@epcms2p5>
2026-10-06 0:34 ` Daejun Park
2026-10-06 5:13 ` Darrick J. Wong
[not found] ` <CGME20261006003425epcms2p586728e55ff5f9bbabc506b672fc4a421@epcms2p8>
2026-10-06 5:48 ` Daejun Park
2026-10-06 15:23 ` (2) " Darrick J. Wong
2026-10-08 13:32 ` Carlos Maiolino [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=179146636404.378461.1931859114820869361.b4-ty@kernel.org \
--to=cem@kernel.org \
--cc=cel@kernel.org \
--cc=daejun7.park@samsung.com \
--cc=dai.ngo@oracle.com \
--cc=dgc@kernel.org \
--cc=djwong@kernel.org \
--cc=hch@lst.de \
--cc=jlayton@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=sergeybashirov@gmail.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®