9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Akshat Kumar <akumar@mail.nanosouffle.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Distributed Pipelines
Date: Mon, 26 Apr 2010 14:57:42 -0700	[thread overview]
Message-ID: <p2nfe41879c1004261457td104b7bds737d0041249cfa78@mail.gmail.com> (raw)
In-Reply-To: <7763d735e69d8028c5acb643c6b90b13@coraid.com>

Hi Erik,

Thanks for figuring that bit out!
Indeed, it seems TCP is the
problem, and IL seems to work
fine for me for the moment:

echo '1 2 3' | rx il!$cpu!17009 awk -f $home/comp.awk | gview

works perfectly!

I'll try to dig deeper into the TCP case.


Best,
ak


On 4/26/10, erik quanstrom <quanstro@labs.coraid.com> wrote:
>>
>> "...
>>           eqn paper | rx kremvax troff -ms | rx deepthought lp
>>                Parallel processing: do each stage of a pipeline on a
>>                different machine.
>> "
>>
>> however, it seems not to work this way.
>> My basic test has been something like:
>>
>> echo '1 2 3' | rx $cpu awk -f $home/comp.awk | gview
>
> cool that you tracked this down.
>
> this just doesn't work.  the problem seems to be that tcp
> is eating the eof.  awk doesn't know to exit.
>
> if you are using il, this does work.
>
> 	; echo 1 2 3| 8.rx bureau sed s/1/x/ | sed s/2/y/
> 	x y 3
>
> but if you are using tcp, it hangs.  sed never sees the
> eof and doesn't generate output (because it's buffered).
>
> the answer isn't obvious to me with tcp as i don't
> know of a way to half-close a tcp connection —
> from userspace anyway.
>
> - erik
>
>



  reply	other threads:[~2010-04-26 21:57 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-25 23:56 Akshat Kumar
2010-04-26  0:40 ` Steve Simon
2010-04-26  0:50   ` Akshat Kumar
2010-04-26  5:45     ` Eric Van Hensbergen
2010-04-26  7:33       ` Akshat Kumar
2010-04-26  7:55         ` Eric Van Hensbergen
2010-04-26 20:00           ` Akshat Kumar
2010-04-26 21:20             ` erik quanstrom
2010-04-26 21:57               ` Akshat Kumar [this message]
2010-04-26 22:17                 ` erik quanstrom
2010-04-27  8:48                   ` Derek Fawcus
2010-04-27  4:29             ` Tim Newsham
2010-04-27  4:31               ` lucio
2010-04-27 12:04                 ` erik quanstrom
2010-04-27 12:46               ` erik quanstrom
2010-05-01 18:51                 ` Ryousei Takano
2010-05-01 19:40                   ` David du Colombier
2010-05-03  3:19                     ` Ryousei Takano
2010-05-03 18:10                       ` David du Colombier
2010-05-03 20:22                         ` Russ Cox
2010-05-04 15:46                           ` Jorden M
2010-05-04 17:44                             ` ron minnich
2010-05-04 18:16                               ` erik quanstrom
2010-05-04 18:36                                 ` ron minnich
2010-05-04 18:50                                   ` erik quanstrom
2010-05-04 19:51                                   ` Russ Cox
2010-05-04 19:59                                     ` erik quanstrom

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=p2nfe41879c1004261457td104b7bds737d0041249cfa78@mail.gmail.com \
    --to=akumar@mail.nanosouffle.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).