linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jim Rees <rees@umich.edu>
To: john stultz <johnstul@us.ibm.com>
Cc: "Patrick J. LoPresti" <lopresti@gmail.com>, linux-nfs@vger.kernel.org
Subject: Re: Proposal: Use hi-res clock for file timestamps
Date: Fri, 13 Aug 2010 16:52:49 -0400	[thread overview]
Message-ID: <20100813205249.GA12404@merit.edu> (raw)
In-Reply-To: <1281731186.2810.17.camel@localhost.localdomain>

john stultz wrote:

  > How about using getnstimeofday() only if the kernel clocksource is tsc?
  > Presumably anyone running into this problem would have modern high
  > performance hardware with working tsc.
  
  This might be difficult, as clocksources can change while the system is
  running. Further, any checks for specific clocksources would be very
  architecture specific. A fast-timekeeping flag could be used, but would
  be a fairly subjective metric (ie: would there be issues if the fast
  clock on a  slower system is slower then a slow clock on a fast system,
  etc).
  
  That's partly why I suggested a mount option.

It just would be nice if the kernel could "do the right thing" without the
user having to set some option or sysctl.  The problem is infrequently seen,
difficult to diagnose, and not obvious as to whether it's a client or server
issue.  I don't think your typical user, or even your typical professional
sysadmin, is going to get this right if it requires a setting.

Having said that, it's not obvious to me how to do this automatically.

  reply	other threads:[~2010-08-13 20:52 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-13 18:25 Proposal: Use hi-res clock for file timestamps Patrick J. LoPresti
2010-08-13 18:45 ` john stultz
2010-08-13 18:57   ` Patrick J. LoPresti
2010-08-13 19:09     ` john stultz
2010-08-13 20:53       ` Patrick J. LoPresti
2010-08-14 16:45         ` Patrick J. LoPresti
2010-08-15  1:50         ` Bret Towe
2010-08-13 19:57     ` Jim Rees
2010-08-13 20:26       ` john stultz
2010-08-13 20:52         ` Jim Rees [this message]
2010-08-17 14:54 ` Andi Kleen
2010-08-17 17:41   ` J. Bruce Fields
2010-08-17 18:29     ` Andi Kleen
2010-08-17 18:50       ` Patrick J. LoPresti
2010-08-17 19:04       ` J. Bruce Fields
2010-08-17 19:18         ` Patrick J. LoPresti
2010-08-17 19:39           ` Alan Cox
2010-08-17 19:29             ` J. Bruce Fields
2010-08-17 19:52               ` Alan Cox
2010-08-18  5:53               ` Neil Brown
2010-08-18 14:46                 ` Patrick J. LoPresti
2010-08-18 17:32                 ` J. Bruce Fields
2010-08-18 18:15                   ` Chuck Lever
2010-08-18 23:41                     ` Neil Brown
2010-08-19  0:52                       ` Neil Brown
2010-08-19  2:08                         ` J. Bruce Fields
2010-08-19  2:44                           ` Neil Brown
2010-08-19 22:46                             ` J. Bruce Fields
2010-08-18 23:47                   ` Neil Brown
2010-08-18 17:50                 ` Andi Kleen
2010-08-18 18:54                   ` J. Bruce Fields
2010-08-18 19:25                     ` Andi Kleen
2010-08-18 19:30                       ` J. Bruce Fields
2010-08-17 19:34             ` Patrick J. LoPresti
2010-08-17 19:54               ` Alan Cox
2010-08-17 19:43                 ` Patrick J. LoPresti
2010-08-17 19:45                   ` J. Bruce Fields
2010-08-18 18:12               ` J. Bruce Fields
2010-08-19  1:41                 ` john stultz
2010-08-19  2:31                   ` J. Bruce Fields
2010-08-19  3:17                     ` john stultz
2010-08-19 22:53                       ` J. Bruce Fields
2010-08-18 18:20       ` David Woodhouse
2010-08-18 18:32         ` Patrick J. LoPresti
2010-08-18 18:53         ` Andi Kleen

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=20100813205249.GA12404@merit.edu \
    --to=rees@umich.edu \
    --cc=johnstul@us.ibm.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=lopresti@gmail.com \
    /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;
as well as URLs for NNTP newsgroup(s).