From: Casey Marshall <csm@gnu.org>
To: mauve-discuss@sourceware.org
Subject: multidirectbufferIO and multibufferIO
Date: Mon, 25 Sep 2006 18:42:00 -0000 [thread overview]
Message-ID: <451822FB.8080109@gnu.org> (raw)
These two tests, in gnu.testlet.java.nio.channels.FileChannel, look a
bit bogus to me. They test if FileChannel artificially limits the number
of buffers processed in scattering/gathering read/write to 16, which is
definitely the case if the underlying implementation uses readv and
writev, but this limit isn't required otherwise (at least, there is no
mention of any limit in the JDK docs).
I don't see that much point in using readv/writev for file I/O, anyway,
especially because there do seem to be bugs in our implementation of it.
And at any rate, there's no guarantee that on some other system there
would be any limit like this, or if there is, that it would be the same
as it is on POSIXy systems.
next reply other threads:[~2006-09-25 18:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-25 18:42 Casey Marshall [this message]
2006-09-26 22:26 ` Tom Tromey
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=451822FB.8080109@gnu.org \
--to=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).