On Wed, Jun 26, 2013 at 12:33 PM, Peter Zijlstra <pet...@infradead.org> wrote: > On Tue, Jun 25, 2013 at 12:51:23PM +0200, Ingo Molnar wrote: >> A syscall (ioctl?) to dump all current vmas into the mmap update stream >> (to form a starting point) might be handy - that would remove the >> fragility and overhead of parsing /proc/ details. > > Its more difficult than that though :/ Suppose not all mmap events fit > in the output buffer and you're not able to read from the buffer because > you're stuck in the ioctl(). > > This means we need to either force userspace to use threads to reliably > use the feature; or complicate the ioctl() to allow vma ranges -- which > introduces an inherent race window etc.. > > Neither option are really pretty and we already have the maps parse code > -- also its not _that_ hard to parse either.
After more investigation with the author of the false sharing detection tool, I think that if the mapping changes, it is okay. The tool can detect this and drop the analysis at that address. So as long as we can flag the mapping change, we are okay. Hopefully, it does not occur frequently. If so, then I think there are bigger issues to fix on the system than false sharing. -- 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/
