From: Sunil Bhargo <sunil.bhargo@broadcom.com>
To: linux-nfs@vger.kernel.org
Subject: PNFS block layouts
Date: Mon, 13 Apr 2026 09:37:04 +0530 [thread overview]
Message-ID: <CABKB_79e89d3Yq8YpT2iQT8=kH3Eyz4pA1rY6_=eRTHvaG-KLA@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 816 bytes --]
Hi,
I hope this is the proper forum for NFS PNFS related questions, if not can
you please point to the proper mailing list.
I have couple of questions regarding PNFS block layouts:-
1) Is there any limitation in Linux client regarding number of segments in
layoutget that it can handle for block layouts? By segments I mean any
limit on number of entries in blo_extents on client side
/// struct pnfs_block_layout4 {
/// pnfs_block_extent4 blo_extents<>;
/// /* extents which make up this /// layout. */
/// }; ///
2) I see that the Linux server recalls(RECALLCONFLICT) the layouts for
clients if there are more than one client requesting for iomode of
even READ for an overlapping range ? Any reason why iomode of READ should
result in conflict ?
Any pointers would be helpful.
Thanks,
Sunil Bhargo
[-- Attachment #1.2: Type: text/html, Size: 2541 bytes --]
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 5469 bytes --]
reply other threads:[~2026-04-13 4:07 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CABKB_79e89d3Yq8YpT2iQT8=kH3Eyz4pA1rY6_=eRTHvaG-KLA@mail.gmail.com' \
--to=sunil.bhargo@broadcom.com \
--cc=linux-nfs@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 read-only IMAP folder(s) and NNTP newsgroup(s).