In situations where reentrancy is not necessary, maintaining code and
data in separate adjacent areas each on cache boundaries and sizes a
multiple of cache line length, these instructions may be very useful.
And perhaps there are enough critical kernel code paths protected by
locks for which the above code/data organization provides sufficient
performance to justify the effort of implementing the instructions.
On 2022-04-14 4:02 p.m., Tony Harminc wrote:
On Thu, 14 Apr 2022 at 12:29, Ngan, Robert (DXC Luxoft)
<[email protected]> wrote:
STRL/STGRLl?
Is the GCC compiler generating non-reentrant code?
I've wondered why these relatively (heh...) recent instructions exist
in the architecture at all. (There is also STHRL.)
Certainly they appeared long after it became the norm both to separate
code and data for cache reasons, and more generally to not have
non-reenterable code. (I know, C uses different terminology from
everyone else - I guess I could say "constant" areas.)
Maybe Dan Greiner knows why.
Tony H.
Gary Weinhold
Senior Application Architect
DATAKINETICS | Data Performance & Optimization
Phone:+1.613.523.5500 x216
Email: [email protected]
Visit us online at www.DKL.com
E-mail Notification: The information contained in this email and any
attachments is confidential and may be subject to copyright or other
intellectual property protection. If you are not the intended recipient, you
are not authorized to use or disclose this information, and we request that you
notify us by reply mail or telephone and delete the original message from your
mail system.
