From: Gerard Roudier <groudier@club-internet.fr>
To: linux-sound@vger.kernel.org
Subject: Re: Streaming disk I/O kills file buffering and makes Linux unusable
Date: Tue, 24 Aug 1999 07:56:05 +0000 [thread overview]
Message-ID: <marc-linux-sound-93548056018106@msgid-missing> (raw)
In-Reply-To: <marc-linux-sound-93541443318803@msgid-missing>
On Tue, 24 Aug 1999, Gerard Roudier wrote:
> If you are in a hurry but are a courageous guy ;-), you can, for now, add
> some file control (fcntl) option that tells the kernel to discard the
> pages of data of this file once read by user
> (or just to set the pages at the end of the LRU in recent kernels),
This suggestion anticipates too much about page map LRU inclusion in the
kernel main stream and just makes the suggestion just broken). Without
Andrea's page LRU, it may happen that useful page of data will still be
thrown away after a shrink_mmap revolution.
By the way, if 2.4 does not include Andrea's page LRU, I know of people
who will be very disappointed.
> then make appropriate changes in
> the kernel and in the application. The kernel will still prefetch file
> data on read, allowing read streaming, without having to multithread IOs
> at application level.
>
> Sorry if this has been already suggested.
>
> Gérard.
>
> On Mon, 23 Aug 1999, Benno Senoner wrote:
>
> > On Mon, 23 Aug 1999, Alan Cox wrote:
> > > > I'm afraid, if we want that Linux will be a good multimedia OS, this is a
> > > > _STRONGLY_NEEDED_ feature.
> > > >
> > > > The user wants to playback his video/audio from disk, and still be able
> > > > to launch his apps, without waiting 10 secs for loading a simple xterm.
> > > >
> > > > The SCT's raw-io patches are nice, but not very suitable in a general purpose
> > > > multimedia enviroment, since you can't tell to the user to store his videos on a
> > > > raw partition.
> > >
> > > Stephens patches are basis of raw I/O on files in a filesystem too.
> >
> > That sounds nice to me !
> > Any idea when some patches ( for raw file I/O in a filesystem) will be available
> > ?
> > >
> > > However what you are saying and raw-io don't neccessarily tally. You are
> > > actually saying "there is a bug in the current page cache handling for
> > > this kind of operation". Far better therefore to fix the heuristic used.
> >
> > No , I'm not saying that there is a bug, I'm saying that the
> > filebuffering works very well in almost all cases , except of reading large
> > files from disk continuously.
> > This is of course quite logical since the kernel makes assumptions that you
> > will read this large file again, and therefore the kernel has to put it into
> > the buffer cache.
> >
> > In this case I don't need raw I/O to get fast response or higher throughput,
> > but only to avoid that the streaming apps do not monopolizes the buffer, which
> > is very bad.
> >
> > will the SCT's patches add an O_DIRECT -like flag ala SGI ?
> >
> > regards,
> > Benno.
> >
> > -
> > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> > the body of a message to majordomo@vger.rutgers.edu
> > Please read the FAQ at http://www.tux.org/lkml/
>
>
prev parent reply other threads:[~1999-08-24 7:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-08-23 13:20 Streaming disk I/O kills file buffering and makes Linux unusable Benno Senoner
1999-08-23 17:06 ` Peter Monta
1999-08-23 17:25 ` Linus Torvalds
1999-08-23 17:42 ` Peter Monta
1999-08-23 18:06 ` Benno Senoner
1999-08-23 18:32 ` Alan Cox
1999-08-23 18:39 ` Chuck Lever
1999-08-23 19:25 ` Andrea Arcangeli
1999-08-23 20:20 ` Benno Senoner
1999-08-23 20:50 ` Benno Senoner
1999-08-23 20:51 ` Benno Senoner
1999-08-23 21:01 ` Andrea Arcangeli
1999-08-24 0:48 ` Dave Mielke
1999-08-24 7:37 ` Gerard Roudier
1999-08-24 7:56 ` Gerard Roudier [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=marc-linux-sound-93548056018106@msgid-missing \
--to=groudier@club-internet.fr \
--cc=linux-sound@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox