From owner-freebsd-current@FreeBSD.ORG Thu Aug 4 09:37:19 2005 Return-Path: X-Original-To: current@FreeBSD.ORG Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C779016A41F for ; Thu, 4 Aug 2005 09:37:19 +0000 (GMT) (envelope-from ache@nagual.pp.ru) Received: from nagual.pp.ru (nagual.pp.ru [194.87.13.69]) by mx1.FreeBSD.org (Postfix) with ESMTP id F368F43D49 for ; Thu, 4 Aug 2005 09:37:18 +0000 (GMT) (envelope-from ache@nagual.pp.ru) Received: from nagual.pp.ru (ache@localhost [127.0.0.1]) by nagual.pp.ru (8.13.4/8.13.4) with ESMTP id j749bBFg024710; Thu, 4 Aug 2005 13:37:11 +0400 (MSD) (envelope-from ache@nagual.pp.ru) Received: (from ache@localhost) by nagual.pp.ru (8.13.4/8.13.4/Submit) id j749bBgH024709; Thu, 4 Aug 2005 13:37:11 +0400 (MSD) (envelope-from ache) Date: Thu, 4 Aug 2005 13:37:11 +0400 From: Andrey Chernov To: Maxim Sobolev Message-ID: <20050804093710.GA24384@nagual.pp.ru> Mail-Followup-To: Andrey Chernov , Maxim Sobolev , Dan Nelson , "current@freebsd.org" 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> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050804085838.GA20122@www.portaone.com> User-Agent: Mutt/1.5.9i Cc: Dan Nelson , "current@freebsd.org" Subject: Re: Sub-optimal libc's read-ahead buffering behaviour X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Aug 2005 09:37:19 -0000 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/