|
From: Geert U. <ge...@li...> - 2001-06-17 08:53:12
|
On Sun, 17 Jun 2001, Ken Tyler wrote:
> On Sun, 17 Jun 2001, Roman Zippel wrote:
> > 'make -j 10' or 'make -j 3' shouldn't make a difference for the memory.
>
> Not disputing what you say but I would have thought that the running makes
> and gccs are still being brought into 'execution' memory, from disk
> buffers producing more mem activity, and also the more tasks mean more
> context switches and more opportunity for errors.
Yes, the probability for seeing problems is higher with a higher -j value, so
I'd expect to see more problems with higher -j values.
BUT, this is statistics! It's quite possible a single run at -j 10 will reveal
no problems, while it will at -j 3.
I'm suffering from the same problem w.r.t. writing corrupted data to my DDS-1
under 2.4.x: so far ik _looks_ like it doesn't happen under 2.2.17, but I can't
prove it due to the nature of statistics. It's much easier to prove a problem
is there (you need only one `true' report), then proving the problem is not
there (you need infinite `false' reports). In the mean time I found one problem
under 2.2.19 too, so either it got introduced between 2.2.17 and 2.2.19, or it
does happen under 2.2.17 too.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@li...
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
|