fs/smb/server/transport_rdma.h

File Facts

System

Linux kernel

Corpus path

fs/smb/server/transport_rdma.h

Extension

.h

Size

1061 bytes

Lines

31

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

• linux/smbdirect.h

Detected Declarations

• function ksmbd_rdma_init
• function ksmbd_rdma_stop_listening
• function init_smbd_max_io_size

Annotated Snippet

static inline int ksmbd_rdma_init(void) { return 0; }
static inline void ksmbd_rdma_stop_listening(void) { }
static inline bool ksmbd_rdma_capable_netdev(struct net_device *netdev) { return false; }
static inline void init_smbd_max_io_size(unsigned int sz) { }
static inline unsigned int get_smbd_max_read_write_size(struct ksmbd_transport *kt) { return 0; }
#endif

#include <linux/smbdirect.h>

#endif /* __KSMBD_TRANSPORT_RDMA_H__ */

Annotation

• Immediate include surface: `linux/smbdirect.h`.
• Detected declarations: `function ksmbd_rdma_init`, `function ksmbd_rdma_stop_listening`, `function init_smbd_max_io_size`.
• 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.