qat_init(8)

💖 qat_init(8) 💖

okay bestie, welcome to the qat_init page from the man manual, section 8. this one's short and sweet but it does SO much, i fear. 🫶

---

✨ NAME ✨

qat_init — QAT resource initializer

like. that's her. that's the whole name. qat_init. iconic behavior honestly. 👑

---

🌸 SYNOPSIS 🌸

qat_init

no flags. no args. no drama. she just runs. 💅

---

🦋 DESCRIPTION 🦋

so qat_init goes and initializes the Intel© Quick Assist Technology (Intel© QAT) devices, getting them all cute and ready to be used by the user space library (qatlib). it's giving pre-game ritual. it's giving "getting ready for the function." ✨

when you run it on a host system where physical function (PF) QAT devices are visible and bound to the QAT device driver, the qat_init script will enable sriov on each of those PF devices. and what does that do? it enables the virtual function (VF) devices. so the PFs get the VFs online. slay. 🌈

then, for each of the QAT VF devices, qat_init binds the device to the vfio-pci device driver, which makes it available for applications using the qatlib user space library. matchmaker, matchmaker, making the VF meet its driver. 🎀

---

🧚 ENVIRONMENT VARIABLES 🧚

• LKCF_LIST — if you set this, it gives a list of VF devices that should be used for accelerating operations from the Linux crypto framework, instead of being available for user space applications. so basically: pick a lane, bestie. either the crypto framework gets them or user space does. 🙈

example, fr fr:

LKCF_LIST="0000:3d:01.0 0000:3f:01.0 0000:da:01.0"

---

👀 SEE ALSO 👀

• qatmgr(8)

go read her next, she's the manager. literally. 💜

---

💌 AUTHOR 💌

Conor McLoughlin <conor.mcloughlin@intel.com>

---

and that's the whole page!! shoutout to the qat_init man page itself — this is qat_init, dated 30 Oct 2019, straight out of the qat_init(8) manual. no cap, that's the source and the version and the date, all wrapped up with a little bow. 🎀✨ bye bestie, go enable some sriov 💖