Storage Stack Filter for Delete Notification Modification
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current storage systems do not effectively utilize delete notifications to optimize storage operations, leading to unnecessary maintenance of deleted data and inefficient resource management within the storage stack.
Innovation Solution
Implementing filters within the storage stack to modify or create delete notifications, allowing for the exclusion of protected data and freeing up resources by contracting or expanding notification ranges, and creating new notifications to improve performance and resource allocation.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If delete notifications are sent from filesystem to storage device, then storage device can reduce internal operations on invalid data, but storage device cannot distinguish between valid and invalid data without additional processing
Solution Approach 1:
A delete notification filter is introduced as an intermediary component in the storage stack between the filesystem and storage device. The filter receives delete notifications from the filesystem, modifies them by contracting ranges to exclude protected data, and passes the modified notifications to the storage device. This intermediary resolves the contradiction by enabling efficient invalid data identification without requiring complex processing at the storage device level.
Solution Approach 2:
The delete notification range is segmented into multiple sub-ranges by the filter. When a delete notification covers a large range including both valid and invalid data, the filter divides it into smaller segments, contracting the ranges to exclude protected data portions. This segmentation allows the storage device to efficiently process only the actual invalid data ranges without unnecessary operations on protected data.
2Ease of operation
If delete notifications cover entire ranges including protected data, then filesystem can simplify deletion operations, but storage device performs unnecessary maintenance on protected data
Solution Approach 1:
The filter extracts protected data portions from delete notification ranges by contracting the ranges. When a delete notification is received, the filter identifies and removes segments corresponding to protected data, passing only the contracted ranges that actually contain invalid data to the storage device. This extraction prevents unnecessary maintenance operations on protected data while maintaining filesystem deletion simplicity.
3Reliability
If storage device maintains all data without delete notifications, then data integrity is preserved, but storage resources are wasted on deleted data
Solution Approach 1:
The filesystem provides feedback to the storage device about deleted data through delete notifications that are modified by the filter. This feedback mechanism enables the storage device to identify and stop maintaining invalid data, freeing storage resources. The feedback loop maintains data integrity for valid data while optimizing resource utilization by eliminating maintenance of deleted data.
Data Source
AI summary
A filter between a filesystem and a storage device in a storage stack can be configured to modify a delete notification, such as by modifying an existing delete notification or creating a new delete notification. A storage stack filter can receive an existing delete notification and determine a modified range of deleted data in response to receiving the existing notification, where a modified delete notification indicates the modified range of deleted data. A new delete notification can be created with a storage stack filter positioned below a filesystem in a storage stack, where the new delete notification indicates a range of deleted data. The new or modified delete notification can be passed down the storage stack.