Opened 18 years ago
Closed 16 years ago
#1052 closed enhancement (fixed)
Disk Device Manager -- Implement the Notification Mechanism
Reported by: | bonefish | Owned by: | bonefish |
---|---|---|---|
Priority: | normal | Milestone: | R1 |
Component: | System/Kernel | Version: | R1/pre-alpha1 |
Keywords: | Cc: | ||
Blocked By: | Blocking: | #2629 | |
Platform: | All |
Description
The disk device manager needs to notify userland application of two kinds of events: Changes to disk devices and partitions (added/removed devices, moved/resized/added/delete/initialized/otherwise changed partitions), and progress of disk device jobs. This notification mechanism should also be made available within the kernel.
The following tasks have to be performed:
- Implement the core of the notification mechanism in src/system/kernel/disk_device_manager.
- Implement the required syscalls to provide access to the notification mechanism for the userland API.
- Implement the respective parts of the userland API (BDiskDeviceRoster::StartWatching() and related methods).
- Provide access to the notification mechanism interface from the kernel. Both asynchronous and synchronous notifications should be supported. In case of disk device jobs it should be possible to synchronously wait for the termination of a disk device job (with/without timeout).
Change History (4)
comment:1 by , 17 years ago
Milestone: | R1 → R1/alpha |
---|
comment:2 by , 16 years ago
Blocking: | 2629 added |
---|
comment:3 by , 16 years ago
Milestone: | R1/alpha1 → R1 |
---|
comment:4 by , 16 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
More or less implemented since hrev29582.
Note:
See TracTickets
for help on using tickets.
(In #2629) This is also not very surprising, though (#1052).