26.02.2014 Views

Getting Started with QNX Neutrino - QNX Software Systems

Getting Started with QNX Neutrino - QNX Software Systems

Getting Started with QNX Neutrino - QNX Software Systems

SHOW MORE
SHOW LESS

Create successful ePaper yourself

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

Index<br />

© 2009, <strong>QNX</strong> <strong>Software</strong> <strong>Systems</strong> GmbH & Co. KG.<br />

multi-threaded server 90<br />

multipart messages 108<br />

example 108, 111<br />

IOV 108–110<br />

kernel’s view 110<br />

limitations 110<br />

multipart versus linear 113<br />

multiple threads 86<br />

ND/PID/CHIDs 102<br />

network<br />

detailed analysis 125<br />

differences from local 126<br />

network implementation 125<br />

network transparent 133<br />

network-distributed 85<br />

networked 124<br />

networked case<br />

determining how much data should have<br />

been transferred 128<br />

determining how much data was<br />

transferred 127<br />

networked overhead 127<br />

node descriptor 92<br />

not replying to the client 101<br />

notifying client 117<br />

obtaining a connection ID 92<br />

offsetting into the client’s data 107, 112<br />

peeking into a message 105<br />

phases 94<br />

priority 103<br />

process ID 92<br />

pulse<br />

MsgReceive() 114<br />

MsgReceivePulse() 114<br />

receiving 114<br />

race condition <strong>with</strong> unblock 121<br />

reading from the client’s address space 105<br />

readying a thread 82<br />

receive ID 100<br />

and reply 95<br />

receive-blocked 82<br />

diagram 82<br />

receiving only pulses 116<br />

receiving pulses only 116<br />

REPLY-blocked 165<br />

reply-blocked 83<br />

diagram 82<br />

reply-driven model 88, 101<br />

example 89<br />

important subtlety 89<br />

replying to the client 100<br />

replying <strong>with</strong> no data 101<br />

example 101<br />

resource manager 84<br />

run time installability of components 81<br />

scatter/gather<br />

defined 332<br />

SEND state<br />

diagram 82<br />

SEND-blocked 165<br />

send-blocked 83<br />

diagram 82<br />

send-driven model 88<br />

example 89<br />

important subtlety 89<br />

server 95<br />

example 96<br />

server connection ID 99<br />

server replying to client 95<br />

server/subserver 86, 87<br />

delegation of work 88<br />

SETIOV() (macro) 109<br />

SMP 86<br />

STATE_RECV state 82<br />

diagram 82<br />

STATE_REPLY state 83<br />

diagram 82<br />

STATE_SEND state 83<br />

summary 133<br />

synthetic unblock pulse 120<br />

thread and channels 98<br />

thread pool 117<br />

timeouts<br />

informing server 165<br />

timeouts and_NTO_CHF_UNBLOCK 165<br />

timer 116<br />

tracking owner of message 98<br />

transmit buffer 95<br />

transparency over network 85<br />

unblock 121<br />

unblocking<br />

_NTO_MI_UNBLOCK_REQ 123, 124<br />

354 Index April 30, 2009

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

Saved successfully!

Ooh no, something went wrong!