From mboxrd@z Thu Jan 1 00:00:00 1970 From: Haggai Eran Subject: Re: Status of "ummunot" branch? Date: Wed, 5 Jun 2013 10:14:04 +0300 Message-ID: <51AEE53C.2090603@mellanox.com> References: <51ADA761.2080107@mellanox.com> <51ADB948.5080903@mellanox.com> <51ADD489.3020902@mellanox.com> Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: Sender: linux-rdma-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: "Jeff Squyres (jsquyres)" Cc: Or Gerlitz , "linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" List-Id: linux-rdma@vger.kernel.org On 04/06/2013 23:13, Jeff Squyres (jsquyres) wrote: > On Jun 4, 2013, at 4:50 AM, Haggai Eran wrote: > >>> Does this mean that an MPI implementation still has to register memory upon usage, and maintain its own registered memory cache? >> Yes. However, since registration doesn't pin memory, you can leave >> registered memory regions in the cache for longer periods, and you can >> register larger memory regions without needing to back them with >> physical memory. > > Hmm; I'm confused. How does this fix the MPI-needs-to-intercept-freed-memory problem? Well, there is no problem if an application frees registered memory (in an on-demand paging memory region) and that memory is returned to the OS. The OS will invalidate these pages, and the HCA will no longer be able to use them. This means that the registration cache doesn't have to de-register memory immediately when it is freed. Haggai -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html