[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220223011904.GX7074@brightrain.aerifal.cx>
Date: Tue, 22 Feb 2022 20:19:05 -0500
From: Rich Felker <dalias@...c.org>
To: Lee Shallis <gb2985@...il.com>
Cc: musl@...ts.openwall.com
Subject: Re: Suggestion for thread safety
On Mon, Feb 21, 2022 at 11:36:06AM +0000, Lee Shallis wrote:
> First I'll start with the code snippets I've copied from my own code:
> [...]
>
> Take what you will of the above, the Allot function was included just
> to give you an idea of how the locks are made, as for pauseCB that
> should be re-mapped to a variant that calls something like
> pthread_yield(), it's what I tested with, anyways the general idea is
> that the shared lock defaults to NULL when not locked, when you want
> [...]
Is there any context to this? Some problem you're setting out to solve
in relationship to musl? We already have synchronization, using
well-understood standard primitives wherever it's possible and
practical. Are you advocating for doing something different, or just
explaining something you made?
Rich
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
