public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jb at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/25561]  New: Eventually get rid of the Alloc Stream Facility
Date: Sun, 25 Dec 2005 18:23:00 -0000	[thread overview]
Message-ID: <bug-25561-11659@http.gcc.gnu.org/bugzilla/> (raw)

Currently the gfortran IO library is based on a design called the "Alloc Stream
Facility" (ASF), described in the paper 

 *  "Exploiting the advantages of mapped files for stream I/O",
 *  O. Krieger, M. Stumm and R. Umrau, "Proceedings of the 1992 Winter
 *  USENIX conference", p. 27-42.

The idea is to present an interface that avoids an extra copy when used
together with mmap, and the application uses ASF directly instead of
read/write. However, Fortran IO follows a traditional read/write model, and
thus the buffer copy is still needed in the library.

Thus, ASF makes the IO library unnecessarily complex and doesn't improve
performance. If ASF would provide any real benefit, it could be implemented in
the C library or the kernel, and any program using read/write, including the
gfortran IO library, would benefit.


-- 
           Summary: Eventually get rid of the Alloc Stream Facility
           Product: gcc
           Version: unknown
            Status: UNCONFIRMED
          Severity: enhancement
          Priority: P3
         Component: libfortran
        AssignedTo: jb at gcc dot gnu dot org
        ReportedBy: jb at gcc dot gnu dot org


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25561


             reply	other threads:[~2005-12-25 18:23 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-25 18:23 jb at gcc dot gnu dot org [this message]
2006-01-17 22:10 ` [Bug libfortran/25561] " jb at gcc dot gnu dot org
2006-01-29 23:25 ` tkoenig at gcc dot gnu dot org
2007-09-14 11:33 ` fxcoudert at gcc dot gnu dot org
2007-09-16 14:13 ` jb at gcc dot gnu dot org
2008-05-02 15:38 ` jb at gcc dot gnu dot org
2008-05-13 19:07 ` jb at gcc dot gnu dot org
2008-05-15 15:55 ` jb at gcc dot gnu dot org
2008-05-15 18:34 ` jb at gcc dot gnu dot org
2008-05-16  8:13 ` jb at gcc dot gnu dot org
2008-05-16 17:44 ` jb at gcc dot gnu dot org
2009-01-05 22:15 ` jb at gcc dot gnu dot org
2009-01-18  9:30 ` jb at gcc dot gnu dot org
2009-03-22 10:51 ` jb at gcc dot gnu dot org
2009-04-05 20:14 ` jvdelisle at gcc dot gnu dot org
2009-05-27  1:23 ` jvdelisle at gcc dot gnu dot org
2009-06-04  6:43 ` burnus at gcc dot gnu dot org
2009-06-04  7:40 ` jb at gcc dot gnu dot org

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=bug-25561-11659@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.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).