From: kaih@khms.westfalen.de (Kai Henningsen)
To: torvalds@transmeta.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] nanosecond resolution for stat(2)
Date: 24 Sep 2002 08:51:00 +0200 [thread overview]
Message-ID: <8XSRl9U1w-B@khms.westfalen.de> (raw)
In-Reply-To: <Pine.LNX.4.33.0209231154520.3512-100000@penguin.transmeta.com>
torvalds@transmeta.com (Linus Torvalds) wrote on 23.09.02 in <Pine.LNX.4.33.0209231154520.3512-100000@penguin.transmeta.com>:
> On Mon, 23 Sep 2002, Andi Kleen wrote:
> >
> > Some drivers (like mouse drivers or tty) do dubious inode [mac] time
> > accesses of the on disk inode and without even marking it dirty. This is
> > likely a bug.
>
> No, it is intentional. At least some versions of "w" (maybe all) will use
> the tty access times to judge how long the tty has been idle. The point is
> that this is all information that is interesting (and useful), but not
> worth sending to disk - it is useful only as long as the inode remains
> locked in-core for other reasons, ie being in use.
>
> (It's not only "not worth it" to send to disk, but it would be positively
> wrong to even _try_ updating the disk with the access times, since we want
> these things to work even with a read-only /dev).
Should there perhaps be a special function for this - say
device_atime_update_nowrite() or something like that, to make it clearer
what happens? You could put something like you just wrote as a comment
before that function ...
MfG Kai
prev parent reply other threads:[~2002-09-24 7:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20020923184705.GA8195@averell>
2002-09-23 18:57 ` Linus Torvalds
2002-09-23 20:05 ` Andi Kleen
2002-09-24 6:51 ` Kai Henningsen [this message]
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=8XSRl9U1w-B@khms.westfalen.de \
--to=kaih@khms.westfalen.de \
--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 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®