Messages in this thread | | | Date | Wed, 20 Jun 2001 10:12:38 -0600 | From | Richard Gooch <> | Subject | Re: [RFC] Early flush (was: spindown) |
| |
Daniel Phillips writes: > On Wednesday 20 June 2001 06:39, Richard Gooch wrote: > > Starting I/O immediately if there is no load sounds nice. However, > > what about the other case, when the disc is already spun down (and > > hence there's no I/O load either)? I want the system to avoid doing > > writes while the disc is spun down. I'm quite happy for the system to > > accumulate dirtied pages/buffers, reclaiming clean pages as needed, > > until it absolutely has to start writing out (or I call sync(2)). > > I'd like that too, but what about sync writes? As things stand now, > there is no option but to spin the disk back up. To get around this > we'd have to change the basic behavior of the block device and > that's doable, but it's an entirely different proposition than the > little patch above.
I don't care as much about sync writes. They don't seem to happen very often on my boxes.
> You know about this project no doubt: > > http://noflushd.sourceforge.net/
Only vaguely. It's huge. Over 2300 lines of C code and >560 lines in .h files! As you say, not really lightweight. There must be a better way. Also, I suspect (without having looked at the code) that it doesn't handle memory pressure well. Things may get nasty when we run low on free pages.
Regards,
Richard.... Permanent: rgooch@atnf.csiro.au Current: rgooch@ras.ucalgary.ca - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |