From: "Robert Kindred" <RKindred@SwRI.edu>
To: "Stephen Croall" <scroall@tibco.com>,
<pthreads-win32@sources.redhat.com>
Subject: RE: Good Algorithm for "Multiple Readers"/"Multiple Writers"
Date: Thu, 08 Dec 2005 14:46:00 -0000 [thread overview]
Message-ID: <IIEJIMCOHAKGODCMHFEOOENGCCAA.RKindred@SwRI.edu> (raw)
In-Reply-To: <D8495C6C606E0C47AF2720713E1B7A620112383A@NA-PA-VBE01.na.tibco.com>
I use the pthread_rwlock_t in pthreads-win32, and it works fine.
Robert Kindred
> -----Original Message-----
> From: pthreads-win32-owner@sourceware.org
> [mailto:pthreads-win32-owner@sourceware.org]On Behalf Of Stephen Croall
> Sent: Thursday, December 08, 2005 3:10 AM
> To: pthreads-win32@sources.redhat.com
> Subject: Good Algorithm for "Multiple Readers"/"Multiple Writers"
>
>
> Hi,
>
> I'm looking for a good, performant algorithm for "multiple
> reader"/"multiple writer" locking.
>
> I'm in the process of writing my own but I would rather not fall into
> any common pitfalls, especially since performance & scalability are
> critical.
>
> Is anyone aware of whether POSIX implements this type of lock? I can't
> seem to find any reference to it in the POSIX documentation.
>
> Cheers, Steve.
>
> --
>
> J. Senior Software Engineer, Tibco Software Ltd.
> T. +44 (0) 1792 360773
> M. +44 (0) 7788 971394
> E. scroall@tibco.com
> W. www.tibco.com
>
next prev parent reply other threads:[~2005-12-08 14:46 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-08 9:09 Stephen Croall
2005-12-08 14:46 ` Robert Kindred [this message]
2005-12-08 9:57 Stephen Croall
2005-12-08 14:02 Evstiounin, Mikhail
2005-12-08 14:09 Stephen Croall
2005-12-08 14:53 ` Robert Kindred
2005-12-08 14:49 Stephen Croall
2005-12-08 15:00 Evstiounin, Mikhail
2005-12-08 15:01 Stephen Croall
2005-12-08 15:02 Evstiounin, Mikhail
2005-12-08 15:06 Stephen Croall
2005-12-08 15:06 Evstiounin, Mikhail
2005-12-08 15:09 Stephen Croall
2005-12-08 15:11 Stephen Croall
2005-12-08 15:16 Stephen Croall
2005-12-08 15:47 Evstiounin, Mikhail
2005-12-08 16:35 Stephen Croall
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=IIEJIMCOHAKGODCMHFEOOENGCCAA.RKindred@SwRI.edu \
--to=rkindred@swri.edu \
--cc=pthreads-win32@sources.redhat.com \
--cc=scroall@tibco.com \
/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).