From: Ronald G Minnich <rminnich@lanl.gov>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] xcpu fix for Plan9.c
Date: Tue, 25 Oct 2005 14:56:58 -0600 [thread overview]
Message-ID: <435E9C1A.8000308@lanl.gov> (raw)
In-Reply-To: <19b649e3b3fee86d4c20cf4f7187feb7@granite.cias.osakafu-u.ac.jp>
Kenji Okamoto wrote:
> term% xcpusrv -sxcpu
> ....
> term% mount -ac /srv/xcpu /mnt/xcpu
> term% openclone /mnt/xcpu
> (then on a newly created rio window)
> term% cat /mnt/xcpu/clone
> 65537term% <=============here! not 65536!
> term% ls -l /mnt/xcpu
> --rw-rw-rw- M 66 ssh ssh 0 Jan 1 1970 /mnt/xcpu/65536 <========= not 65537!
> --rw-rw-rw- M 66 ssh ssh 0 Jan 1 1970 /mnt/xcpu/clone
weird. I will have to try this on plan 9. I think I know what I am doing
wrong but want to verify it.
>
> On the point why only once copy of execution file, I didn't noticed
> the danger of your example /bin/sh execution. Now, I think why
> you chose that way. So, in xcpu we should do only batch job, right?
no, if you look at xsh you can see it can be used for interactive jobs
(in future).
The real issues are these:
Suppose I
cp /bin/date exec
echo exec >ctl
cp /bin/uname exec
echo exec > ctl
cat stdout
OK, what does the output of stdout mean in this case? how do I
distinguish the two things in a reasonable way? If I want to control the
process, which one am I controlling? If I get an eof on the stdout file,
which one did I get an EOF for? Should stdout deliver more than one EOF
for each process that ends? The whole situation turns into a confusing
mess if you let more than one process run for each 'exec' file.
> On the xsh.c, I still have some problem.
> Isn't this a program to be used for a cluster environment?
yes, but I make no guarantees. I am still fighting what might be a p9p
issue on Linux, so xsh is not quite ready yet. I am trying to get this
thing ready for SC '05, but I am running out of time :-)
>
> In the file, there is a line of
> dirno[nodeno++] = smprint("/%s/%s/xcpu/%s", base, s, buf);
>
> here, I suppose we should name our cluster's cp server by s,
> such as
> /mnt/xcpu/"s"/xcpu/"number", right?
yes, exactly, I had no idea of how to name things, so this is what I
came up with. This is done this way to make it fit linux as well. On
linux, we will have
/mnt/xcpu/"s"/xcpu ==> xcpu server for "s"
/mnt/xcpu/"s"/fs ==> u9fs server for that node, so we can access files
on the node "s"
note that in this model, the node is the server, and it exports both the
xcpu service and its own file system.
>
> So, we have only one cpu server, then we should use the xsh command
> like
> term% xsh 0
> ?
yes.
>
> Or if we have many cpu server, then
>
> xsh 0 1 2 3 4 5 6 7
> ?
yes. so to run date on all those nodes:
xsh 0 1 2 3 4 5 6 7 -- /bin/date
>
> By the way, in your mkfile-plan9
>
> $O.xsh: xsh.$O P9pshell.$O
> $LD -o $target $prereq $LDFLAGS
>
> should be
> $O.xsh: xsh.$O Plan9shell.$O <============
> $LD -o $target $prereq $LDFLAGS
thanks for that fix, I just installed it.
thanks again
ron
next prev parent reply other threads:[~2005-10-25 20:56 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-20 2:58 YAMANASHI Takeshi
2005-10-20 14:33 ` Ronald G Minnich
2005-10-20 15:40 ` Ronald G Minnich
2005-10-20 15:56 ` Ronald G Minnich
2005-10-22 3:43 ` kokamoto
2005-10-24 14:46 ` Ronald G Minnich
2005-10-25 2:24 ` Kenji Okamoto
2005-10-25 2:29 ` Kenji Okamoto
2005-10-25 20:56 ` Ronald G Minnich [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-10-24 1:01 YAMANASHI Takeshi
2005-10-21 5:55 YAMANASHI Takeshi
2005-10-21 4:24 YAMANASHI Takeshi
2005-10-21 4:31 ` Russ Cox
2005-10-21 2:14 YAMANASHI Takeshi
2005-10-24 14:40 ` Ronald G Minnich
2005-10-24 14:57 ` Lucio De Re
2005-10-24 15:06 ` Lucio De Re
2005-10-19 13:28 Ronald G Minnich
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=435E9C1A.8000308@lanl.gov \
--to=rminnich@lanl.gov \
--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).