mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jamie Lokier <lk@tantalophile.demon.co.uk>
To: Bill Davidsen <davidsen@tmr.com>
Cc: Andreas Dilger <adilger@clusterfs.com>, Andi Kleen <ak@muc.de>,
	linux-kernel@vger.kernel.org
Subject: Re: New nanosecond stat patch for 2.5.44
Date: Wed, 30 Oct 2002 22:17:24 +0000	[thread overview]
Message-ID: <20021030221724.GA25231@bjl1.asuk.net> (raw)
In-Reply-To: <Pine.LNX.3.96.1021030155404.14229A-100000@gatekeeper.tmr.com>

Bill Davidsen wrote:
> I have to think about the point you raise of doing it one way or the other
> but not mixing. I had assumed that the inode of a file which was open
> would remain in core, and I want to look at the code before I form an
> opinion. If the file is not open or the inode is a non-file...

Oh, the inode of a file which is open does remain in core.  It's just
that between runs of a program like "make", the file's aren't open are
they?

> I think you may have missed the point of (4), some of the overhead of
> keeping HRT is the conversion of data to ns from some machine dependent
> information. Where possible the base information, such as a register,
> could be stored with a flag, avoiding the "convert to ns" CPU usage. The
> conversion could be done when the data was used, before save, at the time
> of a stat, etc. I have the feeling that would take some of the sting out
> of keeping HRT. It doesn't matter if it's atime, mtime or ctime, the atime
> was in response to "nobody uses HRT atime" in an earlier post.

That's some of the overhead.  The other overhead is reading the clock,
which is quite high on x86 when TSC is not available.  On a Pentium
with no reliable TSC, I think that the time for a read() system call
is comparable to the time to read the clock.

-- Jamie

  reply	other threads:[~2002-10-30 22:12 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-27 12:13 Andi Kleen
2002-10-27 14:33 ` New nanosecond stat patch for 2.5.44 - new patch II Andi Kleen
2002-10-27 21:49 ` New nanosecond stat patch for 2.5.44 Andreas Dilger
2002-10-27 22:54   ` H. Peter Anvin
2002-10-28  1:23     ` Chris Friesen
2002-10-28  1:35       ` Rob Landley
2002-11-06 13:27     ` Gabriel Paubert
2002-11-06 18:00       ` H. Peter Anvin
2002-10-27 23:16   ` Horst von Brand
2002-10-28 17:10     ` Andreas Dilger
2002-10-29 15:01   ` Bill Davidsen
2002-10-29 16:30     ` Andreas Dilger
2002-10-29 20:37       ` Bill Davidsen
2002-10-30  0:44         ` Jamie Lokier
2002-10-30 21:12           ` Bill Davidsen
2002-10-30 22:17             ` Jamie Lokier [this message]
2002-10-31  0:34               ` H. Peter Anvin
2002-11-01  1:57               ` Bill Davidsen
2002-11-01  3:32                 ` Jamie Lokier
     [not found] <20021027121318.GA2249@averell.suse.lists.linux.kernel>
     [not found] ` <20021027214913.GA17533@clusterfs.com.suse.lists.linux.kernel>
2002-10-28  4:42   ` Andi Kleen
2002-10-28  5:35     ` Andreas Dilger
     [not found]   ` <aphqqo$261$1@cesium.transmeta.com.suse.lists.linux.kernel>
     [not found]     ` <3DBC9194.5090006@nortelnetworks.com.suse.lists.linux.kernel>
2002-10-28  4:47       ` Andi Kleen
     [not found] <3ED66C83.8070608@austin.ibm.com.suse.lists.linux.kernel>
2003-05-29 21:11 ` Nightly regression runs against current bk tree Andi Kleen
2003-05-29 21:25   ` David S. Miller
2003-05-29 21:29     ` Andi Kleen
2003-05-29 21:38       ` Randy.Dunlap
2003-05-29 21:48         ` David S. Miller
2003-05-29 22:04           ` Craig Thomas
2003-05-29 22:05             ` Andi Kleen
2003-05-29 22:25               ` Cliff White
2003-05-29 23:41               ` David S. Miller
2003-05-29 21:50       ` Craig Thomas
2003-05-29 22:03         ` Andi Kleen
2003-05-29 22:16           ` Cliff White
2003-05-29 22:23           ` Nathan
2003-05-29 23:10           ` Mark Peloquin
2003-05-29 22:51     ` Mark Peloquin
2003-05-29 22:03   ` Nathan
2003-05-29 23:08     ` Mark Peloquin
2003-05-29 22:48   ` Mark Peloquin
2003-05-29 23:17     ` Andreas Dilger
2003-05-29 23:30       ` Cliff White

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=20021030221724.GA25231@bjl1.asuk.net \
    --to=lk@tantalophile.demon.co.uk \
    --cc=adilger@clusterfs.com \
    --cc=ak@muc.de \
    --cc=davidsen@tmr.com \
    --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

all inboxes | Powered by JetHome®