[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"doc-seo-656280-105":3,"detail-sidebar-cat-0-en-105":80,"doc-detail-656280-en":130},{"code":4,"msg":5,"data":6},0,"ok",{"site_id":7,"language":8,"slug":9,"title":10,"keywords":11,"description":12,"schema_data":13,"social_meta":73,"head_meta":75,"extra_data":77,"updated_unix":79},105,"en","linux-storage-stack-diagram-linux-kernel-69","Linux Storage Stack Diagram - Linux Kernel 6.9","","Linux Storage Stack Diagram (Linux Kernel 6.9) visualizes how Linux handles block I/O from request generation through block layer, queuing, and I/O scheduling, down to underlying transports and device drivers. It covers stackable and block-based filesystems, network and Fibre Channel/ISCSI paths, page cache and memory mapping, and BIO structures including operation flags and target devices. The diagram also highlights storage technologies like NVMe (PCI/Fabric), MTD/UBI/flash, dm/md RAID, and example system call entry points.",{"@graph":14,"@context":72},[15,34,55],{"@type":16,"itemListElement":17},"BreadcrumbList",[18,23,27,31],{"item":19,"name":20,"@type":21,"position":22},"https://docshare.wps.com","Home","ListItem",1,{"item":24,"name":25,"@type":21,"position":26},"https://docshare.wps.com/document/","Document",2,{"item":28,"name":29,"@type":21,"position":30},"https://docshare.wps.com/document/technology/","Technology",3,{"item":32,"name":10,"@type":21,"position":33},"https://docshare.wps.com/document/linux-storage-stack-diagram-linux-kernel-69/656280/",4,{"url":32,"name":10,"@type":35,"image":36,"author":41,"headline":10,"publisher":44,"fileFormat":47,"inLanguage":8,"description":12,"dateModified":48,"datePublished":49,"encodingFormat":47,"isAccessibleForFree":50,"interactionStatistic":51},"DigitalDocument",{"url":37,"@type":38,"width":39,"height":40},"https://docshare.wps.com/thumbnails/linux-storage-stack-diagram-linux-kernel-69/656280.png","ImageObject",300,407,{"name":42,"@type":43},"putri.kecil17","Person",{"url":19,"name":45,"@type":46},"DocShare","Organization","application/pdf","2026-10-31","2026-10-25",true,{"@type":52,"interactionType":53,"userInteractionCount":33},"InteractionCounter",{"@type":54},"ViewAction",{"@type":56,"mainEntity":57},"FAQPage",[58,64,68],{"name":59,"@type":60,"acceptedAnswer":61},"What layers does the Linux storage stack diagram cover for Linux Kernel 6.9?","Question",{"text":62,"@type":63},"It outlines the stack from block layer and I/O scheduling through request-based drivers, VFS and filesystem layers, and down to NVMe/flash and other transport and device layers.","Answer",{"name":65,"@type":60,"acceptedAnswer":66},"How does the diagram represent block I/O requests?",{"text":67,"@type":63},"It includes BIOs (block I/Os) with fields such as operation and flags, target device, and bvec lists/iterators, and it shows read/write-style interfaces as entry points.",{"name":69,"@type":60,"acceptedAnswer":70},"Which networking storage paths are shown in the diagram?",{"text":71,"@type":63},"It includes Network FS along with Fibre Channel over Ethernet, iSCSI, Fibre Channel, and SCSI RDMA, reflecting multiple networked storage transports.","https://schema.org",{"og:url":32,"og:type":74,"og:title":10,"og:site_name":45,"og:description":12},"article",{"robots":76,"canonical":32},"index,follow",{"doc_id":78,"site_id":7},656280,1792967380,{"code":4,"msg":81,"data":82},"success",[83,87,91,95,100,104,109,114,119,122,126],{"id":22,"doc_module":4,"doc_module_name":25,"category_name":84,"show_sort_weight":85,"slug":86},"Story & Novel",90,"story-novel",{"id":26,"doc_module":4,"doc_module_name":25,"category_name":88,"show_sort_weight":89,"slug":90},"Literature",80,"literature",{"id":33,"doc_module":4,"doc_module_name":25,"category_name":92,"show_sort_weight":93,"slug":94},"Exam",70,"exam",{"id":96,"doc_module":4,"doc_module_name":25,"category_name":97,"show_sort_weight":98,"slug":99},5,"Comic",60,"comic",{"id":101,"doc_module":4,"doc_module_name":25,"category_name":29,"show_sort_weight":102,"slug":103},6,50,"technology",{"id":105,"doc_module":4,"doc_module_name":25,"category_name":106,"show_sort_weight":107,"slug":108},7,"Healthcare",40,"healthcare",{"id":110,"doc_module":4,"doc_module_name":25,"category_name":111,"show_sort_weight":112,"slug":113},8,"Research & Report",30,"research-report",{"id":115,"doc_module":4,"doc_module_name":25,"category_name":116,"show_sort_weight":117,"slug":118},9,"Religion & Spirituality",20,"religion-spirituality",{"id":117,"doc_module":4,"doc_module_name":25,"category_name":120,"show_sort_weight":117,"slug":121},"World Cup","world-cup",{"id":123,"doc_module":4,"doc_module_name":25,"category_name":124,"show_sort_weight":123,"slug":125},10,"Lifestyle","lifestyle",{"id":127,"doc_module":4,"doc_module_name":25,"category_name":128,"show_sort_weight":96,"slug":129},19,"General","general",{"code":4,"msg":81,"data":131},{"doc_id":78,"user_id":132,"nickname":42,"user_avatar":133,"doc_module":4,"category_id":101,"category_name":29,"doc_title":10,"doc_description":12,"doc_content":134,"file_id":135,"file_url":136,"file_type":137,"file_size":138,"view_count":33,"is_deleted":4,"is_public":22,"is_downloadable":22,"audit_status":22,"page_count":22,"language":139,"language_code":8,"site_id":7,"html_lang":8,"table_of_contents":140,"faqs":141,"seo_title":142,"seo_description":12,"update_tm":79,"read_time":30},962094509873,"https://ap-avatar.wpscdn.com/davatar_3d24733baf745e90a7e4bdd5f77d97b2","The Linux Storage Stack Diagram (Linux Kernel 6.9)  \nstackable  \nBlock Layer  \nblk_mq  \nI/O scheduler  \n|  ext4   btrfs   xfs   f2fs   gfs2  ocfs2 ntfs3  |  |  |  | VFS\u003Cbr> smbfs  ceph   nfs   coda \u003Cbr>\u003Cbr>...\u003Cbr>| \u003Cbr>\u003Cbr>\u003Cbr>\u003Cbr>Raw flash  ubifs jffs2  |  |\n| --- | --- | --- | --- | --- | --- | --- |\n| |  | |  |  |  |  |\n| \u003Cbr>erofs | \u003Cbr>squashfs |  | \u003Cbr>... |  |  |  |\n| |  |  |  |  |  |  |\n\nRequest based drivers  \nmemory  \nnetwork  \ninfiband/RoCE/iWarp  \nfibre Channel HBA driver  \nSCSI low level drivers  \n tcm_loop   aacraid  vmware_pvscsi   \nmpt3_sas  \nmpi3mr  \nhyperv_storage  \niscsi_tcp  \nstruct bio  \n-operation & flags  \n-target device  \n-bvec list  \n-bvec_iter  \n(sector, size, index)  \nBIOs (block I/Os)  \n|  | \u003Cbr>Network FS |  |\n| --- | --- | --- |\n|  | |  |\n\nBlock-based FS  \nbcachefs iso9660  \nStackable FS  \necryptfs overlayfs  \nfscache  \nPage cache  \nmalloc  \nmmap (anonym.  pages)  \nApplications (processes)  \nFibre Channel over Ethernet  \nISCSI  \nFibre Channel  \nFireWire  \nUSB  \nVirtua l Host  \npmem  \n/dev/pmem  \nSCS I RDMA  \n(version 6.9 2024-05-12, outlines the Linux storage stack as of Linux Kernel version 6.9)  \nnetwork  \ntarget_core_iblock  \n(optional) Devices on top of \"normal\" block devices  \ndevice mapper (dm)  \nmd (RAID) bcache  \nNVMe transport drivers  \nnvme (pci)  \nnvme-fc  \nnvme-rdma  \nNVMe Layer  \n\n| ata_piix |  |\n| --- | --- |\n| | |\n\nread (2)  \nwrite (2)  \nopen (2)  \nstat (2)  \nchmod (2)  \n... (2)  \nbrd  \nn64cart  \n/dev/rd*  \n/dev/nullb*  \nnvme-loop  \nubi  \n/dev/mtdblock*ro  \nMTD  \n(Memory Technology Device)  \nmtip32xx  \n/dev/mmcblk*p*  \ndasd  \n/dev/dasd*  \nvirtio_blk  \n/dev/vd*  \nnbd  \n/dev/nbd*  \n/dev/rbd*  \nzram  \n/dev/zram*  \nUBI  \nMTD  \nSCSI mid Layer SCSI upper level drivers  \n/dev/ublkb*  \nublkb  \nThe Linux Storage Stack Diagram  \n[https://www.thomas-krenn.com/en/wiki/Linux_Storage_Stack_Diagram](https://www.thomas-krenn.com/en/wiki/Linux_Storage_Stack_Diagram)[ ](https://www.thomas-krenn.com/en/wiki/Linux_Storage_Stack_Diagram)Design Werner Fischer, support by Christoph Hellwig, Richard Weinberger et al.  \nLicense: CC-BY-SA 3 .0, see [http://creativecommons.org/l](http://creativecommons.org/l)icenses/by-sa/4 .0/","cbCaibkF8VQKwVXS","https://ap.wps.com/l/cbCaibkF8VQKwVXS","pdf",171657,"English","# Stack overview\n## Block layer and I/O scheduling\n## File systems and caching\n## Request-based drivers and transports\n## Device layers and transports\n## Kernel interfaces and example syscalls","[{\"question\":\"What layers does the Linux storage stack diagram cover for Linux Kernel 6.9?\",\"answer\":\"It outlines the stack from block layer and I/O scheduling through request-based drivers, VFS and filesystem layers, and down to NVMe/flash and other transport and device layers.\"},{\"question\":\"How does the diagram represent block I/O requests?\",\"answer\":\"It includes BIOs (block I/Os) with fields such as operation and flags, target device, and bvec lists/iterators, and it shows read/write-style interfaces as entry points.\"},{\"question\":\"Which networking storage paths are shown in the diagram?\",\"answer\":\"It includes Network FS along with Fibre Channel over Ethernet, iSCSI, Fibre Channel, and SCSI RDMA, reflecting multiple networked storage transports.\"}]","Linux Storage Stack Diagram - Linux Kernel 6.9 | PDF"]