Re: Scalability problem (kmap_lock) with -aa kernels
Hugh Dickins (hugh@veritas.com)
Wed, 20 Mar 2002 18:15:10 +0000 (GMT)
My guess: persistent kmaps are okay, kmapped high pagetables are okay,
persistent kmapped high pagetables are okay. What's wrong is how we
flush_all_zero_pkmaps on all cpus, synchronously while holding the
kmap_lock everyone needs to get a new kmap (and hopefully more often,
just inc or dec the pkmap_count of kmap already got). That's what
cries out for redesign: it's served us well but should now be improved.
Hugh
-
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/