> You could try instrumenting the paths in bdflush and kswapd, to see
> what really happens when they run crazy. This would help a lot.
:-( My knowledge of the kernel is too poor and I have too few time to
study it.
I tried the suggestion of A.Arcangeli about size interval. The test is
always
You could try instrumenting the paths in bdflush and kswapd, to see
what really happens when they run crazy. This would help a lot.
:-( My knowledge of the kernel is too poor and I have too few time to
study it.
I tried the suggestion of A.Arcangeli about size interval. The test is
always
Hi!
I found the time to make some tests with 2.4 and the blk-13B patch.
It performs very well, no process starvation, no missed merges,
etc., but sometimes it happens dbflush and kswapd start eating
100% CPU for about 20-30 secs.:
11:02am up 18 min, 5 users, load average: 2.74, 1.97, 1.15
Hi!
I found the time to make some tests with 2.4 and the blk-13B patch.
It performs very well, no process starvation, no missed merges,
etc., but sometimes it happens dbflush and kswapd start eating
100% CPU for about 20-30 secs.:
11:02am up 18 min, 5 users, load average: 2.74, 1.97, 1.15
4 matches
Mail list logo