Note that the saga of trying to push ummunotify upstream to Linux ended up with Linus essentially saying "fix your own network stack; don't put this in the main kernel."
He's was right back then. With a 2nd "customer" for this kind of thing (cuda), that equation might be changing, but I'll leave that to Nvidia to push on Linus. :-) Something like ummunotify should be in the ibcore area in the kernel. And at least initially, probably something like this should be in the cuda kernel module(s). Just my $0.02... On Nov 8, 2012, at 9:38 AM, Shamis, Pavel wrote: > Another good reason for ummunotify kernel module > (http://lwn.net/Articles/345013/) > > Pavel (Pasha) Shamis > --- > Computer Science Research Group > Computer Science and Math Division > Oak Ridge National Laboratory > > On Nov 8, 2012, at 9:08 AM, Jeff Squyres wrote: > > On Nov 8, 2012, at 8:51 AM, Rolf vandeVaart wrote: > > Not sure. I will look into this. And thank you for the feedback Jens! > > FWIW, I +1 Jens' request. MPI implementations are able to handle network > registration mechanisms via standard memory hooks (their hooks are actually > pretty terrible, but for the most part, they are generally functional). > > If CUDA requires registered memory, then it should also provide hooks so that > MPI implementations can "just make it work" from the users' perspective (and > please please please provide BETTER hooks than verbs / glibc malloc!). > > -- > Jeff Squyres > jsquy...@cisco.com<mailto:jsquy...@cisco.com> > For corporate legal information go to: > http://www.cisco.com/web/about/doing_business/legal/cri/ > > > _______________________________________________ > users mailing list > us...@open-mpi.org > http://www.open-mpi.org/mailman/listinfo.cgi/users > > > _______________________________________________ > users mailing list > us...@open-mpi.org > http://www.open-mpi.org/mailman/listinfo.cgi/users -- Jeff Squyres jsquy...@cisco.com For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/
