lib/raid/raid6/riscv/rvv.h

File Facts

System

Linux kernel

Corpus path

lib/raid/raid6/riscv/rvv.h

Extension

.h

Size

1187 bytes

Lines

39

Domain

Kernel Services

Bucket

lib

Inferred role

Kernel Services: implementation source

Status

source implementation candidate

Why This File Exists

Shared kernel service surface used by multiple subsystems, including helpers, cryptography, virtualization support, and async I/O infrastructure.

• Shared kernel service surface used by multiple subsystems, including helpers, cryptography, virtualization support, and async I/O infrastructure.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• asm/vector.h
• algos.h

Detected Declarations

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

Annotated Snippet

#include <asm/vector.h>
#include "algos.h"

#define RAID6_RVV_WRAPPER(_n)						\
	static void raid6_rvv ## _n ## _gen_syndrome(int disks,		\
					size_t bytes, void **ptrs)	\
	{								\
		void raid6_rvv ## _n  ## _gen_syndrome_real(int d,	\
					unsigned long b, void **p);	\
		kernel_vector_begin();					\
		raid6_rvv ## _n ## _gen_syndrome_real(disks,		\
				(unsigned long)bytes, ptrs);		\
		kernel_vector_end();					\
	}								\
	static void raid6_rvv ## _n ## _xor_syndrome(int disks,		\
					int start, int stop,		\
					size_t bytes, void **ptrs)	\
	{								\
		void raid6_rvv ## _n  ## _xor_syndrome_real(int d,	\
					int s1, int s2,			\
					unsigned long b, void **p);	\
		kernel_vector_begin();					\
		raid6_rvv ## _n ## _xor_syndrome_real(disks,		\
			start, stop, (unsigned long)bytes, ptrs);	\
		kernel_vector_end();					\
	}								\
	struct raid6_calls const raid6_rvvx ## _n = {			\
		.gen_syndrome	= raid6_rvv ## _n ## _gen_syndrome,	\
		.xor_syndrome	= raid6_rvv ## _n ## _xor_syndrome,	\
		.name		= "rvvx" #_n,				\
	}

Annotation

• Immediate include surface: `asm/vector.h`, `algos.h`.
• Atlas domain: Kernel Services / lib.
• 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.