public inbox for linux-nfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Amit Gud <agud@akamai.com>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>,
	Steve Dickson <SteveD@redhat.com>,
	"gud-OYTqUY/oFF8@public.gmane.org"
	<gud-OYTqUY/oFF8@public.gmane.org>,
	"Uhlenkott, Jason" <juhlenko@akamai.com>
Subject: Re: [PATCH] NFS: Add acreg{min,max} and acdir{min,max} in milliseconds
Date: Mon, 15 Jun 2009 15:53:05 -0700	[thread overview]
Message-ID: <4A36D0D1.3000904@akamai.com> (raw)
In-Reply-To: <1244846673.32257.69.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>

Trond Myklebust wrote:
> It boils down to this: I'm extremely reluctant to get into an arms race
> of adding ever more mount options for increasingly finer-tuned attribute
> cache timeouts. While such an option may meet _your_ machine room
> requirements here and now, it becomes tiresome over the years as
> machines gain power, and people first start lobbying for millisecond
> timeouts, then microseconds, nanoseconds, pico... in order to catch up.
> 

It only makes sense to make machines more powerful and put that power to
optimum use. If keeping up with increased resolution is an issue, you
think something like "-o unit=ms acregmin=..." would be better? 'unit'
can apply to all the time related options defaulting to seconds.


AG
-- 
May the source be with you.
http://cis.ksu.edu/~gud

  parent reply	other threads:[~2009-06-15 22:52 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-10  1:32 [PATCH] NFS: Add acreg{min,max} and acdir{min,max} in milliseconds Amit Gud
2009-06-10 12:27 ` Trond Myklebust
     [not found]   ` <1244636844.24750.23.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2009-06-10 19:43     ` Amit Gud
2009-06-11  0:11       ` Trond Myklebust
2009-06-11 20:24         ` Amit Gud
2009-06-11 21:14           ` Trond Myklebust
     [not found]             ` <1244754888.5047.132.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2009-06-12 19:30               ` Amit Gud
2009-06-12 19:50                 ` Trond Myklebust
     [not found]                   ` <1244836259.19533.19.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2009-06-12 21:49                     ` Amit Gud
2009-06-12 22:44                       ` Trond Myklebust
     [not found]                         ` <1244846673.32257.69.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2009-06-15 22:53                           ` Amit Gud [this message]
2009-06-15 23:08                             ` [PATCH] NFS: Add acreg{min,max} and acdir{min, max} " NeilBrown
     [not found]                               ` <3786d1f06aae533fa82740d68985fd50.squirrel-eq65iwfR9nKIECXXMXunQA@public.gmane.org>
2009-06-15 23:19                                 ` Trond Myklebust
     [not found]                                   ` <1245107980.7470.0.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2009-06-16 16:30                                     ` Steve Dickson
2009-06-17 10:37                                       ` Neil Brown

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=4A36D0D1.3000904@akamai.com \
    --to=agud@akamai.com \
    --cc=SteveD@redhat.com \
    --cc=gud-OYTqUY/oFF8@public.gmane.org \
    --cc=juhlenko@akamai.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox