Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!cs.utexas.edu!sun-barr!newstop!west!texsun!digi!cfoughty From: cfoughty@digi.lonestar.org (Cy Foughty) Newsgroups: comp.unix.internals Subject: Re: Regular pipe vs. Named Pipe Message-ID: <1991Jun10.143256.29982@digi.lonestar.org> Date: 10 Jun 91 14:32:56 GMT References: <1991Jun7.195953.27744@digi.lonestar.org> Organization: DSC Communications, Plano Tx. Lines: 47 In article zfgo01@hgo7.hou.amoco.com (F. G. Oakes) writes: >cfoughty@digi.lonestar.org (Cy Foughty) writes: > > >> What are the differences between a regular pipe and a >> named pipe? > >> Which type of pipe is faster and by how much? > >> Which is faster, a named pipe or a message queue? > >> Does a named pipe always go to disk or only when the allocated >> memory is exhausted? > >> Finally, please send me any additional comments, hints, or >> suggestions concerning Interprocess Communications. I been >> using ALL the different IPC mechanisms for years but there >> are a few lingering questions. > >I don't mean to offend, but I think some of this would be obvious if you RTM. > >As to which is faster--depends on your CPU, the version of UNIX you're using, >etc. > >There are a number of good references on the design, structure, and internals >of the UNIX operating system that describe this very well. I'd recommend them >as supplemental reading--not light, but enlightening. > >As far as IPC, I've found the docmentation, included with the operating >system (SVR5.3.X and SVR4.0) to adequate for me. >-- >============================================================================ >zfgo01@hgo7.hou.amoco.com (Glen Oakes) Unfortunately Unix manuals are a joke at best. Not everything works as advertised. Hardly any books/manuals include live working examples. I also don't need "adequate" documentation, I need answers quick. I've a lot of work to perform. -- Cy Foughty DSC Communications, Inc. 1000 Coit Rd., Plano,TX 75075 Work:214.519.4237 La Casa:214.578.8837 Don't compromise your compromises.