From: Bill Davidsen <davidsen@tmr.com>
To: Arjan van de Ven <arjan@infradead.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [ANN] Userspace M-on-N threading model implementation. Alpha release.
Date: Sun, 04 Feb 2007 15:12:32 -0500 [thread overview]
Message-ID: <45C63E30.4010106@tmr.com> (raw)
In-Reply-To: <1170516376.3073.1015.camel@laptopd505.fenrus.org>
Arjan van de Ven wrote:
>> Because user threading can avoid context switches, there will always be
>> cases where it will outperform o/s threads for hardware reasons.
>
> actually.. switching from one "real" thread to another in Linux is not
> an actual context switch in the hardware sense... at least this part of
> your argument seems to be incorrect ;)
>
How does that work? Switching between kernel threads requires going into
the kernel, user level thread switches are all done in user mode.
Do you have some way to change o/s threads w/o going into the kernel?
--
Bill Davidsen <davidsen@tmr.com>
"We have more to fear from the bungling of the incompetent than from
the machinations of the wicked." - from Slashdot
next prev parent reply other threads:[~2007-02-04 20:12 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-30 21:16 [ANN] Userspace M-on-N threading model implementation. Alpha release Kaz Kylheku
2007-01-31 8:47 ` Evgeniy Polyakov
2007-02-02 16:12 ` Bill Davidsen
2007-02-03 15:26 ` Arjan van de Ven
2007-02-04 20:12 ` Bill Davidsen [this message]
2007-02-04 20:20 ` Jakub Jelinek
2007-02-04 21:42 ` Bill Davidsen
2007-02-05 6:14 ` Arjan van de Ven
2007-02-14 12:17 ` Pavel Machek
2007-02-04 22:52 ` Davide Libenzi
[not found] <40f323d00701290747y68c8e27ege824694bfa378f58@mail.gmail.com>
2007-01-29 14:52 ` Evgeniy Polyakov
2007-01-29 14:57 ` Evgeniy Polyakov
2007-01-29 16:40 ` Chris Friesen
2007-01-30 9:46 ` Evgeniy Polyakov
2007-01-30 1:18 ` Samuel Thibault
2007-01-30 9:53 ` Evgeniy Polyakov
2007-01-30 10:24 ` Samuel Thibault
2007-01-30 10:43 ` Evgeniy Polyakov
2007-02-01 4:28 ` Lee Revell
2007-02-01 7:09 ` Evgeniy Polyakov
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=45C63E30.4010106@tmr.com \
--to=davidsen@tmr.com \
--cc=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.