Getting Started with QNX Neutrino - QNX Software Systems

More documents

Recommendations

Info

Scheduling and the real world © 2009, QNX Software Systems GmbH & Co. KG. Summary Neutrino offers a rich set of scheduling options with threads, the primary scheduling elements. Processes are defined as a unit of resource ownership (e.g., a memory area) and contain one or more threads. Threads can use any of the following synchronization methods: • mutexes — allow only one thread to own the mutex at a given point in time. • semaphores — allow a fixed number of threads to “own” the semaphore. • sleepons — allow a number of threads to block on a number of objects, while allocating the underlying condvars dynamically to the blocked threads. • condvars — similar to sleepons except that the allocation of the condvars is controlled by the programmer. • joining — allows a thread to synchronize to the termination of another thread. • barriers — allows threads to wait until a number of threads have reached the synchronization point. Note that mutexes, semaphores, and condition variables can be used between threads in the same or different processes, but that sleepons can be used only between threads in the same process (because the library has a mutex “hidden” in the process’s address space). As well as synchronization, threads can be scheduled (using a priority and a scheduling algorithm), and they’ll automatically run on a single-processor box or an SMP box. Whenever we talk about creating a “process” (mainly as a means of porting code from single-threaded implementations), we’re really creating an address space with one thread running in it — that thread starts at main() or at fork() or vfork() depending on the function called. 78 Chapter 1 • Processes and Threads April 30, 2009
Chapter 2 Message Passing In this chapter. . . Messaging fundamentals 81 Message passing and client/server 82 Network-distributed message passing 85 What it means for you 85 Multiple threads 86 Using message passing 90 Pulses 113 Message passing over a network 124 Priority inheritance 130 April 30, 2009 Chapter 2 • Message Passing 79
Page 1 and 2:
QNX Neutrino RTOS Getting Started w
Page 3 and 4:
Contents About This Guide xi What y
Page 5 and 6:
© 2009, QNX Software Systems GmbH
Page 7 and 8:
Page 9 and 10:
List of Figures A process as a cont
Page 11:
About This Guide April 30, 2009 Abo
Page 14 and 15:
Typographical conventions © 2009,
Page 17:
Foreword to the First Edition by Pe
Page 20 and 21:
Page 23 and 24:
Page 25 and 26:
Page 27:
Page 31 and 32:
Page 33 and 34:
Page 35 and 36:
Page 37 and 38:
Page 39 and 40:
Page 41 and 42:
Page 43 and 44: © 2009, QNX Software Systems GmbH
Page 93: © 2009, QNX Software Systems GmbH
Page 98 and 99: Message passing and client/server
Page 100 and 101: Message passing and client/server
Page 102 and 103: Multiple threads © 2009, QNX Softw
Page 104 and 105: Multiple threads © 2009, QNX Softw
Page 106 and 107: Using message passing © 2009, QNX
Page 130 and 131: Pulses © 2009, QNX Software System
Page 140 and 141: Message passing over a network © 2
Page 142 and 143: Message passing over a network © 2
Page 144 and 145:
Message passing over a network © 2
Page 146 and 147:
Priority inheritance © 2009, QNX S
Page 148 and 149:
Priority inheritance © 2009, QNX S
Page 151:
Chapter 3 Clocks, Timers, and Getti
Page 154 and 155:
Clocks and timers © 2009, QNX Soft
Page 156 and 157:
Page 158 and 159:
Page 160 and 161:
Page 162 and 163:
Using timers © 2009, QNX Software
Page 164 and 165:
Page 166 and 167:
Page 168 and 169:
Page 170 and 171:
Page 172 and 173:
Page 174 and 175:
Page 176 and 177:
Advanced topics © 2009, QNX Softwa
Page 178 and 179:
Page 180 and 181:
Page 183:
Chapter 4 Interrupts In this chapte
Page 186 and 187:
Neutrino and interrupts © 2009, QN
Page 188 and 189:
Page 190 and 191:
Page 192 and 193:
Writing interrupt handlers © 2009,
Page 194 and 195:
Page 196 and 197:
Page 198 and 199:
Page 200 and 201:
TIME TIME Writing interrupt handler
Page 202 and 203:
Page 204 and 205:
Summary © 2009, QNX Software Syste
Page 207 and 208:
Page 209 and 210:
Page 211 and 212:
Page 213 and 214:
Page 215 and 216:
Page 217 and 218:
Page 219 and 220:
Page 221 and 222:
Page 223 and 224:
Page 225 and 226:
Page 227 and 228:
Page 229 and 230:
Page 231 and 232:
Page 233 and 234:
Page 235 and 236:
Page 237 and 238:
Page 239 and 240:
Page 241 and 242:
Page 243 and 244:
Page 245 and 246:
Page 247 and 248:
Page 249 and 250:
Page 251 and 252:
Page 253 and 254:
Page 255 and 256:
Page 257 and 258:
Page 259 and 260:
Page 261 and 262:
Page 263 and 264:
Page 265 and 266:
Page 267 and 268:
Page 269 and 270:
Page 271 and 272:
Page 273 and 274:
Page 275 and 276:
Page 277 and 278:
Page 279 and 280:
Page 281 and 282:
Page 283 and 284:
Page 285 and 286:
Page 287 and 288:
Page 289 and 290:
Page 291 and 292:
Page 293 and 294:
Page 295 and 296:
Page 297 and 298:
Page 299:
Page 303 and 304:
Page 305 and 306:
Page 307 and 308:
Page 309 and 310:
Page 311 and 312:
Page 313 and 314:
Page 315 and 316:
Page 317 and 318:
Page 319:
Appendix B Calling 911 In this appe
Page 322 and 323:
Seeking professional help © 2009,
Page 324 and 325:
Seeking professional help © 2009,
Page 327:
Appendix C Sample Programs In this
Page 330 and 331:
atoz.c © 2009, QNX Software System
Page 332 and 333:
atoz.c © 2009, QNX Software System
Page 334 and 335:
time1.c © 2009, QNX Software Syste
Page 336 and 337:
time1.c © 2009, QNX Software Syste
Page 338 and 339:
tp1.c © 2009, QNX Software Systems
Page 340 and 341:
tt1.c © 2009, QNX Software Systems
Page 343 and 344:
Page 345 and 346:
Page 347 and 348:
Page 349 and 350:
Page 351 and 352:
Index ! /dev/null resource manager
Page 353 and 354:
Page 355 and 356:
Page 357 and 358:
Page 359 and 360:
Page 361 and 362:
Page 363 and 364:
Page 365 and 366:
Page 367 and 368:
Page 369 and 370:
Page 371 and 372:
Page 373 and 374:
Page 375 and 376:
Page 377 and 378:
Page 379 and 380:
Page 381 and 382:
Page 383 and 384:
Page 385 and 386:
Page 387 and 388:
show all

Getting Started with QNX Neutrino - QNX Software Systems

Create successful ePaper yourself

Delete template?

Save as template?