On Tue, 20 Jun 2006 23:38:57 -0400
Mark Lord <[email protected]> wrote:
> > I just gave it a try here. With or without a suspend/resume cycle after
> > boot,
> > the "sync" time is much quicker. But the Dirty count in /proc/meminfo
> > still shows very huge (eg. 600MB) values that never really get smaller
> > until I type "sync". But that subsequent "sync" only takes a couple
> > of seconds now, rather than 10-20 seconds like before.
> ..
>
> Yup, behaviour is *definitely* much better now. I'm not sure why
> the /proc/meminfo "Dirty" count lags behind reality, but the disk
> is being kept much more up-to-date than without this patch.
Are you able to come up with a foolproof set of steps which would allow the
laggy-dirtiness to be reproduced by yours truly?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
