From: "Mkrtchyan, Tigran" <tigran.mkrtchyan@desy.de>
To: Cedric Blancher <cedric.blancher@gmail.com>
Cc: Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: Linux NFSv4.1 client with Linux NFSv4.1 server, getting block size of exported filesystem?
Date: Thu, 4 Apr 2024 17:38:08 +0200 (CEST) [thread overview]
Message-ID: <1246600035.9928999.1712245088183.JavaMail.zimbra@desy.de> (raw)
In-Reply-To: <CALXu0UfExxAtoqnFUYbMG=Mpwc0HU3qtb0vuiygXLf6bt=4AaA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 958 bytes --]
Hi Ced,
no, it can not. However, spec defines two attributes, maxread and maxwrite, that can indicate
client preferred IO request sizes:
https://datatracker.ietf.org/doc/html/rfc5661#section-5.8.2.20
In pNFS case, an additional layout-specific option, that can override those values.
Best regards,
Tigran.
----- Original Message -----
> From: "Cedric Blancher" <cedric.blancher@gmail.com>
> To: "Linux NFS Mailing List" <linux-nfs@vger.kernel.org>
> Sent: Wednesday, 3 April, 2024 19:59:16
> Subject: Linux NFSv4.1 client with Linux NFSv4.1 server, getting block size of exported filesystem?
> Good evening!
>
> Assuming a Linux 6.6 NFSv4.1 client and a Linux 6.6 NFSv4.1 server,
> can the NFSv4.1 client obtain the exact block size of the exported
> filesystem (e.g. ReiserFS, btrfs, ext4, ...) via fstatat()/stat()?
>
> Ced
> --
> Cedric Blancher <cedric.blancher@gmail.com>
> [https://plus.google.com/u/0/+CedricBlancher/]
> Institute Pasteur
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 2826 bytes --]
prev parent reply other threads:[~2024-04-04 15:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-03 17:59 Linux NFSv4.1 client with Linux NFSv4.1 server, getting block size of exported filesystem? Cedric Blancher
2024-04-04 15:38 ` Mkrtchyan, Tigran [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=1246600035.9928999.1712245088183.JavaMail.zimbra@desy.de \
--to=tigran.mkrtchyan@desy.de \
--cc=cedric.blancher@gmail.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).