> per_cpu data is statically allocated, at compile-time. And it doesn't work
> for modules.
>
> These hashed locks need to be dynamically allocated (one per filesystem) and
> they need to work from modules.
Ok.
>
> And this hashed lock is not a per-cpu thing. (No locks are!) It just uses
> NR_CPUS to decide how big the hash should be.
Isn't that what the IBM kmalloc_per_cpu() was for ? (I think the patch
was from Dipankar)
-Andi
-
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/
This archive was generated by hypermail 2b29 : Tue Apr 15 2003 - 22:00:34 EST