Linux CIFS filesystem development
 help / color / mirror / Atom feed
From: Jeff Layton <jlayton-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Suresh Jayaraman <sjayaraman-l3A5Bk7waGM@public.gmane.org>
Cc: Steve French <smfrench-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
	linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH -v3] cifs: add attribute cache timeout (actimeo) tunable
Date: Tue, 30 Nov 2010 13:29:38 -0500	[thread overview]
Message-ID: <20101130132938.7c72ae62@corrin.poochiereds.net> (raw)
In-Reply-To: <4CF5302A.7030200-l3A5Bk7waGM@public.gmane.org>

On Tue, 30 Nov 2010 22:41:06 +0530
Suresh Jayaraman <sjayaraman-l3A5Bk7waGM@public.gmane.org> wrote:

> >> +/*
> >>   * MAX_REQ is the maximum number of requests that WE will send
> >>   * on one socket concurrently. It also matches the most common
> >>   * value of max multiplex returned by servers.  We may
> >> diff --git a/fs/cifs/connect.c b/fs/cifs/connect.c
> >> index 32fa4d9..ee7cb11 100644
> >> --- a/fs/cifs/connect.c
> >> +++ b/fs/cifs/connect.c
> >> @@ -105,6 +105,7 @@ struct smb_vol {
> >>  	unsigned int wsize;
> >>  	bool sockopt_tcp_nodelay:1;
> >>  	unsigned short int port;
> >> +	unsigned long actimeo; /* attribute cache timeout (jiffies) */
> > 
> > 	^^^ unused variable?
> 
> We use this to store the actimeo value in jiffies as we parse the mount
> options in cifs_parse_mount_options() below in this patch.
> 
> Did you mean this could be avoided?
> 

Sorry, I misread the patch and thought it was a local variable in
cifs_parse_mount_options. Please disregard that comment.

-- 
Jeff Layton <jlayton-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>

      parent reply	other threads:[~2010-11-30 18:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-30 13:50 [PATCH -v3] cifs: add attribute cache timeout (actimeo) tunable Suresh Jayaraman
     [not found] ` <1291125010-12772-1-git-send-email-sjayaraman-l3A5Bk7waGM@public.gmane.org>
2010-11-30 13:55   ` Suresh Jayaraman
     [not found]     ` <4CF50258.3080100-l3A5Bk7waGM@public.gmane.org>
2010-11-30 14:13       ` Jeff Layton
2010-11-30 14:08   ` Jeff Layton
     [not found]     ` <20101130090825.78865825-9yPaYZwiELC+kQycOl6kW4xkIHaj4LzF@public.gmane.org>
2010-11-30 17:07       ` Suresh Jayaraman
2010-11-30 17:11       ` Suresh Jayaraman
     [not found]         ` <4CF5302A.7030200-l3A5Bk7waGM@public.gmane.org>
2010-11-30 18:29           ` Jeff Layton [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=20101130132938.7c72ae62@corrin.poochiereds.net \
    --to=jlayton-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
    --cc=linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=sjayaraman-l3A5Bk7waGM@public.gmane.org \
    --cc=smfrench-Re5JQEeQqe8AvxtiuMwx3w@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