Hi! > I am resubmitting this patch because I believe that the discussion > has shown this to be an acceptable solution. I have fixed the 32 bit > build errors, but other than that change, the code is the same as > Roland's V3 patch. > > From: Roland Dreier <rola...@cisco.com> > > As discussed in <http://article.gmane.org/gmane.linux.drivers.openib/61925> > and follow-up messages, libraries using RDMA would like to track > precisely when application code changes memory mapping via free(), > munmap(), etc. Current pure-userspace solutions using malloc hooks > and other tricks are not robust, and the feeling among experts is that > the issue is unfixable without kernel help.
I do not know. I still believe that this does not belong in the kernel; application should not need to trace itself to know what it does. Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html