From: Vladimir Kliatchko <vladimir@kliatchko.com>
To: 'Ross Johnson' <ross.johnson@homemail.com.au>
Cc: 'Gottlob Frege' <gottlobfrege@gmail.com>,
pthreads-win32@sources.redhat.com
Subject: RE: New pthread_once implementation
Date: Sat, 28 May 2005 14:29:00 -0000 [thread overview]
Message-ID: <0IH700C30EV237@mta8.srv.hcvlny.cv.net> (raw)
In-Reply-To: <1117288359.787.143.camel@desk.home>
[-- Attachment #1: Type: text/plain, Size: 4787 bytes --]
What do you think of the attached implementation? I am still analyzing it,
but it passes the tests and appears to be free of that problem. It does have
one minor glitch though:
If two threads come in, the semaphore is created. If both are cancelled and
no new calls a made to finish the job, the semaphore is never destroyed.
I am not sure how big a deal this is.
Re. optimizations: Great, I will try to do something.
Thnx,
--vlad
> -----Original Message-----
> From: pthreads-win32-owner@sources.redhat.com [mailto:pthreads-win32-
> owner@sources.redhat.com] On Behalf Of Ross Johnson
> Sent: Saturday, May 28, 2005 9:55 AM
> To: Vladimir Kliatchko
> Cc: 'Gottlob Frege'; Pthreads-Win32 list
> Subject: RE: New pthread_once implementation
>
> On Sat, 2005-05-28 at 06:51 -0400, Vladimir Kliatchko wrote:
> >
> > > -----Original Message-----
> > > From: pthreads-win32-owner@sources.redhat.com [mailto:pthreads-win32-
> > > owner@sources.redhat.com] On Behalf Of Ross Johnson
> > > Sent: Friday, May 27, 2005 11:48 PM
> > > To: Vladimir Kliatchko
> > > Cc: 'Gottlob Frege'; Pthreads-Win32 list
> > > Subject: RE: New pthread_once implementation
> > >
> > > On Fri, 2005-05-27 at 21:30 -0400, Vladimir Kliatchko wrote:
> > > > Nice catch. Let me see if I can fix it.
> > > >
> > > > Note that the same problem exists in the currently released event-
> based
> > > > implementation (cvs version 1.16):
> > > >
> > > > thread1 comes in, start initing
> > > > thread2 creates event, starts waiting
> > > > thread3 comes in starts waiting
> > > > thread1 is cancelled, signals event
> > > > thread2 wakes up, proceeds to the point right before the resetEvent
> > > > thread3 wakes up, closes event handle
> > > > thread2 resets closed handle
> > >
> > > Relies on HANDLE uniqueness and assumes that an error will result.
> This
> > > is why the 2.6.0 version (and earlier) checks the return code and
> > > restores Win32 LastError if necessary - for GetLastError transparency.
> >
> > Does Windows guarantee that the handles are not reused? What happens if
> a
> > thread closes a handle while another thread is blocked on it? Is any of
> this
> > in Microsoft documentation? Consider the following scenario for the
> > event-based implementation:
>
> Well, apparently they're not unique when recycled, so there is a bug
> here to fix in both versions:
> http://msdn.microsoft.com/library/default.asp?url=/library/en-
> us/dngenlib/html/msdn_handles1.asp
> [Under "Native Windows NT Objects"]
> "Unlike the handles that are maintained by the Win32 USER and GDI
> subsystem components, handles to native objects under Windows NT are not
> unique; that is, upon destruction of an object, the corresponding handle
> may be recycled and will look exactly like the handle to the destroyed
> object."
>
> But they are local to the process, rather than system wide if that
> helps.
>
> > > > Also, regarding my previous comment to Ross about very high cost of
> > > using
> > > > InterlockedExchangeAdd for MBR:
> > > > I did some simple benchmarking. Running pthread_once 50,000,000 on
> my
> > > pretty
> > > > slow single CPU machine takes about 2.1 seconds. Replacing
> > > > InterlockedExchangeAdd with simple read brings it down to 0.6
> seconds.
> > > This
> > > > looks significant.
> > >
> > > Using the PTW32_INTERLOCKED_COMPARE_EXCHANGE macro as in your latest
> (in
> > > CVS) version and building the library for inlined functions (nmake VC-
> > > inlined) and x86 architecture causes customised versions of
> > > InterlockedCompareExchange to be used, and this results in inlined
> asm.
> > > Same for PTW32_INTERLOCKED_EXCHANGE.
> > >
> > > Also, on single-CPU x86, the library dynamically switches to using
> > > 'cmpxchg' rather than 'lock cmpxchg' to avoid locking the bus. This
> > > appears to match what the kernel32.dll versions do. On non-x86
> > > architectures the kernel32.dll versions are called, with call
> overhead.
> > >
> > > PTW32_INTERLOCKED_EXCHANGE_ADD could be added, as could other
> > > architectures. See ptw32_InterlockedCompareExchange.c
> >
> > I have rerun my benchmark with VC-inline. The difference is now less
> > significant 0.9 vs 0.6 but still noticeable. I guess cmpxchg even
> without
> > locking is quite expensive. On multi-CPU systems the difference should
> be
> > much higher due to the time it takes to lock the bus and to the
> contention
> > it may cause. It sounded as if you did not care much to try to optimize
> it.
> > I did not mean to suggest that we have to do it right now either. I just
> > wanted to get your opinion on whether we want to deal with this in the
> > future.
>
> By all means include any optimisation you think is worthwhile. I was
> just pointing out that the difference isn't necessarily 2.1 v 0.6.
>
[-- Attachment #2: vk_pthread_once4.c --]
[-- Type: text/plain, Size: 3358 bytes --]
#define PTHREAD_ONCE_INIT {0, 0, 0, 0}
enum ptw32_once_state {
PTW32_ONCE_INIT = 0x0,
PTW32_ONCE_STARTED = 0x1,
PTW32_ONCE_DONE = 0x2
};
struct pthread_once_t_
{
int state;
int reserved;
int numSemaphoreUsers;
HANDLE semaphore;
};
static void PTW32_CDECL
ptw32_once_on_init_cancel (void * arg)
{
pthread_once_t * once_control = (pthread_once_t *) arg;
(void) PTW32_INTERLOCKED_EXCHANGE((LPLONG)&once_control->state,
(LONG)PTW32_ONCE_INIT);
if (InterlockedExchangeAdd((LPLONG)&once_control->semaphore,
0L)) /* MBR fence */
{
ReleaseSemaphore(once_control->semaphore, 1, NULL);
}
}
static int
ptw32_once (pthread_once_t * once_control, void (*init_routine) (void))
{
int state;
HANDLE sema;
while ((state = PTW32_INTERLOCKED_COMPARE_EXCHANGE(
(PTW32_INTERLOCKED_LPLONG)&once_control->state,
(PTW32_INTERLOCKED_LONG)PTW32_ONCE_STARTED,
(PTW32_INTERLOCKED_LONG)PTW32_ONCE_INIT)) !=
PTW32_ONCE_DONE)
{
if (PTW32_ONCE_INIT == state)
{
#ifdef _MSC_VER
#pragma inline_depth(0)
#endif
pthread_cleanup_push(ptw32_once_on_init_cancel,
(void *) once_control);
(*init_routine)();
pthread_cleanup_pop(0);
#ifdef _MSC_VER
#pragma inline_depth()
#endif
(void) PTW32_INTERLOCKED_EXCHANGE((LPLONG)&once_control->state,
(LONG)PTW32_ONCE_DONE);
/*
* we didn't create the semaphore.
* it is only there if there is someone waiting.
*/
if (InterlockedExchangeAdd((LPLONG)&once_control->semaphore,
0L)) /* MBR fence */
{
ReleaseSemaphore(once_control->semaphore,
once_control->numSemaphoreUsers, NULL);
}
}
else
{
InterlockedIncrement((LPLONG)&once_control->numSemaphoreUsers);
if (!InterlockedExchangeAdd((LPLONG)&once_control->semaphore,
0L)) /* MBR fence */
{
sema = CreateSemaphore(NULL, 0, INT_MAX, NULL);
if (PTW32_INTERLOCKED_COMPARE_EXCHANGE(
(PTW32_INTERLOCKED_LPLONG)&once_control->semaphore,
(PTW32_INTERLOCKED_LONG)sema,
(PTW32_INTERLOCKED_LONG)0))
{
CloseHandle(sema);
}
}
/*
* Check 'state' again in case the initting thread has finished or
cancelled and left before seeing that there was a semaphore.
*/
if (InterlockedExchangeAdd((LPLONG)&once_control->state,
0L) == PTW32_ONCE_STARTED)
{
WaitForSingleObject(once_control->semaphore, INFINITE);
}
InterlockedDecrement((LPLONG)&once_control->numSemaphoreUsers);
}
}
if (0 == InterlockedExchangeAdd((LPLONG)&once_control->numSemaphoreUsers,
0)) /* MBR */
{
if ((sema = (HANDLE) PTW32_INTERLOCKED_EXCHANGE(
(LPLONG)&once_control->semaphore,
(LONG)0)))
{
CloseHandle(sema);
}
}
return 0;
}
int
pthread_once (pthread_once_t * once_control, void (*init_routine) (void))
{
int result;
if (once_control == NULL || init_routine == NULL)
{
result = EINVAL;
}
else
{
if (InterlockedExchangeAdd((LPLONG)&once_control->state,
0L) != PTW32_ONCE_DONE) /* MBR */
{
result = ptw32_once(once_control, init_routine);
}
else
{
result = 0;
}
}
return (result);
} /* pthread_once */
next prev parent reply other threads:[~2005-05-28 14:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <97ffb3105052709425ce1126a@mail.gmail.com>
2005-05-28 1:30 ` Vladimir Kliatchko
2005-05-28 3:46 ` Ross Johnson
2005-05-28 10:51 ` Vladimir Kliatchko
2005-05-28 13:54 ` Ross Johnson
2005-05-28 14:29 ` Vladimir Kliatchko [this message]
2005-05-29 12:58 ` Vladimir Kliatchko
2005-05-30 14:48 ` Ross Johnson
2005-05-30 15:26 ` Vladimir Kliatchko
2005-05-31 16:28 ` Gottlob Frege
2005-06-01 3:02 ` Ross Johnson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0IH700C30EV237@mta8.srv.hcvlny.cv.net \
--to=vladimir@kliatchko.com \
--cc=gottlobfrege@gmail.com \
--cc=pthreads-win32@sources.redhat.com \
--cc=ross.johnson@homemail.com.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).