From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] dial and time out
Date: Thu, 10 Sep 2009 05:59:43 -0400 [thread overview]
Message-ID: <06439554cf2ab2600ed70356dbf35eb2@quanstro.net> (raw)
In-Reply-To: <e5760b1ec598d2f3d6bec4bf4a892778@smgl.fr.eu.org>
> it seemed safer at first if I didn't have to worry about the procs
> preempting each other (and appart from that dial() bottleneck, I don't
> need them to), that's why I started with threads. I was thinking of
> sticking to threads and not using procs until I really do need them. But
> yeah, no real good reason not to switch to procs if that's the best way
> to go in that case.
one can use ioproc(2). though i tend to go for procs.
this is because i have a hard time understanding why
csp (and thus safety) wouldn't generally be used instead.
and when csp techniques aren't going to cut it, i find
it easier to understand a small amount of explicit locking,
because the interesting bits of contention are well-marked.
- erik
next prev parent reply other threads:[~2009-09-10 9:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-10 9:32 Mathieu L.
2009-09-10 9:34 ` erik quanstrom
2009-09-10 9:51 ` Mathieu L.
2009-09-10 9:59 ` erik quanstrom [this message]
2009-09-10 10:07 ` Sape Mullender
2009-09-10 9:57 ` Sape Mullender
2009-09-10 11:26 ` Mathieu L.
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=06439554cf2ab2600ed70356dbf35eb2@quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.net \
/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).