Confirmed users
699
edits
IPDL/Proposal:Shmem access control: Difference between revisions
Jump to navigation
Jump to search
m
IPDL/Proposal:Shmem access control (view source)
Revision as of 02:56, 27 October 2009
, 27 October 2009→Optional fine-grained access change for Shmem
mNo edit summary |
|||
| Line 3: | Line 3: | ||
New syntax | New syntax | ||
['[' access | ['[' access '|' access ']'] Shmem | ||
|access| can be one of | |access| can be one of | ||
| Line 20: | Line 20: | ||
The second |access| specifier refers to the ''other side's'' shmem access after ''receiving'' the Shmem in a message. So |+w| would mean that the other side is granted write privileges. | The second |access| specifier refers to the ''other side's'' shmem access after ''receiving'' the Shmem in a message. So |+w| would mean that the other side is granted write privileges. | ||
Fine-grained access change is optional. If no access change is specified, then it defaults to |[-r-w | Fine-grained access change is optional. If no access change is specified, then it defaults to |[-r-w|+r+w]|, which is what is currently implemented. | ||
An actor may take away particular access from itself without granting it to the other actor. This could be called a "reserved" right. The actor may later grant it to the other actor, or grant it to itself. For example | An actor may take away particular access from itself without granting it to the other actor. This could be called a "reserved" right. The actor may later grant it to the other actor, or grant it to itself. For example | ||
[-w | [-w|+r] Shmem | ||
// reserve write access for myself, but only grant read access to the other actor | // reserve write access for myself, but only grant read access to the other actor | ||