Libor> Do you mean that the set/clear parameters to do_mlock()
Libor> are the actual flags which are set/cleared by the caller?
Libor> Also, the issue remains that the flags are not reference
Libor> counted which is a problem if you are dealing with
Libor> overlapping memory region, or even if one region ends and
Libor> another begins on the same page. Since the desire is to be
Libor> able to pin any memory that a user can malloc this is a
Libor> likely scenario.
Good point... we need to figure out how to handle:
a) app registers 0x0000 through 0x17ff
b) app registers 0x1800 through 0x2fff
c) app unregisters 0x0000 through 0x17ff
d) the page at 0x1000 must stay pinned
hmm...
- R.
_______________________________________________
openib-general mailing list
[email protected]
http://openib.org/mailman/listinfo/openib-general
To unsubscribe, please visit http://openib.org/mailman/listinfo/openib-general
