Linux CIFS filesystem development
 help / color / mirror / Atom feed
From: Suresh Jayaraman <sjayaraman-l3A5Bk7waGM@public.gmane.org>
To: Jeff Layton <jlayton-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] mount.cifs: manpage: add entry for "actimeo" option
Date: Wed, 01 Dec 2010 18:49:49 +0530	[thread overview]
Message-ID: <4CF64B75.9040400@suse.de> (raw)
In-Reply-To: <20101201080932.24f4386e-9yPaYZwiELC+kQycOl6kW4xkIHaj4LzF@public.gmane.org>

On 12/01/2010 06:39 PM, Jeff Layton wrote:
> On Wed,  1 Dec 2010 18:30:36 +0530
> Suresh Jayaraman <sjayaraman-l3A5Bk7waGM@public.gmane.org> wrote:
> 
>>
>> Signed-off-by: Suresh Jayaraman <sjayaraman-l3A5Bk7waGM@public.gmane.org>
>> ---
>>  mount.cifs.8 |   18 ++++++++++++++++++
>>  1 files changed, 18 insertions(+), 0 deletions(-)
>>
>> diff --git a/mount.cifs.8 b/mount.cifs.8
>> index 7d2bf69..15dc2dc 100644
>> --- a/mount.cifs.8
>> +++ b/mount.cifs.8
>> @@ -403,6 +403,24 @@ Map user accesses to individual credentials when accessing the server\&. By defa
>>  With this change, it's feasible for the server to handle permissions enforcement, so this option also implies "noperm"\&. Furthermore, when unix extensions aren't in use and the administrator has not overriden ownership using the uid= or gid= options, ownership of files is presented as the current user accessing the share\&.
>>  .RE
>>  .PP
>> +actimeo=\fIarg\fR
>> +.RS 4
>> +The time (in seconds) that the CIFS client caches attributes of a file or
>> +directory before it requests attribute information from a server. During this
>> +period the changes that occur on the server remain undetected until the client
>> +checks the server again.
>> +.sp
>> +By default, the attribute cache timeout is set to 1 second. This means more
>> +frequent on-the-wire calls to the server to check whether attributes have
>> +changed which could impact performance. With this option the users can make
> 
> "With this option, users can make a"
> 
>> +tradeoff between performance and cache metadata correctness depending on the
> 						"correctness, depending"
> 
>> +workload needs. Shorter timeouts mean better the cache coherency, but frequent
> 
> 		"Shorter timeouts mean better cache coherency, but an"
> 
>> +increased number of calls to the server. Longer timeouts mean reduced number
>> +of calls to the server at the expense of stricter cache coherency\&. The
> 
> A little unclear...maybe "Longer timeouts mean a reduced number of calls to the server but looser cache coherency."
> 
>> +actimeo value is a positive integral that can hold values between 0 and a

Doh, this word "integral" was borrowed from nfs man page. But, I agree
"integer" is correct and the nfs man page perhaps needs to be fixed too.

> 				"integer"
> 
>> +maximum value of 2^30 * HZ (frequency of timer interrupt) setting\&. 
>> +.RE
>> +.PP
>>  \-\-verbose
>>  .RS 4
>>  Print additional debugging information for the mount\&. Note that this parameter must be specified before the \-o\&. For example:
> 
> If those edits look ok, I'll add them in when I merge the patch, which
> should be soon after Steve merges the kernel patch. No need to resend.
> 

All of them look fine. Thanks for getting those finer bits correct.


-- 
Suresh Jayaraman

  parent reply	other threads:[~2010-12-01 13:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-01 13:00 [PATCH] mount.cifs: manpage: add entry for "actimeo" option Suresh Jayaraman
     [not found] ` <1291208436-12371-1-git-send-email-sjayaraman-l3A5Bk7waGM@public.gmane.org>
2010-12-01 13:09   ` Jeff Layton
     [not found]     ` <20101201080932.24f4386e-9yPaYZwiELC+kQycOl6kW4xkIHaj4LzF@public.gmane.org>
2010-12-01 13:19       ` Suresh Jayaraman [this message]
2010-12-09 14:42       ` Jeff Layton

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=4CF64B75.9040400@suse.de \
    --to=sjayaraman-l3a5bk7wagm@public.gmane.org \
    --cc=jlayton-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
    --cc=linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.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