DTRACE_CALLOUT_EXECUTE(4)
πΈ NAME πΈ
Okay so bestie, welcome to dtrace_callout_execute(4) β from the Kernel Interfaces Manual, no less β aka dtrace_callout_execute, a DTrace provider for the callout API. β¨
β¨ SYNOPSIS β¨
callout_execute:kernel::callout_start
callout_execute:kernel::callout_end
π DESCRIPTION π
The callout_execute provider lets you trace the callout(9) mechanism. Slay. π
The callout_execute:kernel::callout_start probe fires just before a callout. π
The callout_execute:kernel::callout_end probe fires right after a callout. π¬
The only argument to the callout_execute probes, args[0], is a callout handler struct callout * of the invoked callout. That's the whole vibe check: one argument, one struct callout *, zero cap. π«Ά
π EXAMPLES π
π¦ Example 1: Graph of Callout Execution Time π¦
The following d(7) script generates a distribution graph of callout(9) execution times:
callout_execute:::callout_start
{
self->cstart = timestamp;
}
callout_execute:::callout_end
{
@length = quantize(timestamp - self->cstart);
}
π₯ SEE ALSO π₯
π AUTHORS π
The callout_execute provider was written by Robert N. M. Watson <rwatson@FreeBSD.org>. π
This manual page was written by Mateusz Piotrowski <0mp@FreeBSD.org>. π«Ά
mwah π this page is from Debian, dated November 4, 2025, and the manual tag is DTRACE_CALLOUT_EXECUTE(4). Bye bestie! π
π¦ where this page comes from
- freebsd 14.5: base 14.5
- freebsd 15.1: base 15.1
- π the page's license: BSD-2-Clause
- Copyright (c) 2025 Mateusz Piotrowski <0mp@FreeBSD.org>
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms