9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "pedro henrique antunes de oliveira" <ph.rpguo@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] Blocking reads on single-threaded Srv-based 9p server?
Date: Fri,  6 Apr 2007 07:43:41 -0300	[thread overview]
Message-ID: <e510e47e0704060343s71ff9d18mad52e7dc8e1e8e40@mail.gmail.com> (raw)
In-Reply-To: <20070406063050.GA27497@kris.home>

[-- Attachment #1: Type: text/plain, Size: 855 bytes --]

"s there some reason that I shouldn't implement that in a single-threaded
server?"

you've asked that. i'm not an expert about concurrent programming, i've
never used threads, but here:  http://swtch.com/~rsc/thread/  (it's about
that subject)
if you read, you'll see that there that 'block' mechanisms are used to keep
the system synchronyzed, becuase using that block mechanisms keep the system
simple too.

in systens that you arent going to use concurrent programming, you can do
the synchronization in other ways, more simples, i think.

if i didnt understand the document wrong, what I've said make some sense..


i'm new to plan9 'world', and what i'm seeing is that concurrent programming
here is too much common, and you'll find a lot of specialist in the subject
here, and, probably get good help to your software. good luck.

[-- Attachment #2: Type: text/html, Size: 1019 bytes --]

  reply	other threads:[~2007-04-06 10:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-06  3:33 Colin DeVilbiss
2007-04-06  6:30 ` Kris Maglione
2007-04-06 10:43   ` pedro henrique antunes de oliveira [this message]
2007-04-06 10:45     ` pedro henrique antunes de oliveira
2007-04-06 10:58     ` erik quanstrom
2007-04-06 13:52 ` Russ Cox
2007-04-06 14:01 ` Skip Tavakkolian

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=e510e47e0704060343s71ff9d18mad52e7dc8e1e8e40@mail.gmail.com \
    --to=ph.rpguo@gmail.com \
    --cc=9fans@cse.psu.edu \
    /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).