From: "Francisco J Ballesteros" <nemo@lsub.org>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] trying to understand how fork/pipe a filtering program
Date: Mon, 4 Sep 2006 22:25:05 +0200 [thread overview]
Message-ID: <8ccc8ba40609041325p3a90cfa0nf1184af8bdce0919@mail.gmail.com> (raw)
In-Reply-To: <e0e53b081fe30e1db228d82ddebb5e06@9netics.com>
I think there is an example in section 5.4 (or 5.5?) in the draft at
http://lsub.org/who/nemo/9.intro.pdf
hth
On 9/4/06, Skip Tavakkolian <9nut@9netics.com> wrote:
just this: in your example, if parent needs to write more than some
pipe-buf-limit (i think 32k) to child and/or if child produces output
larger than this limit and blocks on the write, it would be a problem.
i attached my example of using only one pipe which requires two
rendezvous points and customization of the slave proc; this could
have a deadlock when a child requires multiple reads to cause a write.
prev parent reply other threads:[~2006-09-04 20:25 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-30 22:46 Axel Belinfante
2006-08-30 23:05 ` geoff
2006-08-31 16:26 ` "Nils O. Selåsdal"
2006-08-31 19:55 ` Axel Belinfante
2006-08-31 20:15 ` rog
2006-08-31 20:24 ` Axel Belinfante
2006-08-31 20:24 ` rog
2006-08-31 20:45 ` Axel Belinfante
2006-09-01 3:43 ` geoff
2006-09-01 10:57 ` rog
2006-09-01 14:35 ` rog
2006-09-01 15:33 ` Skip Tavakkolian
2006-09-01 15:59 ` rog
2006-09-01 18:42 ` Skip Tavakkolian
2006-09-03 19:09 ` Axel Belinfante
2006-09-04 14:52 ` Gorka guardiola
2006-09-04 20:50 ` Gorka guardiola
2006-09-04 19:26 ` Skip Tavakkolian
2006-09-04 20:25 ` Francisco J Ballesteros [this message]
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=8ccc8ba40609041325p3a90cfa0nf1184af8bdce0919@mail.gmail.com \
--to=nemo@lsub.org \
--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).