On 05/11/13 13:36, David Vrabel wrote: > On 05/11/13 11:24, Roger Pau Monne wrote: >> IMHO there's no reason to set a m2p override if the mapping is done in >> kernel space, so only set the m2p override when kmap_ops is set. > > Can you provide a more detailed reasoning about why this is safe?
To tell the truth, I don't understand why we need to use the m2p override for kernel space only mappings, my understanding is that this m2p override is needed for user space mappings only (where we actually end up doing two mappings, one in kernel space and one in user space). For kernel space I don't see why we need to do anything else than setting the right p2m translation. > Did you consider other ways of improving scalability? e.g., a > per-bucket read-write lock. Not really, the main focus of this patch is to optimize kernel space only mappings (like the ones done in blkback), so why go down this road when we can actually remove the need for a lock at all in this case? -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
