From: YAMANASHI Takeshi <uncover@beat.cc.titech.ac.jp>
To: 9fans@cse.psu.edu
Subject: [9fans] lib9p
Date: Tue, 18 Dec 2001 13:50:53 +0900 [thread overview]
Message-ID: <12636.1008651053@beat.cc.titech.ac.jp> (raw)
I'm building a file server program on lib9p.
On providing the client read function, is it OK that the parent
process forks off a child and returns imediately, while the
child calls the respond() funtion after having done blocking
read() or something? I'm concerning about the variable
'long *count' passed to srv->read() function for the sake of
returning the count of bytes.
I found srv() is calling the client read function as
srv->read(r, r->fid, r->rbuf, &r->fcall.count, r->fcall.offset);
in /sys/src/lib9p/srv.c and doesn't care '*count' at all
after that.
So I think it's OK for the present. But can I rely on it?
--
Sincerely,
YAMANASHI Takeshi
next reply other threads:[~2001-12-18 4:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-18 4:50 YAMANASHI Takeshi [this message]
2001-12-18 5:00 Russ Cox
2001-12-18 8:17 ` YAMANASHI Takeshi
2001-12-19 14:04 ` David Rubin
2001-12-20 0:22 ` YAMANASHI Takeshi
2001-12-18 16:31 Russ Cox
2001-12-19 4:46 ` YAMANASHI Takeshi
2001-12-20 1:59 okamoto
2001-12-20 2:25 ` YAMANASHI Takeshi
2001-12-20 2:31 okamoto
2001-12-21 9:58 ` David Rubin
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=12636.1008651053@beat.cc.titech.ac.jp \
--to=uncover@beat.cc.titech.ac.jp \
--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).