User Space File System Messaging Module Bypasses Kernel SCI
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing file system approaches in computing systems are not optimized to handle current demand trends, particularly in data centers, as they rely on kernel-based interactions which are inflexible, limited by system calls, and inefficient due to multiple buffer copies and context switches, restricting data size and semantic information handling.
Innovation Solution
Implementing a file system in user space with a messaging module that bypasses the System Call Interface (SCI) of the kernel, using a library with system-call emulations and shared memory to enable customizable and efficient interactions between applications and the file system, allowing for increased data sizes and semantic information handling.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the file system resides within the kernel close to underlying hardware, then data storage and retrieval operations can be performed through system calls, but the interaction becomes inflexible and limited by system call constraints
Solution Approach 1:
The patent extracts the file system from the kernel space and places it in user space, allowing the file system to operate as an independent process. This extraction enables the file system to receive requests through a messaging module without being constrained by kernel system call interfaces, thereby improving flexibility while maintaining reliability through process-based isolation and fault containment.
2Adaptability or versatility
If the file system is placed in user space with messaging module bypassing kernel SCI, then data handling capacity and flexibility increase, but the system must manage communication without kernel infrastructure
Solution Approach 1:
The patent introduces a messaging module as an intermediary between the application and the user-space file system. This messaging module handles communication, data transfer, and coordination tasks, abstracting the complexity of user-space file system operations from the application. The messaging module acts as a mediator that manages the interaction protocol, reducing the apparent complexity while enabling enhanced flexibility and data handling capacity.
3Ease of operation
If traditional kernel-based file system interactions are used, then system calls provide a standardized interface, but multiple buffer copies and context switches reduce efficiency
Solution Approach 1:
The patent employs copying mechanisms to transfer data between the application and the user-space file system through shared memory segments. Instead of multiple buffer copies and context switches required by traditional system calls, the messaging module uses efficient copying techniques that reduce data duplication overhead. Shared memory segments allow direct memory access, minimizing the number of copy operations while maintaining interface standardization.
4Quantity of substance
If the file system operates in user space with shared memory, then data handling capacity increases, but memory management complexity increases
Solution Approach 1:
The messaging module serves multiple functions including request routing, data transfer, error handling, and coordination between the application and file system. By consolidating these functions into a single multi-functional module, the patent manages memory and data handling complexity centrally, enabling increased data handling capacity through shared memory without proportionally increasing overall system complexity.
Data Source
AI summary
Systems and methods are disclosed for interacting with a file system. The file system is operable to reside in user space of a computing system. A module, also within user space, may provide a messaging service supporting requests from an application to the file system. By bypassing a System-Call Interface (SCI) of the computing system's kernel space, the module may support requests from the application to the file system with enhanced efficiency and/or customizable features not provided by the SCI. In some examples, the module may include a library in an independent layer within user space and below the application, allowing the library to provide an application-independent messaging service for different applications. Furthermore, in some examples, the module may include a segment of memory, within user space, shared between the application and the file system for passing data involved in requests and/or responses to and/or from the file system.