From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20212 invoked by alias); 26 Sep 2006 22:26:05 -0000 Received: (qmail 20203 invoked by uid 22791); 26 Sep 2006 22:26:04 -0000 X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (66.187.233.31) by sourceware.org (qpsmtpd/0.31) with ESMTP; Tue, 26 Sep 2006 22:26:02 +0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.12.11.20060308/8.12.11) with ESMTP id k8QMPxrs009088; Tue, 26 Sep 2006 18:25:59 -0400 Received: from pobox.corp.redhat.com (pobox.corp.redhat.com [10.11.255.20]) by int-mx1.corp.redhat.com (8.12.11.20060308/8.12.11) with ESMTP id k8QMPxai011708; Tue, 26 Sep 2006 18:25:59 -0400 Received: from opsy.redhat.com (IDENT:SNld+E/3QTFFPmUQR+PGXwgpeowOIv94@tooth.toronto.redhat.com [172.16.14.29]) by pobox.corp.redhat.com (8.13.1/8.12.8) with ESMTP id k8QMPwHS012734; Tue, 26 Sep 2006 18:25:59 -0400 Received: by opsy.redhat.com (Postfix, from userid 500) id 4E3D237A5BF; Tue, 26 Sep 2006 16:19:16 -0600 (MDT) To: Casey Marshall Cc: mauve-discuss@sourceware.org Subject: Re: multidirectbufferIO and multibufferIO References: <451822FB.8080109@gnu.org> From: Tom Tromey Reply-To: tromey@redhat.com X-Attribution: Tom Date: Tue, 26 Sep 2006 22:26:00 -0000 In-Reply-To: <451822FB.8080109@gnu.org> Message-ID: User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-IsSubscribed: yes Mailing-List: contact mauve-discuss-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: mauve-discuss-owner@sourceware.org X-SW-Source: 2006-q3/txt/msg00034.txt.bz2 >>>>> "Casey" == Casey Marshall writes: Casey> I don't see that much point in using readv/writev for file I/O, anyway, Casey> especially because there do seem to be bugs in our implementation of it. Can you ask the guy who wrote this code in Classpath about his motivations? I don't remember them, and it would be good to know what drove the implementation before we look at removing it. Tom