All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: linux-kernel@vger.kernel.org
Cc: linux-fsdevel@vger.kernel.org
Subject: fadvise syscall?
Date: Sun, 17 Mar 2002 03:39:17 -0500	[thread overview]
Message-ID: <3C945635.4050101@mandrakesoft.com> (raw)

Has anyone ever done an madvise(2)-type syscall for file descriptors?
(or does the capability exist and I'm missing it?)


I was thinking, in playing around with stuff like cp(1) I've found that 
standard read(2) and write(2) of a 4-8K buffer is the fastest solution 
overall, in addition to providing the useful side effect of better error 
reporting, such as ENOSPC report.  Better error reporting than the 
alternative I see anyway, mmap(2).

So... we have madvise, why not fadvise?  I would love the capability for 
applications to provide hints to the OS like madvise, but for file 
descriptors...

    Jeff




             reply	other threads:[~2002-03-17  8:40 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-17  8:39 Jeff Garzik [this message]
2002-03-17  8:56 ` fadvise syscall? Andrew Morton
2002-03-17  9:10   ` Jeff Garzik
2002-03-17 20:18     ` Richard Gooch
2002-03-17 13:41   ` Anton Altaparmakov
2002-03-17 14:31     ` Simon Richter
2002-03-17 14:56       ` Jan Hudec
2002-03-17 15:00     ` Anton Altaparmakov
2002-03-17 19:20     ` Joel Becker
2002-03-17 23:59     ` Anton Altaparmakov
2002-03-18  7:28     ` Jeff Garzik
2002-03-18  7:55       ` Andrew Morton
2002-03-18  8:07         ` Jeff Garzik
2002-03-18  8:17           ` Andrew Morton
2002-03-18 16:41         ` Richard Gooch
2002-03-18 19:00           ` Andrew Morton
2002-03-18 19:15             ` Richard Gooch
2002-03-22 16:05       ` Pavel Machek
2002-03-24  6:38         ` Stevie O
2002-03-24 11:24           ` Pavel Machek
2002-03-24 12:52             ` Anton Altaparmakov
2002-03-25 11:12               ` Pavel Machek
2002-03-18  8:05     ` Joel Becker
2002-03-18  8:10       ` Jeff Garzik
2002-03-18  8:20         ` Joel Becker
2002-03-18  8:14       ` Andrew Morton
2002-03-18 14:39         ` Martin K. Petersen
2002-03-18 19:15           ` Andrew Morton
2002-03-18 19:42             ` Martin K. Petersen
2002-03-19 20:08               ` Eric W. Biederman
2002-03-19 23:38                 ` Martin K. Petersen
2002-03-17 15:13 ` Ken Hirsch
2002-03-17 17:14 ` Anton Altaparmakov
2002-03-17 18:31   ` Mark Mielke
2002-03-17 18:35   ` Ken Hirsch
2002-03-17 19:06   ` Anton Altaparmakov
2002-03-17 20:19     ` Ken Hirsch
2002-03-18  0:12     ` Anton Altaparmakov
     [not found]       ` <a73ujs$5mc$1@cesium.transmeta.com>
2002-03-18  8:58         ` Jan Hudec
2002-03-18 10:08           ` Jeff Garzik
2002-03-18 17:29             ` Mark Mielke

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=3C945635.4050101@mandrakesoft.com \
    --to=jgarzik@mandrakesoft.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.