From: Jens Axboe <axboe@suse.de>
To: "Martin J. Bligh" <mbligh@aracnet.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Long pauses (IO?) whilst ripping DVDs
Date: Sun, 4 Jan 2004 13:22:24 +0100 [thread overview]
Message-ID: <20040104122224.GG3418@suse.de> (raw)
In-Reply-To: <34270000.1073154474@[10.10.2.4]>
On Sat, Jan 03 2004, Martin J. Bligh wrote:
>
>
> --Jens Axboe <axboe@suse.de> wrote (on Saturday, January 03, 2004 13:26:14 +0100):
>
> > On Fri, Jan 02 2004, Martin J. Bligh wrote:
> >> Start transcode in one window, doing something like:
> >> "transcode -i /dev/hdc -x dvd -U file_name -y divx4"
> >> on a DVD ... probably pretty CPU intensive as well as IO.
> >>
> >> Now do ls in another window ... hangs for about 5 seconds before
> >> giving any output ;-( Anyone else seeing that? I do get a lot of
> >> "*** libdvdread: CHECK_VALUE failed in nav_read.c:202 ***"
> >> messages as well ... but I always seem to get those from DVD stuff.
> >
> > DMA or PIO? vmstat info would be very handy here.
> >
> > --
> > Jens Axboe
> >
> >
>
> OK, now I'm really confused ... sometimes it happens. sometimes it doesn't
> with no apparent rhyme or reason. You're welcome to the data I have though.
You have periods of excessive system usage, although DMA is enabled on
the drive. Depending on what transcode does, it might still be using pio
though. Any chance you can profile such a 'sy' peak so we can see what's
going on?
Looks odds, though. I'm inclined to guess this is a CPU scheduler
problem. Does booting with elevator=deadline change anything at all?
--
Jens Axboe
next prev parent reply other threads:[~2004-01-04 12:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-03 6:24 Long pauses (IO?) whilst ripping DVDs Martin J. Bligh
2004-01-03 12:26 ` Jens Axboe
2004-01-03 18:27 ` Martin J. Bligh
2004-01-04 12:22 ` Jens Axboe [this message]
2004-01-03 19:53 ` Martin J. Bligh
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=20040104122224.GG3418@suse.de \
--to=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@aracnet.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 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.