linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Neil Brown <neilb-l3A5Bk7waGM@public.gmane.org>
To: Chuck Lever <chuck.lever-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
Cc: "J. Bruce Fields"
	<bfields-uC3wQj2KruNg9hUCZPvPmw@public.gmane.org>,
	Alan Cox <alan-qBU/x9rampVanCEyBjwyrvXRex20P6io@public.gmane.org>,
	"Patrick J. LoPresti"
	<lopresti-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
	Andi Kleen <andi-Vw/NltI1exuRpAAqCnN02g@public.gmane.org>,
	linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-nfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-kernel
	<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: Proposal: Use hi-res clock for file timestamps
Date: Thu, 19 Aug 2010 10:52:18 +1000	[thread overview]
Message-ID: <20100819105218.7620ec29@notabene> (raw)
In-Reply-To: <20100819094136.24fef59b@notabene>

On Thu, 19 Aug 2010 09:41:36 +1000
Neil Brown <neilb-l3A5Bk7waGM@public.gmane.org> wrote:

> So I agree that this is probably more of an issue for directories than for
> files, and that implementing it just for directories would be a sensible
> first step with lower expected overhead - just my reasoning seems to be a bit
> different.

Just to be sure we are on the same page:
  file_update_time would always refer to current_nfsd_time, but nfsd would
  only update current_nfsd_time when a directory was examined (and the other
  conditions were met).


So my current thinking on how this would look - names have been changed:

 - global timespec 'current_fs_precise_time' is zeroed when
   current_kernel_time moves backwards and is protected by a seqlock

 - current_fs_time would be
         now = max(current_kernel_time(), current_fs_precise_time)
         return timespec_trunc(now, sb->s_time_gran)
   (with appropriate seqlock protection)

 - new function in fs/inode.c
         get_precise_time(timestamp)
                cft = current_fs_time()
                if (timestamp == cft)
                   write_seqlock()
                   if cft == current_fs_precise_time
                        current_fs_precise_time.tv_nsec++
                   else if cft > current_fs_precise_time
                        current_fs_precise_time = cft
                   write_sequnlock()
                return timestamp

  - nfsd xdr response routine does
             ts = inode->i_mtime
             if (S_ISDIR(inode->i_mode))
                ts = get_precise_time(ts)
             xdr_encode_timespec(ts)


get_precise_time() probably needs a bit more subtlety to handle different
s_time_gran values and possible races, but I think it is fairly close.

Then if we ever had an xstat or similar that could ask for precise
timestamps, it just makes a similar call to get_precise_time.
Also if we added code later to use a hires timer on hardware where it was
efficient, get_precise_time could test for that and become a no-op

Yes, I should probably turn this into a patch ... maybe another day.

NeilBrown
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2010-08-19  0:52 UTC|newest]

Thread overview: 42+ 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
     [not found] ` <AANLkTimnyXKahtjaFeSsgcq=xMy-pP3na1jidQhZ-dt2-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-08-13 18:45   ` john stultz
2010-08-13 18:57     ` Patrick J. LoPresti
2010-08-13 19:09       ` john stultz
     [not found]         ` <1281726579.2810.10.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
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-17 14:54   ` Andi Kleen
     [not found]     ` <87aaolwar8.fsf-3rXA9MLqAseW/qJFnhkgxti2O/JbrIOy@public.gmane.org>
2010-08-17 17:41       ` J. Bruce Fields
     [not found]         ` <20100817174134.GA23176-uC3wQj2KruNg9hUCZPvPmw@public.gmane.org>
2010-08-17 18:29           ` Andi Kleen
2010-08-17 19:04             ` J. Bruce Fields
     [not found]               ` <20100817190447.GA28049-uC3wQj2KruNg9hUCZPvPmw@public.gmane.org>
2010-08-17 19:18                 ` Patrick J. LoPresti
     [not found]                   ` <AANLkTi=w1UA5ZZDBigpxMiL7A7DnbnQhLkg62JZpC6Ri-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-08-17 19:39                     ` Alan Cox
     [not found]                       ` <20100817203941.729830b7-qBU/x9rampVanCEyBjwyrvXRex20P6io@public.gmane.org>
2010-08-17 19:29                         ` J. Bruce Fields
     [not found]                           ` <20100817192937.GD26609-uC3wQj2KruNg9hUCZPvPmw@public.gmane.org>
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
     [not found]                                 ` <20100818173203.GC32430-uC3wQj2KruNg9hUCZPvPmw@public.gmane.org>
2010-08-18 18:15                                   ` Chuck Lever
     [not found]                                     ` <0F91AB9D-0E14-4384-ADD6-0A467C3ABFAC-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
2010-08-18 23:41                                       ` Neil Brown
2010-08-19  0:52                                         ` Neil Brown [this message]
2010-08-19  2:08                                           ` J. Bruce Fields
     [not found]                                             ` <20100819020803.GA30151-uC3wQj2KruNg9hUCZPvPmw@public.gmane.org>
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
     [not found]                             ` <20100817205441.200ab9a4-qBU/x9rampVanCEyBjwyrvXRex20P6io@public.gmane.org>
2010-08-17 19:43                               ` Patrick J. LoPresti
     [not found]                                 ` <AANLkTi=BB-zVFyCLgC+RWai9FFecaOad=pUC2=XFnY3J-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-08-17 19:45                                   ` J. Bruce Fields
2010-08-18 18:12                           ` J. Bruce Fields
2010-08-19  1:41                             ` john stultz
     [not found]                               ` <AANLkTi=cx31Mgfe7FxJz6LUmTKFR4=9KEBgbFsNLjiSE-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-08-19  2:31                                 ` J. Bruce Fields
     [not found]                                   ` <20100819023106.GB30151-uC3wQj2KruNg9hUCZPvPmw@public.gmane.org>
2010-08-19  3:17                                     ` john stultz
2010-08-19 22:53                                       ` J. Bruce Fields
     [not found]             ` <20100817182920.GD18161-u0/ZJuX+froe6aEkudXLsA@public.gmane.org>
2010-08-17 18:50               ` Patrick J. LoPresti
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=20100819105218.7620ec29@notabene \
    --to=neilb-l3a5bk7wagm@public.gmane.org \
    --cc=alan-qBU/x9rampVanCEyBjwyrvXRex20P6io@public.gmane.org \
    --cc=andi-Vw/NltI1exuRpAAqCnN02g@public.gmane.org \
    --cc=bfields-uC3wQj2KruNg9hUCZPvPmw@public.gmane.org \
    --cc=chuck.lever-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org \
    --cc=linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-nfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=lopresti-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;
as well as URLs for NNTP newsgroup(s).