arch/sparc/include/uapi/asm/resource.h
Source file repositories/reference/linux-study-clean/arch/sparc/include/uapi/asm/resource.h
File Facts
- System
- Linux kernel
- Corpus path
arch/sparc/include/uapi/asm/resource.h- Extension
.h- Size
- 770 bytes
- Lines
- 32
- Domain
- Architecture Layer
- Bucket
- arch/sparc
- Inferred role
- Architecture Layer: implementation source
- Status
- source implementation candidate
Why This File Exists
CPU and platform-specific kernel glue: boot entry, traps, syscall entry, interrupts, page tables, context switch, and low-level barriers.
- CPU and platform-specific kernel glue: boot entry, traps, syscall entry, interrupts, page tables, context switch, and low-level barriers.
Dependency Surface
asm-generic/resource.h
Detected Declarations
- No top-level syscall, struct, function, initcall, or export declaration detected by the generator.
Annotated Snippet
#ifndef _SPARC_RESOURCE_H
#define _SPARC_RESOURCE_H
/*
* These two resource limit IDs have a Sparc/Linux-specific ordering,
* the rest comes from the generic header:
*/
#define RLIMIT_NOFILE 6 /* max number of open files */
#define RLIMIT_NPROC 7 /* max number of processes */
#if defined(__sparc__) && defined(__arch64__)
/* Use generic version */
#else
/*
* SuS says limits have to be unsigned.
* We make this unsigned, but keep the
* old value for compatibility:
*/
#define RLIM_INFINITY 0x7fffffff
#endif
#include <asm-generic/resource.h>
#endif /* !(_SPARC_RESOURCE_H) */
Annotation
- Immediate include surface: `asm-generic/resource.h`.
- Atlas domain: Architecture Layer / arch/sparc.
- 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.