[ofa-general] Memory registration redux
Jonathan Perkins
perkinjo at cse.ohio-state.edu
Mon May 11 05:13:18 PDT 2009
On Tue, May 05, 2009 at 04:57:09PM -0400, Jeff Squyres wrote:
> Roland and I chatted on the phone today; I think I now understand
> Roland's counter-proposal (I clearly didn't before). Let me try to
> summarize:
>
> 1. Add a new verb for "set this userspace flag to 1 if mr X ever becomes
> invalid"
> 2. Add a new verb for "no longer tell me if mr X ever becomes invalid"
> (i.e., remove the effects of #1)
> 3. Add run-time query indicating whether #1 works
> 4. Add [optional] memory registration caching to libibverbs
>
> Prior to talking to Roland, I had envisioned *one* flag in userspace
> that indicated whether any memory registrations had become invalid.
> Roland's idea is that there is one flag *per registration* -- you can
> instantly tell whether a specific registration is valid.
>
> Given this, let's keep the discussion going here in email -- perhaps the
> teleconference next Monday may become moot.
It looks like there has been more discussion on how to implement this
idea. Are we still planning on having this teleconference today?
--
Jonathan Perkins
http://www.cse.ohio-state.edu/~perkinjo
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL: <http://lists.openfabrics.org/pipermail/general/attachments/20090511/22e1c8ce/attachment.sig>
More information about the general
mailing list