3.2 Rtlinux Inter-Process Communication (Ipc)

RTLINUX OVERVIEW---Detail of the bare Linux kernel
Detail of the RTLinux kernel
3.2 RTLinux Inter-Process Communication (IPC)

The general philosophy of RTLinux requires the realtime component of an application to be lightweight, small and simple. Applications should be split in such a way that, as long as timing restrictions are met, most of the work
is done in user space. This approach makes for easier debugging and better understanding of the realtime part of the system. Consequently, communication mechanisms are necessary to interface RTLinux tasks and Linux. RTLinux provides several mechanisms which allow communication between realtime threads and user space Linux processes. The most important are realtime FIFOs and shared memory.
3.2.1 Using Real-Time FIFOs

Realtime FIFOs are First-In-First-Out queues that can be read from and written to by Linux processes and RTLinux threads. FIFOs are uni-directional you can use a pair of FIFOs for bi-directional data exchange. To use the FIFOs, the system/rtl posixio.o and fifos/rtl fifo.o Linux modules must be loaded in the kernel. RT-FIFOs are Linux character devices with the major number of 150. Device entries in /dev are created during system installation. The device file names are /dev/rtf0, /dev/rtf1, etc., through /dev/rtf63 (the maximum number of RT-FIFOs in the system is configurable during system compilation). Before a realtime FIFO can be used, it must be initialized: #include <rtl_fifo.h> int rtf_create(unsigned int fifo, int size); int rtf_destroy(unsigned int fifo); rtf create allocates the buffer of the specified size for the fifo buffer. The fifo argument corresponds to the minor number of the device. rtf destroy deallocates the FIFO. These functions must only be called from the Linux kernel thread (i.e., from init module()). 3.2. RTLINUX IPC 23 After the FIFO is created, the following calls can be used to access it from RTLinux threads: open(2) , read(2) , write(2) and close(2) . Support for other STDIO functions is planned for future releases. Current implementation requires the FIFOs to be opened in non-blocking mode (O NONBLOCK) by RTL threads. You can also use the RTLinux-specific functions rtf put (3) and rtf get (3) . Linux processes can use UNIX file IO functions without restriction. See the examples/measurement/rt process.c example program for a practical application of RT-FIFOs.
3.2.2 Using Shared Memory

For shared memory, you can use the excellent mbuff driver by Tomasz Motylewski (motyl@chemie.unibas.ch. It is included with the RTLinux distribution and is installed in the drivers/mbuff directory. A manual is included with the package. Here, well just briefly describe the basic mode of operation. First, the mbuff.o module must be loaded in the kernel. Two functions are used to allocate blocks of shared memory, connect to them and eventually deallocate them.
#include <mbuff.h> void * mbuff_alloc(const char *name, int size); void mbuff_free(const char *name, void * mbuf); The first time mbuff alloc is called with a given name, a shared memory block of the specified size is allocated. The reference count for this block is set to 1. On success, the pointer to the newly allocated block is returned. NULL is returned on failure. If the block with the specified name already exists, this function returns a pointer that can be used to access this block and increases the reference count. .4. INTERRUPTS 27 Functions with the p suffix (e.g., outb p) provide a small delay after reading or writing to the port. This delay is needed for some slow ISA devices on fast machines. (See also the Linux I/O port programming mini-HOWTO). Check out examples/sound to see how some of these functions are used to program the PC realtime clock and the speaker.
3.4 Soft and Hard Interrupts

There are two types of interrupts in RTLinux: hard and soft. Soft interrupts are normal Linux kernel interrupts. They have the advantage that some Linux kernel functions can be called from them safely. However, for many tasks they do not provide hard realtime performance; they may be delayed for considerable periods of time. Hard interrupts (or realtime interrupts), on the other hand, have much lower latency. However, just as with realtime threads, only a very limited set of kernel functions may be called from the hard interrupt handlers.
3.4.1 Hard Interrupts

The two functions: rtl request irq(3) and rtl free irq(3) are used for installing and uninstalling hard interrupt handlers for specific interrupts. The manual pages describe their operation in detail. #include <rtl_core.h> int rtl_request_irq(unsigned int irq, unsigned int (*handler) (unsigned int, struct pt_regs *)); int rtl_free_irq(unsigned int irq); 28 CHAPTER 3. THE ADVANCED API
3.4.2 Soft interrupts

int rtl_get_soft_irq( void (*handler)(int, void *, struct pt_regs *), const char * devname); void rtl_global_pend_irq(int ix);
void rtl_free_soft_irq(unsigned int irq); The rtl get soft irq(3) function allocates a virtual irq number and installs the handler function for it. This virtual interrupt can later be triggered using rtl global pend irq(3) . rtl global pend irq is safe to use from realtime threads and realtime interrupts. rtl free soft frees the allocated virtual interrupt.
Mass Storage - hardware This is about Disk Behavior and Management. Disk Characteristics Space Management RAID Disk Attachment IO Interface how the OS interfaces to the hardware The busses in the computer and how the O.S. interfaces to it. Talking to the IO Polling, Interrupts and DMA Application IO Interface Kernel IO Subsystem
Mass-Storage Structure
A disk can be viewed as an array of blocks. In fact, a file system will want to view it at that logical level. However, there's a mapping scheme from logical block address B, to physical address (represented by a track / sector pair.) The smallest storage allocation is a block - nothing smaller can be placed on the disk. This results in unused space (internal fragmentation) on the disk, since quite often the
data being placed on the disk doesn't need a whole block
The components making up disk service time include: time = setup + seek + rotation time + transfer + wrap-up The methods discussed below try to optimize seek time but make no attempt to account for the total time. The ideal method would optimize the total time and many controllers are now able to accomplish this. Disk formatting Creates a logical disk from the raw disk. Includes setting aside chunks of the disk for booting, bad blocks, etc. Also provides information needed by the driver to understand its positioning. Boot block That location on the disk that is accessed when trying to boot
the operating system. It's a well-known location that contains the code that understands how to get at the operating system - generally this code has a rudimentary knowledge of the file system. Bad blocks The driver knows how to compensate for a bad block on the disk. It does this by putting a pointer, at the location of the bad block, indicating where a good copy of the data can be found. Swap Space Management The Operating System requires a contiguous space where it knows that disk blocks have been reserved for paging. This space is needed because a program can't be given unshared memory unless there's a backing store location for that memory
Network-attached storage
Network-attached storage (NAS) is storage made available over a network rather than over a local connection (such as a bus) NFS and CIFS are common protocols Implemented via remote procedure calls (RPCs) between host and storage New iSCSI protocol uses IP network to carry the SCSI protocol

3.2 Rtlinux Inter-Process Communication (Ipc)

Uploaded by

Copyright:

Available Formats

3.2 Rtlinux Inter-Process Communication (Ipc)

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

3.2 Rtlinux Inter-Process Communication (Ipc)

Uploaded by

Copyright:

Available Formats

RTLINUX OVERVIEW---Detail of the bare Linux kernel

Detail of the RTLinux kernel

3.2 RTLinux Inter-Process Communication (IPC)

3.2.1 Using Real-Time FIFOs

3.2.2 Using Shared Memory

3.4 Soft and Hard Interrupts

3.4.1 Hard Interrupts

3.4.2 Soft interrupts

data being placed on the disk doesn't need a whole block

You might also like

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.