Mailing-List: contact cygwin-developers-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT cygwin DOT com Delivered-To: mailing list cygwin-developers AT cygwin DOT com Date: Mon, 26 Aug 2002 16:29:21 +0200 From: Corinna Vinschen To: cygwin-developers AT cygwin DOT com Subject: Re: readv/writev Message-ID: <20020826162921.M5475@cygbert.vinschen.de> Reply-To: cygwin-developers AT cygwin DOT com Mail-Followup-To: cygwin-developers AT cygwin DOT com References: <00c501c2496e$39ae2720$6132bc3e AT BABEL> <1029976536 DOT 27825 DOT 46 DOT camel AT lifelesswks> <025401c24a0d$1c996380$6132bc3e AT BABEL> <1030060087 DOT 8462 DOT 14 DOT camel AT lifelesswks> <20020824191035 DOT GB27153 AT redhat DOT com> <018201c24d0b$aa2d26e0$6132bc3e AT BABEL> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <018201c24d0b$aa2d26e0$6132bc3e@BABEL> User-Agent: Mutt/1.3.22.1i On Mon, Aug 26, 2002 at 03:20:00PM +0100, Conrad Scott wrote: > "Christopher Faylor" wrote: > > There shouldn't really be that much overhead to the current > method for > > handling text/binary reads, though. It's just checking a bit > field. > > At the coal-face it ends up being a bit more messy than that. For > example, the fhandler::read code checks the readahead buffers for > pending data but they will always be empty in binary-mode (AFAIK) > . In fact there's a page of code before the check for whether a > binary read is being done and only then does the code escape back > to the caller. Since (AFAIK) you can't change the text/binary > mode of an fd once it's been opened (and thus the readahead You can. setmode(fd, O_TEXT); or setmode(fd, O_BINARY); Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Developer mailto:cygwin AT cygwin DOT com Red Hat, Inc.