Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.csd.uwm.edu!cs.utexas.edu!uunet!mcsun!hp4nl!nikhefh!n62
From: n62@nikhefh.nikhef.nl (Klamer Schutte)
Newsgroups: comp.os.minix
Subject: Re: Pipes in the Minix filesystem
Message-ID: <252@nikhefh.nikhef.nl>
Date: 5 Sep 89 15:23:32 GMT
References: <15116@ea.ecn.purdue.edu>
Reply-To: Schutte@nikhefh.nikhef.nl (Klamer Schutte)
Organization: Nikhef-H, Amsterdam (the Netherlands).
Lines: 20

In article <15116@ea.ecn.purdue.edu> housel@en.ecn.purdue.edu (Peter S. Housel) writes:
 >> a discussion about where to put the pipe'd data <<
>Another would be to make sure that pipe-related blocks never get flushed
>to disk but stay in the buffer cache. This sounds dangerous and difficult
>to implement.
 don't do. This puts a constrain on the maximum data size of a pipe. And what to do
 when one more block is needed in the cache and the rest are pipes? Abort job with
 Broken Pipe signal?
>
>Any comments?
>
Why not configuring at compile-time at which device the pipes should go?
( at my system this should be RAM; but this also puts a constraint on the maximum
  pipe size (512k on my system)).
>-Peter S. Housel-	housel@ecn.purdue.edu		...!pur-ee!housel

Klamer.
-- 
____________________Yes, mail address changed again :-(_________________________
Klamer Schutte        mcvax!nikhefh!{n62,Schutte}        {Schutte,n62}@nikhef.nl