“When dealing with real-time systems, the overhead of
interprocess communications (IPC) becomes important. The
formalized structures that are used in Linux for IPC can carry with
them a significant amount of overhead. This can create timing
problems for your applications. In this article, I’ll examine
two of the best IPC mechanisms available under Linux — FIFOs and
shared memory…”
“An alternative to FIFOs is shared memory, in which a portion of
physical memory is set aside for sharing between Linux and
real-time processes. In a nutshell, shared memory is a pool of
memory segments reserved at boot time. These segments may be mapped
into the address space of more than one application, allowing for
fast data sharing, data updates, and handshaking. This allows for
low-latency parallel updates.”
Web Webster has more than 20 years of writing and editorial experience in the tech sector. He’s written and edited news, demand generation, user-focused, and thought leadership content for business software solutions, consumer tech, and Linux Today, he edits and writes for a portfolio of tech industry news and analysis websites including webopedia.com, and DatabaseJournal.com.
LinuxToday is a trusted, contributor-driven news resource supporting all types of Linux users. Our thriving international community engages with us through social media and frequent content contributions aimed at solving problems ranging from personal computing to enterprise-level IT operations. LinuxToday serves as a home for a community that struggles to find comparable information elsewhere on the web.
Property of TechnologyAdvice. © 2025 TechnologyAdvice. All Rights Reserved
Advertiser Disclosure: Some of the products that appear on this site are from companies from which TechnologyAdvice receives compensation. This compensation may impact how and where products appear on this site including, for example, the order in which they appear. TechnologyAdvice does not include all companies or all types of products available in the marketplace.