Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!cwjcc!hal!ncoast!allbery From: allbery@ncoast.UUCP (Brandon S. Allbery) Newsgroups: comp.unix.wizards Subject: Re: Is Unix stdio slow? Message-ID: <12837@ncoast.UUCP> Date: 17 Oct 88 21:34:05 GMT References: <411@marob.MASA.COM> <178@arnold.UUCP> <3442@crash.cts.com> <26315@ucbvax.BERKELEY.EDU> <104@minya.UUCP> Reply-To: allbery@ncoast.UUCP (Brandon S. Allbery) Followup-To: comp.unix.wizards Organization: Cleveland Public Access UN*X, Cleveland, Oh Lines: 29 As quoted from <104@minya.UUCP> by jc@minya.UUCP (John Chambers): +--------------- | > I will go as far as to say that standard output to pipes should be | > line buffered, since we no longer put pipes in files. | | BTW, on every Unix system I've ever used, a pipe is a file. What could | the stuff after the comma in the above quote possibly mean? Is there a | new implementation of pipes that doesn't use file descriptors? I sure | hope not; that sure would be a giant step backwards. +--------------- He means that on V7-based systems (including SVR3), pipes are essentially implemented in the kernel in a way that's almost identical to: p[1] = creat(some_temp_file, 0); p[1] = open(some_temp_file, 0); unlink(some_temp_file); whereas under BSD pipes are linked socketpairs and under SVR4 they're supposed to be a variant of the "clone" device (essentially, the STREAMS version of sockets) and are implemented quite differently. ++Brandon -- Brandon S. Allbery, comp.sources.misc moderator and one admin of ncoast PA UN*X uunet!hal.cwru.edu!ncoast!allbery ncoast!allbery@hal.cwru.edu allbery@skybridge.sdi.cwru.edu allbery@uunet.uu.net comp.sources.misc is moving off ncoast -- please do NOT send submissions direct (But the aliases are NOT on UUNET yet, use the aliases at backbone sites!)