public inbox for mauve-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Casey Marshall <csm@gnu.org>
To: tromey@redhat.com
Cc: mauve-discuss@sourceware.org
Subject: Re: multidirectbufferIO and multibufferIO
Date: Wed, 27 Sep 2006 02:01:00 -0000	[thread overview]
Message-ID: <4519DB4B.30900@gnu.org> (raw)
In-Reply-To: <m3bqp2xod7.fsf@localhost.localdomain>

Tom Tromey wrote:
>>>>>> "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.
> 

It's probably moot, now. I've figured out why writeGathering wasn't
working, and am working on a similar fix for readScattering. Since there
don't seem to be any problems with using readv/writev (correctly) for
files, we can leave this in.

      reply	other threads:[~2006-09-27  2:01 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
2006-09-27  2:01   ` Casey Marshall [this message]

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=4519DB4B.30900@gnu.org \
    --to=csm@gnu.org \
    --cc=mauve-discuss@sourceware.org \
    --cc=tromey@redhat.com \
    /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).