Look at the vmstat(1) values. I think the problem is outside afs.
Just doing this dd test but writing data directly to the ext2
target gives same behaviour, i.e. on 2.4 kernel I see most of the
CPU idle but on 2.6 kernel all that CPU amount is shown as in
wait state.
M.

chas williams - CONTRACTOR wrote:
> In message <[EMAIL PROTECTED]>,=?windows-1252?Q?Martin_MOKR
> EJ=8A?= writes:
> 
>>kernel, I ran the same test twice. The first results were discarded
>>but the data ended-up in kernel memory so on the second execution
>>the data were just written to the disk through afs (from kernel memory).
> 
> 
> i guess i am not convinced.  with a 1G cache, i saw the following:
_______________________________________________
OpenAFS-devel mailing list
[email protected]
https://lists.openafs.org/mailman/listinfo/openafs-devel

Reply via email to