fs/xfs/xfs_buf_mem.h

File Facts

System

Linux kernel

Corpus path

fs/xfs/xfs_buf_mem.h

Extension

.h

Size

932 bytes

Lines

33

Domain

Core OS

Bucket

VFS And Filesystem Core

Inferred role

Core OS: implementation source

Status

source implementation candidate

Why This File Exists

Core operating-system implementation surface: boot, tasks, memory, VFS, syscall-facing interfaces, synchronization, credentials, and isolation.

• Core operating-system implementation surface: boot, tasks, memory, VFS, syscall-facing interfaces, synchronization, credentials, and isolation.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• No C-style include directives detected by the generator.

Detected Declarations

• function Copyright

Annotated Snippet

// SPDX-License-Identifier: GPL-2.0-or-later
/*
 * Copyright (c) 2023-2024 Oracle.  All Rights Reserved.
 * Author: Darrick J. Wong <djwong@kernel.org>
 */
#ifndef __XFS_BUF_MEM_H__
#define __XFS_BUF_MEM_H__

#define XMBUF_BLOCKSIZE			(PAGE_SIZE)
#define XMBUF_BLOCKSHIFT		(PAGE_SHIFT)

#ifdef CONFIG_XFS_MEMORY_BUFS
static inline bool xfs_buftarg_is_mem(const struct xfs_buftarg *btp)
{
	return btp->bt_bdev == NULL;
}

int xmbuf_alloc(struct xfs_mount *mp, const char *descr,
		struct xfs_buftarg **btpp);
void xmbuf_free(struct xfs_buftarg *btp);

bool xmbuf_verify_daddr(struct xfs_buftarg *btp, xfs_daddr_t daddr);
void xmbuf_trans_bdetach(struct xfs_trans *tp, struct xfs_buf *bp);
int xmbuf_finalize(struct xfs_buf *bp);
#else
# define xfs_buftarg_is_mem(...)	(false)
# define xmbuf_verify_daddr(...)	(false)
#endif /* CONFIG_XFS_MEMORY_BUFS */

int xmbuf_map_backing_mem(struct xfs_buf *bp);

#endif /* __XFS_BUF_MEM_H__ */

Annotation

• Detected declarations: `function Copyright`.
• Atlas domain: Core OS / VFS And Filesystem Core.
• 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.