From: Andreas Dilger <adilger@clusterfs.com>
To: Horst von Brand <vonbrand@inf.utfsm.cl>
Cc: Andi Kleen <ak@muc.de>, linux-kernel@vger.kernel.org
Subject: Re: New nanosecond stat patch for 2.5.44
Date: Mon, 28 Oct 2002 10:10:10 -0700 [thread overview]
Message-ID: <20021028171010.GD17533@clusterfs.com> (raw)
In-Reply-To: <200210272316.g9RNGQxd011519@pincoya.inf.utfsm.cl>
On Oct 27, 2002 20:16 -0300, Horst von Brand wrote:
> Andreas Dilger <adilger@clusterfs.com> said:
> > 1) It would be good if it were possible to select this with a config
> > option (I don't care which way the default goes), so that people who
> > don't need/care about the increased resolution don't need the extra
> > space in their inodes and minor extra overhead. To make this a lot
> > easier to code, having something akin to the inode_update_time()
> > which does all of the i_[acm]time updates as appropriate.
>
> Please don't. Do not create incompatible versions of the same filesystem
> just because they were written on kernels compiled with different
> configurations. Superblock flags might be OK, but what is the point then?
> Better mount flags (mount with/without finegrained timestamps)?
I don't say anything about creating incompatible versions of the same
filesystem. Configuring out nsec timestamps is no different than what
we have today. Many filesystems do not support nsec timestamps anyways.
I just see this as one of many hundreds of "tiny" features that are
added to Linux that could easily be made a config option when they
are first added, but all just end up adding a tiny bit of bloat for
people that don't need it.
Cheers, Andreas
--
Andreas Dilger
http://www-mddsp.enel.ucalgary.ca/People/adilger/
http://sourceforge.net/projects/ext2resize/
next prev parent reply other threads:[~2002-10-28 17:06 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 [this message]
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=20021028171010.GD17533@clusterfs.com \
--to=adilger@clusterfs.com \
--cc=ak@muc.de \
--cc=linux-kernel@vger.kernel.org \
--cc=vonbrand@inf.utfsm.cl \
/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