Linus Torvalds writes: (Summary) When people use these things for debugging and
for identifying which device node or socket or whatever they are
tracking, we're generally talking a (small) handful of different
devices or whatever.
devices or whatever.
Tobin did the statistics, most of the %p users are in drivers, and they tend to be things like identifying *which* ACPI descriptor we're talking about, or which command/request we're tracing, or which device we're probing etc. A 32-bit hash is fine, because if we have so many different things going on at the same time that you'd have a noticeable risk of collisions, you'd not depend on debug traces etc anyway, you'd start doing fancier tracing (ie start filtering using ebpf etc).
tracing (ie start filtering using ebpf etc).
My guess would be that something like that might be nice if it would mean that we'd get hw acceleration for the hashing, and that the reversibility would be entirely secondary.
reversibility would be entirely secondary.
devices or whatever.
Tobin did the statistics, most of the %p users are in drivers, and they tend to be things like identifying *which* ACPI descriptor we're talking about, or which command/request we're tracing, or which device we're probing etc. A 32-bit hash is fine, because if we have so many different things going on at the same time that you'd have a noticeable risk of collisions, you'd not depend on debug traces etc anyway, you'd start doing fancier tracing (ie start filtering using ebpf etc).
tracing (ie start filtering using ebpf etc).
[...]
interested.My guess would be that something like that might be nice if it would mean that we'd get hw acceleration for the hashing, and that the reversibility would be entirely secondary.
reversibility would be entirely secondary.