Hi Roland, > Linus, please consider pulling from > > master.kernel.org:/pub/scm/linux/kernel/git/roland/infiniband.git > ummunotify > > This tree is also available from kernel.org mirrors at: > > git://git.kernel.org/pub/scm/linux/kernel/git/roland/infiniband.git > ummunotify > > This will get "ummunotify," a new character device that allows a > userspace library to register for MMU notifications; this is > particularly useful for MPI implementions (message passing libraries > used in HPC) to be able to keep track of what wacky things consumers > do to their memory mappings. My colleague Jeff Squyres from the Open > MPI project posted a blog entry about why MPI wants this: > > http://blogs.cisco.com/ciscotalk/performance/comments/better_linux_memory_tracking/ > > His summary of ummunotify: > > "It’s elegant, doesn’t require strange linker tricks, and seems to > work in all cases. Yay!" > > This code went through several review iterations on lkml and was in > -mm and -next for quite a few weeks. Andrew is OK with merging it (I > think -- Andrew please correct me if I misunderstood you).
I'm sorry. I haven't review this code and I didn't track this discussion carefully. but I have one stupid question. May I ask? Can I this version already solved fork() + COW issue? if so, could you please explain what happen at fork. Obviously RDMA point to either parent or child page, not both. but Corrent COW rule is, first touch process get copyed page and other process still own original page. I think it's unpecected behavior form RDMA. -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
