FUSE Data Consistency via Event-Triggered Invalidation

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing filesystem in userspace (FUSE) technologies face challenges in maintaining data consistency between the kernel module and the file service end, leading to potential inconsistencies and reduced system performance due to periodic synchronization issues.

Innovation Solution

A method that synchronizes data in real-time by comparing modification time information from both the kernel module and the file service end, returning an invalidation result if inconsistent, and subsequently invalidating the data in the kernel module and synchronizing updated data from the file service end.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the duration of the synchronization period is set to be short, then the data consistency between kernel module and file service end is improved, but the system performance deteriorates due to frequent synchronization operations

Engineering Contradiction:

Improvedata consistencyVSAvoidsystem performance

Core Design Contradiction:

ReliabilityVSProductivity

Solution Approach 1:

The patent implements dynamic synchronization by triggering data validation only when specific events occur (data requests, mount/unmount operations, attribute changes) rather than using fixed periodic intervals. This event-driven approach adapts the synchronization frequency to actual system needs, maintaining data consistency while avoiding unnecessary performance overhead from frequent periodic checks.

Inventive Principle:

Principle #15Dynamics

Solution Approach 2:

The kernel module autonomously determines when synchronization is needed by monitoring its own operational states and data request patterns. The system self-regulates the synchronization process based on internal events without requiring external control, enabling it to maintain consistency while optimizing performance by avoiding redundant synchronization operations.

Inventive Principle:

Principle #25Self-service

2Productivity

If the duration of the synchronization period is set to be long, then the system performance is improved, but the data consistency between kernel module and file service end deteriorates due to delayed synchronization

Engineering Contradiction:

Improvesystem performanceVSAvoiddata consistency

Core Design Contradiction:

ProductivityVSReliability

Solution Approach 1:

The patent implements a feedback mechanism where the kernel module continuously monitors data requests and operational events, and triggers synchronization based on this feedback. When specific events occur (data requests, mount/unmount operations, attribute changes), the system receives feedback that synchronization is needed, ensuring data consistency is maintained without requiring continuous periodic checks that would degrade performance.

Inventive Principle:

Principle #23Feedback

Solution Approach 2:

The system autonomously manages its own synchronization needs by monitoring its operational state and triggering validation only when necessary. This self-service approach allows the kernel module to maintain data consistency while optimizing performance by avoiding unnecessary synchronization operations that would occur with fixed periodic intervals.

Inventive Principle:

Principle #25Self-service

3Reliability

If periodic synchronization is implemented frequently, then the data validity in kernel module is improved, but the system overhead increases due to frequent synchronization operations

Engineering Contradiction:

Improvedata validityVSAvoidsystem overhead

Core Design Contradiction:

ReliabilityVSLoss of energy

Solution Approach 1:

The patent replaces static periodic synchronization with dynamic event-triggered validation. The system adapts its validation frequency to actual system events, performing data consistency checks only when necessary (on data requests, mount/unmount operations, or attribute changes). This dynamic approach maintains data validity while significantly reducing system overhead by eliminating redundant validation operations that would occur during idle periods.

Inventive Principle:

Principle #15Dynamics

Solution Approach 2:

The system maintains continuous monitoring of operational events and triggers validation continuously only when useful actions occur. Rather than continuously validating data at fixed intervals regardless of system state, the patent ensures validation is performed continuously in response to actual system events, maintaining data validity while minimizing unnecessary computational overhead during periods when no useful actions require validation.

Inventive Principle:

Principle #20Continuity of useful action

Data Source

PatentUS12222907B1Method, apparatus, device and storage medium for data processing

Publication Date: 2025.02.11 BEIJING VOLCANO ENGINE TECH CO LTD

AI summary

Embodiments of the present disclosure provide a method, apparatus, device and storage medium for data processing. If a kernel module sends a data calling request to a userspace process, first modification time information and second modification time information of data corresponding to the data calling request are obtained by the userspace process. The first and second modification time information are used to indicate modification time information of the data in the kernel module and in a file service end, respectively. The first and second modification time information are compared by the userspace process. If the first and second modification time information are inconsistent, a verification invalidation result is returned to the kernel module. The data in the kernel module is invalidated by the kernel module according to the verification invalidation result. The data in the file service is synchronized by the userspace process to the kernel module.