On Jun 10, 2013, at 11:56 AM, Liran Liss <[email protected]> wrote:
>> "Register all address space" is the moral equivalent of not having userspace >> registration, so let's talk about it in those terms. Specifically, there's >> a subtle >> difference between: >> >> a) telling verbs to register (0...2^64) >> --> Which is weird because it tells verbs to register memory that isn't in >> my >> address space > > 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. So how is what you're talking about different than regular/reactive memory registration? (vs. pre-emptively registering a whole pile of memory that doesn't exist yet) Specifically: I'm confused because you said you could (preemptively) register some small regions (that assumedly don't yet exist in your virtual memory address space) and use them as memory pools. But given that userspace doesn't control its virtual address ranges, I'm not sure how that's useful. -- Jeff Squyres [email protected] For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/ -- 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
