include/rdma/frmr_pools.h

File Facts

System

Linux kernel

Corpus path

include/rdma/frmr_pools.h

Extension

.h

Size

1130 bytes

Lines

41

Domain

Repository Root And Misc

Bucket

include

Inferred role

Repository Root And Misc: implementation source

Status

source implementation candidate

Why This File Exists

Top-level or miscellaneous repository surface. Use this as map coverage unless a later manual pass promotes the file into a deeper subsystem dossier.

• Top-level or miscellaneous repository surface. Use this as map coverage unless a later manual pass promotes the file into a deeper subsystem dossier.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/types.h
• asm/page.h

Detected Declarations

• struct ib_device
• struct ib_mr
• struct ib_frmr_key
• struct ib_frmr_pool_ops

Annotated Snippet

struct ib_frmr_key {
	u64 vendor_key;
	/* A pool with non-zero kernel_vendor_key is a kernel-only pool. */
	u64 kernel_vendor_key;
	size_t num_dma_blocks;
	int access_flags;
	u8 ats:1;
};

struct ib_frmr_pool_ops {
	int (*create_frmrs)(struct ib_device *device, struct ib_frmr_key *key,
			    u32 *handles, u32 count);
	void (*destroy_frmrs)(struct ib_device *device, u32 *handles,
			      u32 count);
	int (*build_key)(struct ib_device *device, const struct ib_frmr_key *in,
			 struct ib_frmr_key *out);
};

int ib_frmr_pools_init(struct ib_device *device,
		       const struct ib_frmr_pool_ops *pool_ops);
void ib_frmr_pools_cleanup(struct ib_device *device);
int ib_frmr_pool_pop(struct ib_device *device, struct ib_mr *mr);
void ib_frmr_pool_push(struct ib_device *device, struct ib_mr *mr);
void ib_frmr_pool_drop(struct ib_mr *mr);

#endif /* FRMR_POOLS_H */

Annotation

• Immediate include surface: `linux/types.h`, `asm/page.h`.
• Detected declarations: `struct ib_device`, `struct ib_mr`, `struct ib_frmr_key`, `struct ib_frmr_pool_ops`.
• Atlas domain: Repository Root And Misc / include.
• Implementation status: source implementation candidate.

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.