From: Daniel Jacobowitz <drow@mvista.com>
To: David Taylor <taylor@candd.org>
Cc: Kevin Buettner <kevinb@redhat.com>, gdb-patches@sources.redhat.com
Subject: Re: [PATCH RFA/RFC] Don't use lwp_from_thread() in thread_db_wait()
Date: Wed, 13 Mar 2002 09:55:00 -0000 [thread overview]
Message-ID: <20020313124632.A14198@nevyn.them.org> (raw)
In-Reply-To: <200203131737.MAA11028@houston.candd.org>
On Wed, Mar 13, 2002 at 12:37:08PM -0500, David Taylor wrote:
> > Date: Tue, 12 Mar 2002 11:23:31 -0500
> > From: Daniel Jacobowitz <drow@mvista.com>
>
> > Yes, that could probably be arranged. Someday we should talk to a
> > vendor of an M:N threads package and see what we have to work with. I
> > don't know of any offhand besides NGPT.
>
> If I understand you correctly, then: Solaris.
Is it really?
To clarify, LinuxThreads has one thread per process; IBM's NGPT has
multiple threads per process, but still multiple processes. I was
under the impression that Solaris LWPs would have all threads in one
process.
(except of course the terminology gets fuzzy here. One "process" in
Solaris includes multiple LWPs which can be executing at the same time.
If my understanding above is correct it might be more appropriate to
call Solaris one-thread-per-LWP).
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2002-03-13 17:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-11 15:46 Kevin Buettner
2002-03-11 18:47 ` Daniel Jacobowitz
2002-03-11 19:16 ` Kevin Buettner
2002-03-11 19:23 ` Daniel Jacobowitz
2002-03-11 23:52 ` Kevin Buettner
2002-03-12 8:23 ` Daniel Jacobowitz
2002-03-13 9:37 ` David Taylor
2002-03-13 9:55 ` Daniel Jacobowitz [this message]
2002-03-13 10:18 ` Andrew Cagney
2002-03-13 10:38 ` David Taylor
2002-04-02 13:19 ` Daniel Jacobowitz
2002-05-02 14:07 ` Michael Snyder
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=20020313124632.A14198@nevyn.them.org \
--to=drow@mvista.com \
--cc=gdb-patches@sources.redhat.com \
--cc=kevinb@redhat.com \
--cc=taylor@candd.org \
/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