From owner-freebsd-hackers Wed Jun 27 19:46:17 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from bingnet2.cc.binghamton.edu (bingnet2.cc.binghamton.edu [128.226.1.18]) by hub.freebsd.org (Postfix) with ESMTP id 7E0F937B401 for ; Wed, 27 Jun 2001 19:46:14 -0700 (PDT) (envelope-from zzhang@cs.binghamton.edu) Received: from opal (cs.binghamton.edu [128.226.123.101]) by bingnet2.cc.binghamton.edu (8.11.4/8.11.4) with ESMTP id f5S2jMU25391; Wed, 27 Jun 2001 22:45:22 -0400 (EDT) Date: Wed, 27 Jun 2001 22:45:21 -0400 (EDT) From: Zhihui Zhang X-Sender: zzhang@opal To: Manas Bhatt Cc: hackers@FreeBSD.ORG Subject: Re: does data overflow in pipes In-Reply-To: <20010628024057.71824.qmail@web10705.mail.yahoo.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I guess the kernel will block the process trying to write more data than that can be accommodated. Or if you are using non-blocking I/O, it will return an error. -Zhihui On Wed, 27 Jun 2001, Manas Bhatt wrote: > hi all, > pipes uses only direct blocks to store data. so > depending on the blocksize , a total data of > 10*blocksize can be written in one go but what happens > if a writer process tries to write more 10*blocksize > of data in one go. Does the kernel overwrites the > data in pipe or not ? if yes, why? if not, then how > does it allow the writer to write more 10*blocksize of > data? > if someone can direct me to implementation > (source files), it would be great. > thanks > --manas > > __________________________________________________ > Do You Yahoo!? > Get personalized email addresses from Yahoo! Mail > http://personal.mail.yahoo.com/ > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message