POSIX IO Must Die! | Linux Today

POSIX IO Must Die!

Written By
JBL
Jeffrey B. Layton
Mar 3, 2010

“POSIX IO is becoming a serious impediment to IO performance and
scaling. POSIX is one of the standards that enabled portable
programs and POSIX IO is the portion of the standard surrounding
IO. But as the world of storage evolves with greatly increasing
capacities and greatly increasing performance, it is time for POSIX
IO to evolve or die.

“POSIX (Portable Operating System Interface for Unix) is a set
of standards that define the application programming interface
(API) as well as some shell and utility interfaces. It was
developed primarily for *nix operating systems but actually any
operating system can utilize the standards. POSIX IO (not an
official name) is the portion of the standard that defines the IO
interface for POSIX compliant applications. Function such as
read(), write(), open(), close(), lseek(), fwrite(), fread(), and
so on, are defined including their errors. But these definitions
were first codified in 1988 – 22 years ago!”

Complete
Story

JBL

Jeffrey B. Layton

Linux Today Logo

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. © 2026 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.