From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: peterb@telerama.com (Peter Berger)
Cc: linux-kernel@vger.kernel.org
Subject: Re: Pthreads, linux, gdb, oh my! (fwd)
Date: Sat, 9 Dec 2000 00:02:18 +0000 (GMT) [thread overview]
Message-ID: <E144XT2-0004fH-00@the-village.bc.nu> (raw)
In-Reply-To: <Pine.BSI.4.02.10012081344430.26743-100000@frogger.telerama.com> from "Peter Berger" at Dec 08, 2000 02:43:30 PM
> So you're saying that you got this to work? Because I certainly couldn't
> get it working with a higher version either. I would really love a
I read straight down it anf realised you referenced obsolete versions of
tg->created and thus broadcast incorrectly
> I apologize for my ignorance -- I frankly don't know the intricicies of
> linux kernel development; all I know is I wrote what might be the simplest
> of all possible concurrency tests and it is failing. If someone could
> point me to a version or combination of linux and glibc where it doesn't
> fail, I'd be happy.
The way it works on the Linux side for threads is
Kernel provides
Shared resources
clone() - fork with sharing of files/memory etc
glibc provides
POSIX semantics
pthreads API
thread locking on top of its own spin locks and kernel locks
Alan
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-12-09 0:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-08 16:53 Peter Berger
2000-12-08 17:18 ` Alan Cox
2000-12-08 19:43 ` Peter Berger
2000-12-09 0:02 ` Alan Cox [this message]
2000-12-09 6:34 ` Kevin Buhr
2000-12-09 15:15 ` Peter Berger
[not found] <Pine.BSI.4.02.10012081708350.130-100000@frogger.telerama.c om>
2000-12-08 21:21 ` Petr Vandrovec
2000-12-08 22:15 ` Peter Berger
2000-12-08 22:31 ` David Relson
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=E144XT2-0004fH-00@the-village.bc.nu \
--to=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=peterb@telerama.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
all inboxes | Powered by JetHome®