STRUCT UACCE_DEVICE(9)
π struct uacce_device(9) β kernel API manual, bestie edition π
okay so bestie, we're in the struct uacce_device(9) page, from the Kernel API Manual β yes, that one, the header already told you, but I'm saying it again because context is everything β¨
πΈ NAME πΈ
struct uacce_device β literally the struct, that's it, that's the name. no description in the original, so no cap, we're not inventing one π
β¨ SYNOPSIS β¨
here's the whole thing, every field, character for character, do not touch it:
struct uacce_device {
const char *algs;
const char *api_ver;
const struct uacce_ops *ops;
unsigned long qf_pg_num[UACCE_MAX_REGION];
struct device *parent;
bool is_vf;
u32 flags;
u32 dev_id;
struct cdev *cdev;
struct device dev;
struct mutex mutex;
void *priv;
struct list_head queues;
};
π«Ά Members π«Ά
every single member, no skipping, we don't do that here π
algsβ supported algorithms. the whole point, honestly πapi_verβ api version. gotta know which era of the API you're living in π¦opsβ pointer to thestruct uacce_ops. the function table, the main character energy π₯qf_pg_numβ page numbers of the queue file regions. it's an array,[UACCE_MAX_REGION]sized, don't forget πΈparentβ pointer to the parent device. every device has a parent, deep πis_vfβ whether virtual function.bool, so yes or no, that's the vibe check πflagsβ uacce attributes.u32, bitflags-ish, you know the drill βdev_idβ id of the uacce device.u32, the whole identity πcdevβ cdev of the uacce. char device representation, iconic πdevβ dev of the uacce. the actualstruct devicesitting right there inside π§mutexβ protects uacce operation. yes, it protects the operation, so respect the lock, no sketchy unlocked nonsense πprivβ private pointer of the uacce.void *, driver's little secret π€«queuesβ list of queues.struct list_head, it's giving linked list π
π SEE ALSO π
- Kernel file
./include/linux/uacce.h struct uacce_qfile_region(9)struct uacce_ops(9)struct uacce_interface(9)struct uacce_queue(9)
go read those next, iykyk π
quick vibe check bestie: this page lives at ./include/linux, and the manual date on it is October 2026 β yes, October 2026, that's what it says, not my problem π
so that's the whole page! source path ./include/linux, October 2026 date, and the manual is struct uacce_device(9) β slay, you read the whole thing, ate and left no crumbs πβ¨π«Ά
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms