All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: Andrea Arcangeli <andrea@suse.de>
Cc: Andi Kleen <ak@suse.de>, John Alvord <jalvo@mbay.net>,
	Linus Torvalds <torvalds@transmeta.com>,
	linux-kernel@vger.kernel.org
Subject: Re: module mess in -CURRENT
Date: Thu, 14 Nov 2002 19:18:26 +0100	[thread overview]
Message-ID: <20021114191826.A11146@wotan.suse.de> (raw)
In-Reply-To: <20021114180117.GM31697@dualathlon.random>

On Thu, Nov 14, 2002 at 07:01:17PM +0100, Andrea Arcangeli wrote:
> On Thu, Nov 14, 2002 at 06:40:49PM +0100, Andi Kleen wrote:
> > > Owens' kbuild-2.5 handled it a different way and didn't need exact
> > > timings. That is especially important since nanosecond time accuracy is
> > 
> > You may not believe it, but there are projects other than the kernel
> > that do use make too.
> > 
> > > impossible if you are handling a collection of machines doing the
> > > work. NTP is accurate, but not that accurate.
> > 
> > The patch does not actually implement nanosecond resolution, but
> > jiffies resolution (1ms on 2.5), which is easily reachable with NTP.
> 
> 1msec still leave a reasonable window open IMHO. this problem would need
> sequence numbers updated atomically to be solved correctly without
> regard to the timing that may vary depending on the hardware IMHO (so
> that it could still work on a 1Thz cpu even if it's not a pratical
> matter for at least this decade).
> 

The API is ready for nanoseconds so when you feel the need you can 
convert it to using do_gettimeofday()

-Andi

  reply	other threads:[~2002-11-14 18:11 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20021114000206.A8245@infradead.org.suse.lists.linux.kernel>
     [not found] ` <Pine.LNX.4.44.0211131655580.6810-100000@home.transmeta.com.suse.lists.linux.kernel>
2002-11-14 10:19   ` module mess in -CURRENT Andi Kleen
2002-11-14 17:32     ` John Alvord
2002-11-14 17:40       ` Andi Kleen
2002-11-14 18:01         ` Andrea Arcangeli
2002-11-14 18:18           ` Andi Kleen [this message]
2002-11-15  0:27           ` Jamie Lokier
2002-11-15  0:46             ` Linus Torvalds
2002-11-15  3:38               ` Andi Kleen
2002-11-15 18:26                 ` Kai Henningsen
2002-11-15 18:14               ` Linux 2.5.47 -- Trouble booting Xwindows Mark Hamblin
2002-11-14  0:02 module mess in -CURRENT Christoph Hellwig
2002-11-14  0:59 ` Linus Torvalds
2002-11-14  1:05   ` Christoph Hellwig
2002-11-14  2:27   ` Alan Cox
2002-11-14  2:32     ` Linus Torvalds
2002-11-14  5:07       ` Rusty Russell
2002-11-14  4:36     ` Rusty Russell
2002-11-14 14:32       ` Alan Cox
2002-11-14 18:54   ` Roman Zippel
2002-11-14  4:06 ` Rusty Russell

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=20021114191826.A11146@wotan.suse.de \
    --to=ak@suse.de \
    --cc=andrea@suse.de \
    --cc=jalvo@mbay.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.