On Fri, Feb 15, 2002 at 11:07:26AM -0800, Andrew Morton wrote:
> Simon Kirby wrote:
> >
> > Not sure if this is related, but I still can't get 2.4 or 2.5 kernels to
> > actually read and write at the same time during a large file copy between
> > two totally separate devices (eg: from hda1 to hdc1). "vmstat 1" shows
> > reads with no writing for about 6-8 seconds followed by writes with no
> > reading for about 5-6 seconds, repeat.
>
> That's different.
>
> It tends to be the case that when the dirty-data-generator hits
> a particular threshold, it blocks while we write out vast amounts
> of data. So the throughput is very lumpy.
>
> It's probable that it can be tamed a bit by fiddling with the
> /proc/sys/vm/bdflush parameters.
I did try fiddling with bdflush, and I was able to get them to read and
write at what looked like the same time, but the resolution of "vmstat 1"
wasn't really good enough to see. Also, I think the overall throughput
was the same, where as it should be roughly twice as high (shouldn't it
be possible to read and write as fast as the lowest speed of both
drives?).
> > Is there a patch available that could fix this?
>
> The -aa patches fiddle extensively with the bdflush thresholds and logic.
> There's stuff in there which might addresses this.
I'll take a look at this.
Simon-
[ Stormix Technologies Inc. ][ NetNation Communications Inc. ]
[ sim@stormix.com ][ sim@netnation.com ]
[ Opinions expressed are not necessarily those of my employers. ]
-
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/
This archive was generated by hypermail 2b29 : Fri Feb 15 2002 - 21:01:09 EST