Re: New feature
Michael O'Reilly (michael@metal.iinet.net.au)
Wed, 24 Sep 1997 16:03:59 +0800
In message <m0xDmDX-0005FCC@lightning.swansea.linux.org.uk>, Alan Cox writes:
> > > The ATIME updates dirty all the inodes.
> >
> > That's true and ok, but it shouldn't be re-reading the media again
> > should it? The dirty bit should be cleared, but the buffer shouldn't
> > be marked invalid...
>
> Its writing to the disk, to write all the new atime values into the
> inode blocks
Yes, but why is it READING the disk after that? It should all still be
cached in ram (read the original article. It writes on the sync, but
then the next ls goes crazy reading the disk again. write on the sync,
fine, but why is it reading the disk?)
Michael.