Date: Thu, 4 Aug 2005 13:37:11 +0400 From: Andrey Chernov <ache@FreeBSD.ORG> To: Maxim Sobolev <sobomax@portaone.com> Cc: Dan Nelson <dnelson@allantgroup.com>, "current@freebsd.org" <current@FreeBSD.ORG> Subject: Re: Sub-optimal libc's read-ahead buffering behaviour Message-ID: <20050804093710.GA24384@nagual.pp.ru> In-Reply-To: <20050804085838.GA20122@www.portaone.com> References: <42F0CCD5.9090200@portaone.com> <20050803150117.GD93405@dan.emsphone.com> <42F0E9B2.9080208@portaone.com> <20050804060251.GA21228@nagual.pp.ru> <20050804060830.GB21228@nagual.pp.ru> <20050804085838.GA20122@www.portaone.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Aug 04, 2005 at 10:58:38AM +0200, Maxim Sobolev wrote: > I think that any buffering should be disabled for reading from chardev > no matter how "historic" our current behaviour is. Perhaps so. But this thing is user-controlled. He can explicetely use setvbuf to disable buffering. If he does not, he knows, that this particular chardev is buffer-friendly. Since he can't control in-buffer seeking on/off trigger, it always stays off for chardev. -- http://ache.pp.ru/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050804093710.GA24384>