From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jason Gunthorpe Subject: Re: Status of "ummunot" branch? Date: Wed, 12 Jun 2013 15:17:42 -0600 Message-ID: <20130612211742.GA8625@obsidianresearch.com> References: <20130605181853.GB1946@obsidianresearch.com> <20130605190529.GA3044@obsidianresearch.com> <51B023B9.9050000@mellanox.com> <20130607235731.GA25942@obsidianresearch.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: Sender: linux-rdma-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: "Jeff Squyres (jsquyres)" Cc: Liran Liss , Haggai Eran , Or Gerlitz , "linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" , Shachar Raindel List-Id: linux-rdma@vger.kernel.org On Wed, Jun 12, 2013 at 09:10:57PM +0000, Jeff Squyres (jsquyres) wrote: > > Another way to look at it is "specify IO access permissions" for > > address space ranges. This could be useful to implement a buffer > > pool to be used for a specific MR only, yet still map/unmap memory > > within this pool on the fly to optimize physical memory > > utilization. In this case, you would provide smaller ranges than > > 2^64... > Hmm; I'm not sure I understand. > > Userspace doesn't control what virtual addresses it gets back from > mmap/etc. Yes, it can, via MAP_FIXED. There are lots of fun tricks you can play using that. Jason -- 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