On Sat, Sep 09 2000, Ravi K. Swamy wrote:
Well, yes and no. If you have enough memory to hold it all in cache, then there's no point in starting a flush early. However, if the cp as stalled we are indeed not flushing when we should. I'll try and reproduce it here.
I have 512MB of RAM. When I do things like untar a 20MB kernel src tree it does untar really quickly but then within a minute I hear the 10-20 seconds of syncing to the hard disk.
Right and that didn't happen. If cp doesn't return, it is an entirely different problem. I'm banging my head against fs/buffer.c atm looking at this.
The corruption is now a known issue that I'm looking into.
Thanks a lot, this is the first version of the packet writing code that has worked for me, I'm going to set it up on a machine at work, it's an IDE HP CD-RW drive.
Great, remember to be careful, we are still some way from a beta quality product 8)
Sorry about that...
Is this version of ksymoops okay?
[snip]
Trace; c024b865 <__mon_yday+4385/5fa0>
Looks a bit weird, where the heck is this coming from?
--
* Jens Axboe