From: bert hubert <ahu@ds9a.nl>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Kip Macy <kmacy@netapp.com>,
ognen@gene.pbi.nrc.ca, linux-kernel@vger.kernel.org
Subject: Re: threading question
Date: Thu, 14 Jun 2001 21:01:38 +0200 [thread overview]
Message-ID: <20010614210138.A15912@home.ds9a.nl> (raw)
In-Reply-To: <Pine.GSO.4.10.10106121200330.20809-100000@orbit-fe.eng.netapp.com> <E15Abr6-00057R-00@the-village.bc.nu>
In-Reply-To: <E15Abr6-00057R-00@the-village.bc.nu>; from alan@lxorguk.ukuu.org.uk on Thu, Jun 14, 2001 at 07:28:32PM +0100
On Thu, Jun 14, 2001 at 07:28:32PM +0100, Alan Cox wrote:
> There are really only two reasons for threaded programming.
>
> - Poor programmer skills/language expression of event handling
The converse is that pthreads are:
- Very easy to use from C at a reasonable runtime overhead
It is very convenient for a userspace coder to be able to just start a
function in a different thread. Now it might be so that a kernel is not
there to provide ease of use for userspace coders but it is a factor.
I see lots of people only using:
pthread_create()/pthread_join()
mutex_lock/unlock
sem_post/sem_wait
no signals
My gut feeling is that you could implement this subset in a way that is both
fast and right - although it would not be 'pthreads compliant'. Can anybody
confirm this feeling?
Regards,
bert
--
http://www.PowerDNS.com Versatile DNS Services
Trilab The Technology People
'SYN! .. SYN|ACK! .. ACK!' - the mating call of the internet
next prev parent reply other threads:[~2001-06-14 19:03 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-12 18:24 threading question ognen
2001-06-12 18:39 ` Davide Libenzi
2001-06-12 18:57 ` from dmesg: kernel BUG at inode.c:486 Olivier Sessink
2001-06-12 18:58 ` threading question Christoph Hellwig
2001-06-12 19:07 ` ognen
2001-06-12 19:15 ` Kip Macy
2001-06-12 19:29 ` Christoph Hellwig
2001-06-12 19:15 ` Christoph Hellwig
2001-06-13 12:20 ` Kurt Garloff
2001-06-13 13:35 ` J . A . Magallon
2001-06-13 14:17 ` Philips
2001-06-13 15:06 ` ognen
2001-06-12 21:44 ` Davide Libenzi
2001-06-12 21:48 ` ognen
2001-06-14 18:15 ` Alan Cox
2001-06-14 22:42 ` threading question (results after thread pooling) ognen
2001-06-14 23:00 ` Mike Castle
2001-06-12 21:58 ` threading question Albert D. Cahalan
2001-06-12 23:48 ` J . A . Magallon
2001-06-12 19:06 ` Kip Macy
2001-06-12 19:14 ` Alexander Viro
2001-06-12 19:25 ` Russell Leighton
2001-06-12 23:27 ` Mike Castle
2001-06-13 17:31 ` bert hubert
2001-06-14 6:45 ` Helge Hafting
2001-06-14 18:28 ` Alan Cox
2001-06-14 19:01 ` bert hubert [this message]
2001-06-14 19:22 ` Russell Leighton
2001-06-15 11:29 ` Anil Kumar
2001-06-14 23:05 ` J . A . Magallon
2001-06-16 14:16 ` Michael Rothwell
2001-06-16 15:19 ` Alan Cox
2001-06-16 18:33 ` Russell Leighton
2001-06-16 19:06 ` Michael Rothwell
2001-06-16 21:30 ` Coroutines [was Re: threading question] Russell Leighton
2001-06-12 22:41 ` threading question Pavel Machek
2001-06-13 19:05 Hubertus Franke
[not found] <fa.f6da6av.agod3u@ifi.uio.no>
[not found] ` <fa.e54jbkv.kg4r99@ifi.uio.no>
2001-06-16 22:22 ` Dan Maas
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=20010614210138.A15912@home.ds9a.nl \
--to=ahu@ds9a.nl \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=kmacy@netapp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ognen@gene.pbi.nrc.ca \
/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 NNTP newsgroup(s).