public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: Rob Landley <landley@trommello.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: The return of the return of crunch time (2.5 merge candidate list 1.6)
Date: 26 Oct 2002 09:53:26 +0200	[thread overview]
Message-ID: <p7365vptz49.fsf@oldwotan.suse.de> (raw)
In-Reply-To: Rob Landley's message of "26 Oct 2002 04:01:47 +0200"

Rob Landley <landley@trommello.org> writes:

I have some patches to offer better than second resolution for stat.
That is needed for parallel make on MP systems, because otherwise it
cannot detect changes that need less than a second to execute. With CPUs
being as fast as they are and getting even faster currently it is becomming 
a bigger problem. You don't hit it that easily with gcc because it's 
getting faster slower than cpus are getting faster so it's usually slower
than a second, but some people use make rules with other compilers or other 
commands.

I see it in the same category as "necessary changes" similar to 32bit dev_t. 

Linux already has several filesystems in tree that support ns or better than s 
resolution in their underlying formats (XFS,JFS,NFSv3,VFAT)

Patches available on request or older versions from 
ftp://ftp.firstfloor.org/pub/ak/v2.5/nsec*
They don't actually add ns resolution, but jiffies resolution, which
is 1ms on 2.5 and should be good enough for now. It reuses reserved fields
in struct stat and doesn't need any user interface changes.

It requires editing of a lot of file systems in a straight forward way,
so should be better done before the stable series starts.

There are some minor compatbility issues with fs that only support 
second timestamps like ext2/ext3, see nsec.notes in the ftp directory
or past threads on that on the list.

-Andi

       reply	other threads:[~2002-10-26  7:47 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200210251557.55202.landley@trommello.org.suse.lists.linux.kernel>
2002-10-26  7:53 ` Andi Kleen [this message]
2002-10-26  8:13   ` The return of the return of crunch time (2.5 merge candidate list 1.6) Andreas Dilger
     [not found]   ` <20021026190906.GA20571@pimlott.net>
2002-10-27  7:01     ` Andi Kleen
2002-10-27 15:20       ` Andrew Pimlott
2002-10-27 17:57         ` Rob Landley
2002-10-28  4:06           ` Andrew Pimlott
2002-10-28  4:32             ` Andi Kleen
2002-10-28  4:09           ` Andi Kleen
2002-10-28  4:30         ` Andi Kleen
2002-01-15 17:44           ` Pavel Machek
2002-11-08 22:02             ` Andrew Pimlott
2002-10-28  6:03           ` Andrew Pimlott
2002-10-25 20:57 Rob Landley
2002-10-26  2:42 ` Hans Reiser
2002-10-27 15:11   ` Rob Landley
2002-10-28  0:27     ` Hans Reiser
2002-10-26 15:09 ` Eric W. Biederman

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=p7365vptz49.fsf@oldwotan.suse.de \
    --to=ak@suse.de \
    --cc=landley@trommello.org \
    --cc=linux-kernel@vger.kernel.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