From: Icarus Sparry I.Sparry@ss1.bath.ac.uk
Subject: sfio vs bio
Date: Mon, 5 Jul 1993 06:06:20 -0400 [thread overview]
Message-ID: <19930705100620.V-shlqXfKw9uAZyk-VkSaixFw0wxtml65_Eo5XKyYuw@z> (raw)
David Korn and Kiem-Phong Vo have just released a new version of sfio,
the 'Safe Fast I/O' package, which is designed as a replacement for
stdio.
The paper 'How to use the Plan 9 C Compiler' tells us "Bio is a small
and very efficient, particularly for buffer-at-a-time or line-at-a-time
I/O. Even for character-at-a-time I/O, however, it is significantly
faster than the Standard I/O library"
Before I do it, has anyone else measured these two on similar hardware
(e.g. Sun Sparc-Station 2, running SunOS)? The paper with sfio gives
some figures for Andrew Humes FIO package and some existing stdio
packages.
Sfio has more facilities, e.g. you can define error handlers for
streams, and can make use of operating system facilities like memory
mapped files.
Icarus
next reply other threads:[~1993-07-05 10:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1993-07-05 10:06 Icarus [this message]
1993-07-05 17:20 mike
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=19930705100620.V-shlqXfKw9uAZyk-VkSaixFw0wxtml65_Eo5XKyYuw@z \
--to=9fans@9fans.net \
/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 NNTP newsgroup(s).