Date: Sat, 13 Feb 1999 14:33:51 +0000 From: Tony Finch <dot@dotat.at> To: hackers@FreeBSD.ORG Subject: Re: PIPE_BUF Message-ID: <E10Bg8l-0007WQ-00@fanf.noc.demon.net> In-Reply-To: <199902102342.PAA01160@dingo.cdrom.com> References: <E10Ae9I-0004x0-00@fanf.noc.demon.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Mike Smith <mike@smith.net.au> wrote: >> I've been looking at the Apache code for doing buffered writes to >> logs, which it attempts to do in such a way that log records are not >> split across buffer boundaries. It therefore buffers up to PIPE_BUF >> bytes to be written in one go. > >If it's actually writing into a pipe, it should write as much as >possible at once under FreeBSD to get best performance. How likely am I to fall foul of concurrency issues when doing that? The reason Apache does what it does is to avoid writes from different httpds to the same pipe getting confused with each other. Why should a large PIPE_BUF have a bad effect on interactive pipes? Is it simply because of the way stdio buffers writes? Tony. -- f.a.n.finch dot@dotat.at fanf@demon.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E10Bg8l-0007WQ-00>