include/linux/if_eql.h
Source file repositories/reference/linux-study-clean/include/linux/if_eql.h
File Facts
- System
- Linux kernel
- Corpus path
include/linux/if_eql.h- Extension
.h- Size
- 1162 bytes
- Lines
- 52
- Domain
- Core OS
- Bucket
- Core Kernel Interface
- 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/timer.hlinux/spinlock.hnet/net_trackers.huapi/linux/if_eql.h
Detected Declarations
- No top-level syscall, struct, function, initcall, or export declaration detected by the generator.
Annotated Snippet
#ifndef _LINUX_IF_EQL_H
#define _LINUX_IF_EQL_H
#include <linux/timer.h>
#include <linux/spinlock.h>
#include <net/net_trackers.h>
#include <uapi/linux/if_eql.h>
typedef struct slave {
struct list_head list;
struct net_device *dev;
netdevice_tracker dev_tracker;
long priority;
long priority_bps;
long priority_Bps;
long bytes_queued;
} slave_t;
typedef struct slave_queue {
spinlock_t lock;
struct list_head all_slaves;
int num_slaves;
struct net_device *master_dev;
} slave_queue_t;
typedef struct equalizer {
slave_queue_t queue;
int min_slaves;
int max_slaves;
struct timer_list timer;
} equalizer_t;
#endif /* _LINUX_EQL_H */
Annotation
- Immediate include surface: `linux/timer.h`, `linux/spinlock.h`, `net/net_trackers.h`, `uapi/linux/if_eql.h`.
- Atlas domain: Core OS / Core Kernel Interface.
- 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.