From: tomas@fabula.de (Tomas Zerolo)
Cc: guile-user@gnu.org
Subject: Threads (was: mod_lisp for guile)
Date: Tue, 20 Sep 2005 06:44:55 +0200 [thread overview]
Message-ID: <20050920044455.GA27881@www.trapp.net> (raw)
In-Reply-To: <432F80F2.4080605@mail.msen.com>
[-- Attachment #1.1: Type: text/plain, Size: 1253 bytes --]
On Mon, Sep 19, 2005 at 11:24:34PM -0400, Alan Grover wrote:
> Neil Jerram wrote:
> (much elision)
[...]
> > How would using threads reduce resource usage? Otherwise this all
> > makes sense.
AFAIU inter-thread communication is just easier. And forking a thread
might be easier on VM than forking a process. On some bad process
implementations much more so.
> A thread doesn't require an entire process (like a fork does), in
> particular, memory is shared. I think you could limit a thread's
> resource requirements to just an execution "thread" (PC, registers,
> stack), otherwise sharing everything within the one process. Being
> light-weight/cheap is one of the major motivations for threads.
>
> Though I read something recently that claimed some thread
> (mis-)implementations are more costly than a fork, and often more costly
> than you'd hope. Apparently, the Linux 2.6 thread implementation is in
> user-space, which means it isn't very thrifty (and causes some other
> interesting issues).
On Linux 2.6 and with glibc 2.0 you have native Posix threads, and a
quite spiffy implementation at that. See e.g.
<http://kerneltrap.org/node/422>
Newer Guiles try to take advantage of that.
Regards
-- tomas
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
[-- Attachment #2: Type: text/plain, Size: 140 bytes --]
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-user
next prev parent reply other threads:[~2005-09-20 4:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-15 17:25 mod_lisp for guile Alan Grover
2005-09-16 18:46 ` Neil Jerram
2005-09-19 14:46 ` Alan Grover
2005-09-19 21:32 ` Neil Jerram
2005-09-20 3:24 ` Alan Grover
2005-09-20 4:44 ` Tomas Zerolo [this message]
2005-09-20 12:12 ` Threads Alan Grover
2005-12-04 10:07 ` mod_lisp for guile Neil Jerram
2005-12-05 17:21 ` Alan Grover
2005-12-15 23:21 ` Neil Jerram
2005-12-16 13:21 ` Alan Grover
2005-12-29 10:18 ` Neil Jerram
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050920044455.GA27881@www.trapp.net \
--to=tomas@fabula.de \
--cc=guile-user@gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).