From: Andreas Dilger <adilger@clusterfs.com>
To: Mark Mielke <mark@mark.mielke.cc>
Cc: Andi Kleen <ak@muc.de>, linux-kernel@vger.kernel.org
Subject: Re: Nanosecond resolution for stat(2)
Date: Mon, 23 Sep 2002 23:21:05 -0600 [thread overview]
Message-ID: <20020924052105.GV7215@clusterfs.com> (raw)
In-Reply-To: <20020924003502.A3226@mark.mielke.cc>
On Sep 24, 2002 00:35 -0400, Mark Mielke wrote:
> The behaviour does seem wrong. Resolution should not be faked to be
> more accurate than the granularity offered by the underlying file
> system. Timestamps can be persistently stored, or stored for longer
> periods of times, for all sorts of reasons beyond 'make', each with
> consequence that cannot be determined here.
>
> What would it take to get microsecond or better time stored in ext[23]?
Not very much. We have been thinking about this for a while already.
The microsecond-resolution times would be stored in a "large inode"
or in an extended attribute if the inode is a regular-sized one. The
latter would be a pretty big performance hit for most applications if
it were only the u-second data that were being stored in the EA space.
We are also looking at a better method of storing the EA data so that
it is more efficient than the current EA implementation, but that is
mostly tangential to your concerns.
Cheers, Andreas
--
Andreas Dilger
http://www-mddsp.enel.ucalgary.ca/People/adilger/
http://sourceforge.net/projects/ext2resize/
next prev parent reply other threads:[~2002-09-24 5:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-23 21:48 Nanosecond resolution for stat(2) Andi Kleen
2002-09-24 4:05 ` Andrew Pimlott
2002-09-24 4:35 ` Mark Mielke
2002-09-24 5:21 ` Andreas Dilger [this message]
2002-09-24 5:13 ` Neil Brown
[not found] <20020923214836.GA8449@averell.suse.lists.linux.kernel>
[not found] ` <20020924040528.GA22618@pimlott.net.suse.lists.linux.kernel>
2002-09-24 12:10 ` Andi Kleen
[not found] ` <15759.62593.58936.153791@notabene.cse.unsw.edu.au.suse.lists.linux.kernel>
2002-09-24 12:21 ` 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=20020924052105.GV7215@clusterfs.com \
--to=adilger@clusterfs.com \
--cc=ak@muc.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mark@mark.mielke.cc \
/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.