All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chuck Lever <chuck.lever@oracle.com>
To: Neil Brown <neilb@suse.de>
Cc: nfs@lists.sourceforge.net
Subject: Re: [PATCH 4/5] mount.nfs: Add new files for supporting string-ified mount options
Date: Fri, 10 Aug 2007 17:07:26 -0400	[thread overview]
Message-ID: <46BCD38E.3000809@oracle.com> (raw)
In-Reply-To: <18107.50044.333597.209861@notabene.brown>

[-- Attachment #1: Type: text/plain, Size: 1035 bytes --]

Neil Brown wrote:
> On Thursday August 9, chuck.lever@oracle.com wrote:
>> Introduce support files which contain code that builds string mount
>> options and passes them to the kernel.  This is a pre-requisite for
>> actually enabling /sbin/mount.nfs to do text-based mounts.
>>
>> This is only partially complete at the moment, but is presented so that
>> folks can start banging on the kernel mount option string parsing code.
>> There are clearly still parts that are not implemented quite yet, such
>> as bg and retry support, but it should be enough to get going.
>>
>> Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
>> ---
> 
>> +
>> +static int retry_opt = 10000;		/* 10,000 minutes ~= 1 week */
> 
> Why one week?  Why not "MAX_INT"? retry_opt is never actually used, so
> I cannot guess.

retry=10000 is the default setting.  According to the nfs(5) man page, 
this is about 1 week.

The plan is to extract the retry setting from the mount options string 
if it exists, and use the default value of 10000 if it does not.

[-- Attachment #2: chuck.lever.vcf --]
[-- Type: text/x-vcard, Size: 290 bytes --]

begin:vcard
fn:Chuck Lever
n:Lever;Chuck
org:Oracle Corporation;Corporate Architecture: Linux Projects Group
adr:;;1015 Granger Avenue;Ann Arbor;MI;48104;USA
title:Principal Member of Staff
tel;work:+1 248 614 5091
x-mozilla-html:FALSE
url:http://oss.oracle.com/~cel
version:2.1
end:vcard


[-- Attachment #3: Type: text/plain, Size: 315 bytes --]

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/

[-- Attachment #4: Type: text/plain, Size: 140 bytes --]

_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

      reply	other threads:[~2007-08-10 21:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-09 21:37 [PATCH 4/5] mount.nfs: Add new files for supporting string-ified mount options Chuck Lever
2007-08-10  1:46 ` Neil Brown
2007-08-10 21:07   ` Chuck Lever [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=46BCD38E.3000809@oracle.com \
    --to=chuck.lever@oracle.com \
    --cc=neilb@suse.de \
    --cc=nfs@lists.sourceforge.net \
    /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.