Xref: utzoo comp.protocols.tcp-ip:8008 comp.protocols.nfs:325
Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.milw.wisc.edu!cs.utexas.edu!sun-barr!newstop!east!hinode!geoff
From: geoff@hinode.East.Sun.COM (Geoff Arnold @ Sun BOS - R.H. coast near the top)
Newsgroups: comp.protocols.tcp-ip,comp.protocols.nfs
Subject: Re: How to get an urgent message to an arbitrary system
Keywords: rwall
Message-ID: <693@east.East.Sun.COM>
Date: 11 Aug 89 15:41:06 GMT
References: <681@east.East.Sun.COM> <1989Aug10.170537.1823@maccs.dcss.mcmaster.ca>
Sender: news@east.East.Sun.COM
Reply-To: geoff@hinode.East.Sun.COM (Geoff Arnold @ Sun BOS - R.H. coast near the top)
Followup-To: comp.protocols.tcp-ip
Organization: Sun Microsystems, Billerica MA
Lines: 23

In article <1989Aug10.170537.1823@maccs.dcss.mcmaster.ca> beame@maccs.dcss.mcmaster.ca (Carl Beame) writes:
>Since we implemented a rwalld in our BWNFS (PC based NFS client), I checked
>to see how much memory it takes. Not counting the initialization code, (which
>is not resident in memory), it takes 192 (decimal) bytes. 

I presume you're not including the portmapper in this total? We don't
run a portmapper in PC-NFS, since we don't normally run any RPC based servers
on the PC. (After all, we don't want to undercut our workstation
business :^) "rwall" uses a pmap_rmtcall to contact rpc.rwalld, but
to be correct you have to handle both direct and indirect calls, don't
you?

Also, are you doing the any duplicate filtering?

>But I guess if you write in C it takes a lot more :-)

I'm sure you know that none of the resident PC-NFS code is written in C...


Geoff Arnold,                              Internet: geoff@East.Sun.COM
PCDS Group, Sun Microsystems Inc.
---------------------------------------------------------------------------
Just think: If Unix had been developed in England, we'd all be using BCPL...