|| ||Mathieu Desnoyers <email@example.com> |
|| ||Ingo Molnar <firstname.lastname@example.org>, email@example.com |
|| ||[patch 00/12] Immediate Values |
|| ||Thu, 24 Sep 2009 09:26:26 -0400|
|| ||Article, Thread
Here is an updated version of the immediate values, applying to current tip.
[impact: data-cache optimization]
The main benefit of this infrastructure is to encode read-often variables into
the instruction stream. It can benefit to tracepoints by replacing the memory
load by an immediate value instruction. There is still room for improvement
through: an effort to provide static jump patching is ongoing, involving the
kernel and gcc communities.
Even then, the immediate values have their niche: when a value (rather than a
branch selection) is read often on fast-paths, the immediate value
infrastructure can encode these in the instruction stream without any d-cache
Two sample users are provided: prof_on from the scheduler code and tracepoints.
Feel free to merge/drop any of these.
OpenPGP key fingerprint: 8CD5 52C3 8E3C 4140 715F BA06 3F25 A8FE 3BAE 9A68
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to firstname.lastname@example.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/