From: Chris Friesen <cfriesen@nortelnetworks.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: New nanosecond stat patch for 2.5.44
Date: Sun, 27 Oct 2002 20:23:32 -0500 [thread overview]
Message-ID: <3DBC9194.5090006@nortelnetworks.com> (raw)
In-Reply-To: <aphqqo$261$1@cesium.transmeta.com>
H. Peter Anvin wrote:
> We probably need to revamp struct stat anyway, to support a larger
> dev_t, and possibly a larger ino_t (we should account for 64-bit ino_t
> at least if we have to redesign the structure.) At that point I would
> really like to advocate for int64_t ts_sec and uint32_t ts_nsec and
> quite possibly a int32_t ts_taidelta to deal with leap seconds... I'd
> personally like struct timespec to look like the above everywhere.
For filesystems can we get away with just the 64-bit nanoseconds? By my
calculations that gives something like 584 years--do we need to worry
about files older than that?
Chris
--
Chris Friesen | MailStop: 043/33/F10
Nortel Networks | work: (613) 765-0557
3500 Carling Avenue | fax: (613) 765-2986
Nepean, ON K2H 8E9 Canada | email: cfriesen@nortelnetworks.com
next prev parent reply other threads:[~2002-10-28 1:17 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 [this message]
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
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=3DBC9194.5090006@nortelnetworks.com \
--to=cfriesen@nortelnetworks.com \
--cc=hpa@zytor.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
Powered by JetHome