Look free ID genertion (was: Is there a more efficient threading lock?)

[Weatherby,Gerard]

So I guess we know what would have happened.

Get Outlook for iOS<https://aka.ms/o0ukef>
________________________________
From: Python-list <python-list-bounces+gweatherby=uchc.edu at python.org> on behalf of Chris Angelico <rosuav at gmail.com>
Sent: Wednesday, March 1, 2023 8:45:50 PM
To: python-list at python.org <python-list at python.org>
Subject: Re: Look free ID genertion (was: Is there a more efficient threading lock?)

*** Attention: This is an external email. Use caution responding, opening attachments or clicking on links. ***

On Thu, 2 Mar 2023 at 08:01, <2QdxY4RzWzUUiLuE at potatochowder.com> wrote:
>
> On 2023-03-01 at 14:35:35 -0500,
> avi.e.gross at gmail.com wrote:
>
> > What would have happened if all processors had been required to have
> > some low level instruction that effectively did something in an atomic
> > way that allowed a way for anyone using any language running on that
> > machine a way to do a simple thing like set a lock or check it?
>
> Have happened?  I don't know about "required," but processors have
> indeed had such instructions for decades; e.g., the MC68000 from the
> early to mid 1980s (and used in the original Apple Macintosh, but I
> digress) has/had a Test and Set instruction.

As have all CPUs since; it's the only way to implement locks (push the
locking all the way down to the CPU level).

ChrisA
--
https://urldefense.com/v3/__https://mail.python.org/mailman/listinfo/python-list__;!!Cn_UX_p3!g70S067RzF2oPCFUYpFFzUvPHRfS0AHIGEvVyww1Tlj7BCCrsU3DWIqCE9UBO_ex0ZVanquFLHGe1d2b$