All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Vanns <james.vanns@framestore.com>
To: lustre-devel@lists.lustre.org
Subject: [Lustre-devel] Export over NFS sets rsize to 1MB?
Date: Mon, 13 May 2013 14:19:38 +0100 (BST)	[thread overview]
Message-ID: <1975652007.19339235.1368451178426.JavaMail.root@framestore.com> (raw)
In-Reply-To: <1212911910.19338063.1368451002112.JavaMail.root@framestore.com>

Hello dev list. Apologies for a post to perhaps the wrong group but I'm having a
bit of difficulty locating any document or wiki describing how and/or where the
preferred read and write block size for NFS exports of a Lustre filesystem are
set to 1MB?

Basically we have two Lustre filesystems exported over NFSv3. Our lustre block size
is 4k and the max r/w size is 1MB. Without any special rsize/wsize options set for
the export the default one suggested to clients (MOUNT->FSINFO RPC) as the preferred
size is set to 1MB. How does Lustre figure this out? Other non-Lustre exports are generally
much less; 4, 8, 16 or 32 kilobytes.

Any hints would be appreciated. Documentation or code paths welcome as are annotated /proc locations.

Thanks,

Jim

PS. This is Lustre 1.8.8 on Linux 2.6.32

-- 
Jim Vanns
Senior Software Developer
Framestore

       reply	other threads:[~2013-05-13 13:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1212911910.19338063.1368451002112.JavaMail.root@framestore.com>
2013-05-13 13:19 ` James Vanns [this message]
2013-05-13 21:58   ` [Lustre-devel] Export over NFS sets rsize to 1MB? Dilger, Andreas
2013-05-14 15:07     ` James Vanns
2013-05-14 22:06       ` Dilger, Andreas
2013-05-14 22:06         ` Dilger, Andreas
2013-05-15  9:23         ` James Vanns
2013-05-15  9:23           ` James Vanns

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=1975652007.19339235.1368451178426.JavaMail.root@framestore.com \
    --to=james.vanns@framestore.com \
    --cc=lustre-devel@lists.lustre.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.