STRUCT DRM_ETHOSU_JOB(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ struct drm_ethosu_job(9) ✨

okay so this is a page from the Kernel API Manual (yes, the manual name is literally "Kernel API Manual", we love that for us) and it's all about struct drm_ethosu_job πŸ’…


πŸŽ€ NAME πŸŽ€

struct drm_ethosu_job β€” a job to be run on the NPU. that's it, that's the whole vibe 🧚


🌸 SYNOPSIS 🌸

bestie here's the struct, copied exactly, no cap:

struct drm_ethosu_job {
    __u32 cmd_bo;
    __u32 sram_size;
  #define ETHOSU_MAX_REGIONS      8;
    __u32 region_bo_handles[ETHOSU_MAX_REGIONS];
 };

like look at her. cmd_bo? sram_size? region_bo_handles[ETHOSU_MAX_REGIONS]? and the #define ETHOSU_MAX_REGIONS 8; is just sitting there in the middle of the struct being iconic πŸ‘‘


πŸ¦‹ Members πŸ¦‹

so the original page has a Members section and then… literally nothing under it 😭 no cap, it's empty. the fields are all up in SYNOPSIS, go look there bestie 🫢


πŸ’– Description πŸ’–

okay so the real tea: the kernel will schedule the execution of this job, and it takes into account its dependencies with other jobs πŸ”₯ (dependencies, the way that they matter).

and here's the slay part β€” all tasks in the same job will be executed sequentially on the same core, so they get to benefit from memory residency in SRAM πŸ’œ like they're all hanging out in the same spot, main character energy, no bouncing around.


🌈 SEE ALSO 🌈

go read these too, iykyk:

  • Kernel file ./include/uapi/drm/ethosu_accel.h
  • IOCTL IDs(9)
  • IOCTL arguments(9)
  • enum drm_ethosu_dev_query_type(9)
  • struct drm_ethosu_dev_query(9)
  • enum drm_ethosu_bo_flags(9)
  • struct drm_ethosu_bo_create(9)
  • struct drm_ethosu_bo_mmap_offset(9)
  • struct drm_ethosu_submit(9)
  • struct drm_ethosu_perfmon_set_global(9)
  • DRM_IOCTL_ETHOSU(9)

ngl this one's short but she ate. every field, every cross-reference, all present and accounted for ✨

and that's the whole page bestie!! πŸ’– it lives at ./include/uapi/drm and the date on it is October 2026 ⭐ (yes, 2026, we're being so future-forward, periodt) πŸŽ€πŸŒΈπŸ’…

πŸ“¦ where this page comes from