From: Eduard Hasenleithner <eduardh@aon.at>
To: linux-kernel@vger.kernel.org
Subject: Re: DVD blockdevice buffers
Date: Fri, 18 May 2001 21:59:52 +0200 [thread overview]
Message-ID: <20010518215952.A7919@moserv.hasi> (raw)
In-Reply-To: <20010518210226.A7147@moserv.hasi> <20010518212531.A6763@suse.de>
In-Reply-To: <20010518212531.A6763@suse.de>; from axboe@suse.de on Fri, May 18, 2001 at 09:25:31PM +0200
On Fri, May 18, 2001 at 09:25:31PM +0200, Jens Axboe wrote:
> On Fri, May 18 2001, Eduard Hasenleithner wrote:
> > I have a problem with the buffering mechanism of my blockdevice,
> > namely a ide_scsi DVD-ROM drive. After inserting a DVD and reading
> > data linearly from the DVD, an excessive amount of buffer memory gets
> > allocated.
> >
> > This can easily be reproduced with
> > cat /dev/sr0 > /dev/null
> >
> > Remember, nearly the same task is carried out when playing a DVD.
> >
> > As a result the system performance goes down. I'm still able to use
> > my applications, but es every single piece of unused memory is swapped
> > out, and swapping in costs a certain amount of time.
>
> That's why streaming media applications like a dvd player should use raw
> I/O -- to bypass system cache. See /dev/raw*
>
Oh, thank you. That was very fast!
I use xine. To be honest, the procedure of how to create a raw device
is described in their FAQ. But it is not described, what the raw device
does, only that it provides a speed improvement.
Until today, I didn't know what rawio actually does. Strange that I didn't
come across on some information about it.
Was there a official announcement of the availability of this feature?
Is some more detailled information about the rawio existing?
--
Eduard Hasenleithner
student of
Salzburg University of Applied Sciences and Technologies
next prev parent reply other threads:[~2001-05-18 20:01 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-18 19:02 DVD blockdevice buffers Eduard Hasenleithner
2001-05-18 19:25 ` Jens Axboe
2001-05-18 19:59 ` Eduard Hasenleithner [this message]
2001-05-20 2:36 ` Linus Torvalds
2001-05-23 17:34 ` Stephen C. Tweedie
2001-05-23 18:12 ` Linus Torvalds
2001-05-23 19:57 ` Stephen C. Tweedie
2001-05-23 20:01 ` Linus Torvalds
2001-05-23 20:40 ` Jeff Garzik
2001-05-23 22:32 ` Andrea Arcangeli
2001-05-25 20:12 ` blkdev-pagecache-2 [was Re: DVD blockdevice buffers] Andrea Arcangeli
2001-05-25 20:15 ` Andrea Arcangeli
2001-05-23 22:09 ` DVD blockdevice buffers Andrea Arcangeli
2001-05-23 22:13 ` Alexander Viro
2001-05-23 22:24 ` Andrea Arcangeli
2001-05-24 11:36 ` Stephen C. Tweedie
2001-05-25 15:09 ` Eric W. Biederman
2001-05-25 15:45 ` Stephen C. Tweedie
2001-05-25 17:16 ` Linus Torvalds
2001-05-25 17:40 ` Alexander Viro
2001-05-25 18:05 ` Linus Torvalds
2001-05-25 18:24 ` Alexander Viro
2001-05-25 19:02 ` Stephen C. Tweedie
2001-05-27 6:38 ` Pavel Machek
2001-05-25 21:07 ` Eric W. Biederman
2001-05-25 21:18 ` Linus Torvalds
2001-05-25 22:31 ` Eric W. Biederman
-- strict thread matches above, loose matches on Subject: below --
2001-05-19 18:16 Adam Schrotenboer
2001-05-19 22:56 ` Jens Axboe
2001-05-20 1:55 ` Adam Schrotenboer
2001-05-21 15:44 ` Adam Schrotenboer
2001-05-21 15:47 ` Jens Axboe
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=20010518215952.A7919@moserv.hasi \
--to=eduardh@aon.at \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox