PNFS Block Layout TODO
From Linux NFS
(Difference between revisions)
(make these two separate items) |
|||
| Line 6: | Line 6: | ||
* Fully understand and document what it does and why it needs to do it | * Fully understand and document what it does and why it needs to do it | ||
* Use existing methods (udev, libdevmapper, etc) to scan and create disks instead of inventing new methods | * Use existing methods (udev, libdevmapper, etc) to scan and create disks instead of inventing new methods | ||
| + | * read /sys/block instead of supplying a default config file | ||
* Use udev notifications to trigger device rescan, instead of rescanning once a minute | * Use udev notifications to trigger device rescan, instead of rescanning once a minute | ||
* Use a pre-existing upcall mechanism instead of inventing our own | * Use a pre-existing upcall mechanism instead of inventing our own | ||
Revision as of 18:36, 14 September 2010
This page is intended to serve as a "to-do" list for the Linux pNFS Block Layout client.
pNFS Block Layout Userspace Daemon
- Give it consistent naming (process name, executable name, pidfile name, etc)
- Fully understand and document what it does and why it needs to do it
- Use existing methods (udev, libdevmapper, etc) to scan and create disks instead of inventing new methods
- read /sys/block instead of supplying a default config file
- Use udev notifications to trigger device rescan, instead of rescanning once a minute
- Use a pre-existing upcall mechanism instead of inventing our own
- Give it meaningful debug messages
- General code cleanup
- man page and any other needed documentation
—Eanderle 18:13, 3 September 2010 (UTC)
