WARNING: This is the _old_ Lustre wiki, and it is in the process of being retired. The information found here is all likely to be out of date. Please search the new wiki for more up to date information.
Architecture - DMU OSD: Difference between revisions
From Obsolete Lustre Wiki
Jump to navigationJump to search
No edit summary |
|||
| (3 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
'''''Note:''''' ''The content on this page reflects the state of design of a Lustre feature at a particular point in time and may contain outdated information.'' | |||
== Summary == | == Summary == | ||
| Line 42: | Line 44: | ||
== References == | == References == | ||
[[Architecture - MDS-on-DMU]] | [[Architecture - MDS-on-DMU|MDS-on-DMU]] | ||
[[Architecture - OSS-on-DMU]] | [[Architecture - OSS-on-DMU|OSS-on-DMU]] | ||
Latest revision as of 13:02, 22 January 2010
Note: The content on this page reflects the state of design of a Lustre feature at a particular point in time and may contain outdated information.
Summary
DMU OSD is a implementation of OSD API for DMU.
Definitions
DMU is a core of ZFS.
Use Cases
| ID | Quality Attribute | Summary |
|---|---|---|
| mount | usability | |
| umount | usability | |
| fid mapping | usability | how we map fids to local object id (dnode) |
| async IO | performance | use async IO where possible for better performance |
| swapping | performance | protect cache from swapping (actual for userspace DMU) |
Quality Attribute Scenarios
Implementation Details
here we enlist how DMU API matches OSD API
