06.08.2013 Views

pSOSystem System Calls - Read

pSOSystem System Calls - Read

pSOSystem System Calls - Read

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

pSOS+ <strong>System</strong> <strong>Calls</strong> sm_ident<br />

Notes<br />

See Also<br />

1. Internally, the pSOS+ kernel treats a semaphore name as a 32-bit integer.<br />

However, when the application calls the kernel through the pSOS+ C language<br />

API, it passes the semaphore name as a four-byte character array.<br />

2. The pSOS+ kernel does not check for duplicate semaphore names. If duplicate<br />

semaphore names exist, an sm_ident() call can return the smid of any<br />

semaphore with the duplicate name.<br />

Multiprocessor Considerations<br />

1. sm_ident() converts a semaphore's name to its smid by using a search order<br />

determined by the node input parameter, as described in <strong>pSO<strong>System</strong></strong> <strong>System</strong><br />

Concepts. Because semaphores created and exported by different nodes may<br />

not have unique names, the result of this binding may depend on the order in<br />

which the object tables are searched.<br />

2. If the master node's Global Object Table must be searched, then the pSOS+m<br />

kernel makes a sm_ident() RSC to the master node.<br />

Callable From<br />

■ Task<br />

sm_create<br />

<strong>pSO<strong>System</strong></strong> <strong>System</strong> <strong>Calls</strong> 1-127<br />

1

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!