All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kyle Rose <krose@krose.org>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-nfs@vger.kernel.org
Subject: Re: READDIRPLUS max mount option
Date: Fri, 07 Mar 2008 15:09:25 -0500	[thread overview]
Message-ID: <47D1A0F5.2070501@krose.org> (raw)
In-Reply-To: <1204919978.16746.12.camel@heimdal.trondhjem.org>


> The binary mount format is frozen forever, so the changes to nfs_mount.h
> and nfs4_mount.h are definitely NACKed.
>   
Ah. :-)  So is there no way to add mount options, or is there a 
different mechanism today?
> Otherwise, it would be nice to know why this absolutely has to be made a
> mount option rather than just having a system-wide option (either a
> module/boot parameter or a sysctl) to control the behaviour of all
> mounts.
>   
I mount multiple remote file systems.  Only one of them I own, so I'm 
willing to potentially hammer it with huge READDIRPLUS requests, while 
the others probably deserve more benign behavior. ;-)

In general, I think having system-wide defaults somewhere in proc is 
helpful---and certainly superior to a constant in the source---but there 
should really be mount-specific overrides wherever the system-wide 
default might not be globally appropriate.

Kyle

  reply	other threads:[~2008-03-07 20:09 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-07 19:37 READDIRPLUS max mount option Kyle Rose
     [not found] ` <47D1995E.6060501-x8616dYPWyvYtjvyW6yDsg@public.gmane.org>
2008-03-07 19:59   ` Trond Myklebust
2008-03-07 19:59     ` Trond Myklebust
2008-03-07 20:09     ` Kyle Rose [this message]
     [not found]       ` <47D1A0F5.2070501-x8616dYPWyvYtjvyW6yDsg@public.gmane.org>
2008-03-07 20:42         ` Trond Myklebust
2008-03-07 20:42           ` Trond Myklebust
     [not found]           ` <1204922570.16746.37.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2008-03-07 21:04             ` Kyle Rose
2008-03-07 21:04               ` Kyle Rose
     [not found]               ` <47D1ADC5.1050108-x8616dYPWyvYtjvyW6yDsg@public.gmane.org>
2008-03-09 16:16                 ` Jan Engelhardt
2008-03-09 16:16                   ` Jan Engelhardt

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=47D1A0F5.2070501@krose.org \
    --to=krose@krose.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=trond.myklebust@fys.uio.no \
    /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.