From: Linus Torvalds <torvalds@transmeta.com>
To: duncan.sands@math.u-psud.fr, Andrea Arcangeli <andrea@suse.de>,
linux-kernel@vger.kernel.org, Al Viro <viro@redhat.com>
Subject: Re: xine pauses with recent (not -ac) kernels
Date: Fri, 12 Oct 2001 20:51:27 -0700 [thread overview]
Message-ID: <200110130351.f9D3pRp08271@penguin.transmeta.com> (raw)
In-Reply-To: <01101300085600.00832@baldrick>
In-Reply-To: <01101208552800.00838@baldrick> <20011012161052.R714@athlon.random>
In article <01101300085600.00832@baldrick> you write:
>>
>> can you reproduce also on 2.4.12aa1?
>>
>> ftp://ftp.us.kernel.org/pub/linux/kernel/people/andrea/kernels/v2.4/2.4.12
>>aa1.bz2
>>
>> Andrea
>
>Yes, it seems to have the same problem. It even seems a bit worse
>(just my impression, I didn't do any statistics).
Let me guess: xine opens the raw device, and does all the DVD parsing
from there.
Furthermore, maybe it closes and re-opens the device for each VOB file.
Which in turn will invalidate the buffer and page cache, and force a
re-read of all the metadata.. Oh, and wait for all the prefetching to
have finished.
If this is it, it should be "fixed" by doing a
sleep 100000 < /dev/dvd-device &
in the background before starting xine?
Does that make any difference?
If it does, then I suspect we should really look into making the raw
device close just leave the device descriptor around at least for a
while. Al?
Linus
next prev parent reply other threads:[~2001-10-13 3:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-12 6:55 Duncan Sands
[not found] ` <20011012161052.R714@athlon.random>
2001-10-12 22:08 ` Duncan Sands
2001-10-12 22:15 ` Andrea Arcangeli
2001-10-13 13:24 ` Duncan Sands
2001-10-13 14:10 ` Andrea Arcangeli
2001-10-13 3:51 ` Linus Torvalds [this message]
2001-10-13 14:23 ` Andrea Arcangeli
2001-10-13 19:58 ` Duncan Sands
2001-10-13 19:39 Andrei Lahun
2001-10-13 20:40 Andrei Lahun
2001-10-14 4:31 Chris Rankin
2001-10-17 21:38 Guenter Bartsch
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=200110130351.f9D3pRp08271@penguin.transmeta.com \
--to=torvalds@transmeta.com \
--cc=andrea@suse.de \
--cc=duncan.sands@math.u-psud.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@redhat.com \
/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
all inboxes | Powered by JetHome®