Return to BSD News archive
Xref: sserve comp.os.386bsd.questions:12709 comp.os.386bsd.misc:3410 Newsgroups: comp.os.386bsd.questions,comp.os.386bsd.misc Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!bunyip.cc.uq.oz.au!munnari.oz.au!news.Hawaii.Edu!ames!hookup!swrinde!howland.reston.ans.net!math.ohio-state.edu!jussieu.fr!univ-lyon1.fr!swidir.switch.ch!newsfeed.ACO.net!Austria.EU.net!EU.net!uunet!brunix!mhw From: mhw@cs.brown.edu (Mark Weaver) Subject: Re: Whats wrong with Linux networking ??? Message-ID: <1994Aug19.054837.23724@cs.brown.edu> Sender: news@cs.brown.edu Organization: Brown University Department of Computer Science References: <RSANDERS.94Aug9003813@hrothgar.mindspring.com> <32ll52$n7d@quagga.ru.ac.za> <1994Aug15.034939.20997@cs.brown.edu> <32te9lINN6ab@bonnie.sax.de> Date: Fri, 19 Aug 1994 05:48:37 GMT Lines: 26 In article <32te9lINN6ab@bonnie.sax.de>, J Wunsch <j@uriah.sax.de> wrote: >mhw@cs.brown.edu (Mark Weaver) writes: > >>disk activity. I always get significant disk activity from compiling, >>even though my /tmp is a ramdisk. > >>On Linux, while doing the same thing, there is hardly any disk >>activity at all. I always think something's wrong when compiling >>under Linux because I don't hear the characteristic disk chattering >>that I associate with compiling. > >Are you sure your temp files go via the ramdisk? I've used to compile >with ``-pipe'' set, and i notice the same effect as you with Linux >[...] Yes, I'm sure. While building something, I would repeatedly ls /tmp, and watch the tmp files being created and destroyed. I haven't tried -pipe. Perhaps that will help somewhat. However, I'm pretty sold on the unified VM/buffer cache theory. I think that's what's making the difference. Mark -------------------------------------------------------------------- Email: Mark_Weaver@brown.edu | Brown University PGP Key: finger mhw@cs.brown.edu | Dept of Computer Science