SYSTEM Cited by 1 source
Pure Storage DirectFlash Module (DFM)¶
Definition¶
DirectFlash Module (DFM) is Pure Storage's custom QLC flash module paired with its DirectFlash software — a userspace Flash Translation Layer (FTL). Instead of shipping a black-box NVMe SSD with a firmware-embedded FTL, Pure Storage exposes the raw NAND to a host-side software FTL that performs wear levelling, garbage collection, and address translation in userspace.
Meta's 2025-03-04 QLC post discloses co-design with Pure Storage: DFMs are used alongside standard NVMe QLC SSDs from other NAND vendors in Meta's data centers.
Architectural shape¶
┌──────────────────────────────────────────┐
│ Meta storage application │
├──────────────────────────────────────────┤
│ Block device (regular semantics) │
├──────────────────────────────────────────┤
│ ublk (Linux userspace block driver) │
├──────────────────────────────────────────┤
│ io_uring ring buffer │
├──────────────────────────────────────────┤
│ DirectFlash software (userspace FTL) │
├──────────────────────────────────────────┤
│ DirectFlash Module (NAND) │
└──────────────────────────────────────────┘
- ublk presents the storage to applications as a regular block device (no vendor-specific library dependency at the app layer).
- io_uring is the zero-copy, ring-buffer kernel I/O path that makes the userspace-FTL design performant.
- DirectFlash software — the host-side FTL — performs all flash management logic (mapping, GC, wear levelling) in userspace rather than on an on-drive controller.
Properties claimed¶
- Scales to 600 TB per drive — larger than the 512 TB Meta can reach with standard NVMe QLC in U.2-15mm.
- Fits the U.2 slot — Meta's server designed for DFMs also accepts standard U.2 drives, preserving vendor-diversity flexibility.
- Reliable QLC — Pure Storage's software FTL is positioned as the durability and reliability story Meta needs to deploy QLC in production.
Why userspace FTL¶
Classic SSD FTLs live in on-drive firmware, opaque to the host. Moving the FTL to userspace trades drive-vendor simplicity for:
- Host visibility into NAND state — wear, GC pressure, bad-block map.
- Host-driven GC timing — schedule GC around latency-sensitive read windows.
- Mapping-table cache control — host DRAM hosts the mapping table (no DRAM-in-drive needed).
- Faster iteration — software FTL ships in days; firmware FTL ships in months.
Trade: the stack is more complex, the vendor owns more of the host runtime, and cross-vendor swaps are harder.
Co-design posture¶
DFM + DirectFlash is the flash-media-tier instance of Meta-style co-design — Meta already has Microsoft (SAI / OAM / Mount Diablo), NVIDIA + AMD (GPU platforms), and now Pure Storage (flash media). The co-design lineage extends laterally across hardware subsystems.
Seen in¶
- sources/2025-03-04-meta-a-case-for-qlc-ssds-in-the-data-center — canonical Meta disclosure. Meta "started working closely with Pure Storage, utilizing their DirectFlash Module (DFM) and DirectFlash software solution to bring reliable QLC storage to Meta."
Related¶
- systems/qlc-flash — the underlying media tier.
- systems/u2-15mm-form-factor — the physical slot DFMs share with standard U.2 drives.
- patterns/userspace-ftl-via-io-uring — the software-stack pattern DFM instantiates.
- patterns/rate-controller-for-asymmetric-media — necessary co-primitive given QLC's R/W asymmetry.
- patterns/co-design-with-ocp-partners — the broader Meta partnership posture.
- companies/meta.