06.08.2013 Views

pSOSystem System Calls - Read

pSOSystem System Calls - Read

pSOSystem System Calls - Read

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

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

Notes<br />

See Also<br />

Hex Mnemonic Description<br />

0x24 ERR_SEGADDR Incorrect segment starting address.<br />

0x25 ERR_SEGFREE Segment is already unallocated.<br />

1. Refer to <strong>pSO<strong>System</strong></strong> <strong>System</strong> Concepts for the algorithms used to merge<br />

neighboring free segments.<br />

2. There is no notion of segment ownership. A segment can be returned by a task<br />

other than the one that originally allocated it.<br />

3. If there are tasks waiting for memory from this region, then such requests will<br />

be re-examined and allocation granted where possible — in the order of the wait<br />

queue (FIFO or by task priority).<br />

4. Note that the calling task may be preempted if a task waiting for memory<br />

segment is unblocked as a result of the returned segment, and that task has<br />

higher priority.<br />

Multiprocessor Considerations<br />

None, since regions are strictly local resources. rn_retseg() can be called only<br />

from the local node.<br />

Callable From<br />

■ Task<br />

rn_getseg<br />

1-118 <strong>pSO<strong>System</strong></strong> <strong>System</strong> <strong>Calls</strong>

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

Saved successfully!

Ooh no, something went wrong!