It has to flush that whole tar job you just did, which it did in memory
:)
> User CPU 0%
> System CPU 0%
> Idle CPU 99%
>
> So where did it wait???
>
> Here comes what latencytimes show:
>
> Worst 20 latency times of 5061 measured in this period.
> usec cause mask start line/file address end line/file
> 322263 reacqBKL 1 1375/sched.c c01138b4 697/sched.c
> 216174 BKL 1 30/inode.c c016b971 52/inode.c
> 158328 BKL 9 742/block_dev.c c0144d51 697/sched.c
OK, these three are not acceptable...adding them to the "list".
-- Robert M. Love rml at ufl.edu rml at tech9.net- 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/