From: Tom Tromey <tromey@redhat.com>
To: Casey Marshall <csm@gnu.org>
Cc: mauve-discuss@sourceware.org
Subject: Re: multidirectbufferIO and multibufferIO
Date: Tue, 26 Sep 2006 22:26:00 -0000 [thread overview]
Message-ID: <m3bqp2xod7.fsf@localhost.localdomain> (raw)
In-Reply-To: <451822FB.8080109@gnu.org>
>>>>> "Casey" == Casey Marshall <csm@gnu.org> 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
next prev parent reply other threads:[~2006-09-26 22:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-25 18:42 Casey Marshall
2006-09-26 22:26 ` Tom Tromey [this message]
2006-09-27 2:01 ` Casey Marshall
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3bqp2xod7.fsf@localhost.localdomain \
--to=tromey@redhat.com \
--cc=csm@gnu.org \
--cc=mauve-discuss@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).