Documentation/ABI/testing/sysfs-driver-xen-blkfront

Source file repositories/reference/linux-study-clean/Documentation/ABI/testing/sysfs-driver-xen-blkfront

File Facts

System: Linux kernel
Corpus path: Documentation/ABI/testing/sysfs-driver-xen-blkfront
Extension: [no extension]
Size: 942 bytes
Lines: 20
Domain: Support Tooling And Documentation
Bucket: Documentation
Inferred role: Support Tooling And Documentation: Documentation
Status: atlas-only

Why This File Exists

Repository support layer: documentation, build tooling, samples, user-space helper tools, generated initramfs support, licenses, and validation utilities.

Repository support layer: documentation, build tooling, samples, user-space helper tools, generated initramfs support, licenses, and validation utilities.

Dependency Surface

No C-style include directives detected by the generator.

Detected Declarations

No top-level syscall, struct, function, initcall, or export declaration detected by the generator.

Annotated Snippet

What:           /sys/module/xen_blkfront/parameters/max_indirect_segments
Date:           June 2013
KernelVersion:  3.11
Contact:        Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Description:
                Maximum number of segments that the frontend will negotiate
                with the backend for indirect descriptors. The default value
                is 32 - higher value means more potential throughput but more
                memory usage. The backend picks the minimum of the frontend
                and its default backend value.

What:           /sys/module/xen_blkfront/parameters/feature_persistent
Date:           September 2020
KernelVersion:  5.10
Contact:        Maximilian Heyne <mheyne@amazon.de>
Description:
                Whether to enable the persistent grants feature or not.  Note
                that this option only takes effect on newly connected frontends.
                The default is Y (enable).

Annotation

Atlas domain: Support Tooling And Documentation / Documentation.
Implementation status: atlas-only.

Implementation Notes

This generated page is the file-by-file coverage layer; curated subsystem chapters should link here when they synthesize a multi-file control flow.
Core OS pages should be promoted from atlas-only to deep-reviewed when they explain data structures, invariants, locking, lifecycle, and C implementation snippets.
Driver-family pages are intentionally pattern-oriented unless they are part of the selected PCIe/NVMe representative device path.