INtimeÂ® 3.1 Software - tenAsys

More documents

Recommendations

Info

INtime <strong>3.1</strong> <strong>Software</strong> Semaphores A semaphore is a counter that takes positive integer values called units. Threads release units to and wait for units from the semaphore. A semaphore can synchronize a thread’s actions with other threads and can also be used to provide mutual exclusion for data or a resource (although a mutex may be better in that case). A thread can release one or more units to a semaphore. Waiting can be done for a single unit only. A semaphore does not protect against priority inversion (described in Priority inversions on page 37). Deleting a semaphore causes all threads waiting for that semaphore to be woken up with an ERROR_INVALID_HANDLE error code. Semaphore functions include: iwin32 calls CreateSemaphore or RtCreateSemaphore OpenSemaphore or RtOpenSemaphore ReleaseSemaphore or RtReleaseSemaphore WaitForMultipleObjects or RtWaitForMultipleObjects WaitForSingleObject or RtWaitForSingleObject iwin32x calls RtCreateSemaphore RtOpenSemaphore RtReleaseSemaphore RtWaitForMultipleObjects RtWaitForSingleObjects Events An event is a flag that can be set (signaled) or reset; it can be reset manually (once set, it remains set until explicitly reset by a ResetEvent call, independent of how many threads are woken up) or automatically (after waking up one thread, the event is reset). Deleting an event causes all threads waiting for that event to be woken up with an ERROR_INVALID_HANDLE error code. Event functions include: iwin32 calls CreateEvent or RtCreateEvent OpenEvent or RtOpenEvent PulseEvent or RtPulseEvent ResetEvent or RtResetEvent SetEvent or RtSetEvent WaitForMultipleObjects or RtWaitForMultipleObjects WaitForSingleObject or RtWaitForSingleObject iwin32x calls RtCreateEvent RtOpenEvent RtPulseEvent RtResetEvent RtSetEvent RtWaitForMultipleObjects RtWaitForSingleObjects 146
Appendix B: The iwin32 subsystem Shared memory Mutexes and semaphores allow threads to synchronize, but what if you want to exchange data You can use INtime objects such as mailboxes, but in iwin32 you also find shared memory. Shared memory is memory that has been allocated by one process and that can be accessed by other processes as well. To access shared memory created by another process you need to know its name. Since every process has its own virtual address space, a shared memory object must be mapped into a process' address space. Different processes may use different local addresses to access the same shared memory! The shared memory is only deleted when all its handles are closed. Space for shared memory objects comes from an iwin32 virtual memory pool; the maximum size of that pool is configurable. For information about memory configuration, see Running the INtime Configuration Utility on page 68. It is up to the communicating threads to agree on a method of queuing data in the shared memory as necessary. Shared memory functions include: iwin32 calls iwin32x calls RtCreateSharedMemory RtCreateSharedMemory RtOpenSharedMemory RtOpenSharedMemory RtGetPhysicalAddress RtGetPhysicalAddress RtMapMemory RtMapMemory RtUnmapMemory – RtUnmapSharedMemory RtUnmapSharedMemory Timers Any thread can be made to wait for a given time by using Sleep or RtSleepFt. A timer is simply a thread that gets woken up when its time passes. Creating a timer means that a thread is created that calls a user-provided function after a given time. This thread is a special one: it can not be suspended or resumed and its priority can not be changed. It should not call ExitThread and can not be terminated by TerminateThread. Timer functions include: iwin32 calls iwin32x calls RtCancelTimer – RtCreateTimer – RtDeleteTimer – RtGetClockResolution RtGetClockResolution RtGetClockTime RtGetClockTime 147
Page 1 and 2:
U S E R ’ S M A N U A L INtime ®
Page 3 and 4:
Before you begin This guide describ
Page 5 and 6:
Before you begin Glossary Notationa
Page 7 and 8:
Before you begin • Within source
Page 9 and 10:
Contents Part I Chapter 1 Chapter 2
Page 11 and 12:
Contents Part II Chapter 6 Chapter
Page 13 and 14:
Contents Part III Appendix A Append
Page 15 and 16:
Contents NTX DLLs..................
Page 17 and 18:
I Introducing INtime software This
Page 19 and 20:
1 Overview INtime software extends
Page 21 and 22:
Chapter 1: Overview Considerations
Page 23 and 24:
Chapter 1: Overview Developing an I
Page 25 and 26:
Chapter 1: Overview INtime software
Page 27 and 28:
Chapter 1: Overview • INtime Grap
Page 29 and 30:
Chapter 1: Overview • Remote conf
Page 31 and 32:
2 Understanding INtime software arc
Page 33 and 34:
Chapter 2: Understanding INtime sof
Page 35 and 36:
Page 37 and 38:
Page 39 and 40:
Page 41 and 42:
Page 43 and 44:
Page 45 and 46:
3 About INtime software’s RT kern
Page 47 and 48:
Chapter 3: About INtime software’
Page 49 and 50:
Page 51 and 52:
Page 53 and 54:
Page 55 and 56:
4 About RT programming This chapter
Page 57 and 58:
Chapter 4: About RT programming Pre
Page 59 and 60:
Chapter 4: About RT programming whe
Page 61 and 62:
Chapter 4: About RT programming Fig
Page 63 and 64:
Chapter 4: About RT programming Syn
Page 65 and 66:
Chapter 4: About RT programming The
Page 67 and 68:
Chapter 4: About RT programming Exc
Page 69 and 70:
Chapter 4: About RT programming Str
Page 71 and 72:
5 Designing RT applications This ch
Page 73 and 74:
Chapter 5: Designing RT application
Page 75 and 76:
Chapter 5: Designing RT application
Page 77 and 78:
II Using INtime software This part
Page 79 and 80:
6 Installation This chapter explain
Page 81 and 82:
Chapter 6: Installation 5. Select o
Page 83 and 84:
7 Configuration INtime software pro
Page 85 and 86:
Chapter 7: Configuration Tab Local
Page 87 and 88:
Chapter 7: Configuration Configurin
Page 89 and 90:
Chapter 7: Configuration Setting th
Page 91 and 92:
8 Preparing an RT node This chapter
Page 93 and 94:
Chapter 8: Preparing an RT node Bui
Page 95 and 96:
Chapter 8: Preparing an RT node 4.
Page 97 and 98:
Chapter 8: Preparing an RT node Fir
Page 99 and 100:
9 Operation This chapter describes
Page 101 and 102:
Chapter 9: Operation • INtime too
Page 103 and 104:
10 INtime application development T
Page 105 and 106:
Chapter 10: INtime application deve
Page 107 and 108:
Page 109 and 110:
Page 111 and 112: Chapter 10: INtime application deve
Page 125 and 126: III Appendices The appendices inclu
Page 127 and 128: A INtime software system calls This
Page 129 and 130: Appendix A: INtime software system
Page 157 and 158: B The iwin32 subsystem This appendi
Page 159 and 160: Appendix B: The iwin32 subsystem A
Page 161: Appendix B: The iwin32 subsystem Mu
Page 165 and 166: Appendix B: The iwin32 subsystem Us
Page 167 and 168: Appendix B: The iwin32 subsystem Pr
Page 169 and 170: C INtime directory structure This a
Page 171 and 172: D INtime software components This a
Page 173 and 174: Appendix D: INtime software compone
Page 189 and 190: E Visual Studio .NET debugging for
Page 191 and 192: Appendix E: Visual Studio .NET debu
Page 193 and 194: F Adding INtime software to an XP E
Page 195 and 196: G Troubleshooting This appendix lis
Page 197 and 198: Appendix G: Troubleshooting Table G
Page 199 and 200: Appendix G: Troubleshooting Table G
Page 201 and 202: Glossary application loader asynchr
Page 203 and 204: Glossary memory area memory pool me
Page 205 and 206: Index A B C D E F G H I J K L M N O
Page 207 and 208: A B C D E F G H I J K L M N O P Q R
Page 213 and 214:
A B C D E F G H I J K L M N O P Q R
Page 215 and 216:
Page 217 and 218:
show all

INtimeÂ® 3.1 Software - tenAsys

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

Delete template?

Save as template?