mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Greg Stark <gsstark@mit.edu>
To: Gregory Stark <gsstark@MIT.EDU>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Problem with read blocking for a long time on /dev/scd1
Date: 21 Dec 2002 01:14:38 -0500	[thread overview]
Message-ID: <87u1h799v5.fsf@stark.dyndns.tv> (raw)
In-Reply-To: <87adj0b3hj.fsf@stark.dyndns.tv>


Gregory Stark <gsstark@MIT.EDU> writes:

> I'm having a problem with ogle that seems to be being caused by the scsi or
> ide-scsi driver. The video playback freezes for a second or randomly,
> sometimes every few seconds, sometimes not for several minutes. Every such
> glitch is correlated perfectly with a read syscall reading on /dev/scd1
> blocking for an inordinate amount of time.
> 
> Most read syscalls from ogle seem to take between 30us to 100ms depending on
> the size of the read. In fact plotting the time taken reported by strace -T vs
> the size of the read in gnuplot produces a nice obvious linear correlation.

One more piece of data I just found. Whenever the read blocks for a long time
like this it seems ps lists the process's wait channel as "lock_p". The only
matching symbol is lock_page. 

Does that help narrow down the source of the latency or is that just what the
device driver happens to use as its synchronization primitive?

--
greg


  parent reply	other threads:[~2002-12-21  6:06 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-21  0:49 Gregory Stark
2002-12-21  1:28 ` Greg Stark
2002-12-21  6:14 ` Greg Stark [this message]
2002-12-22 16:13   ` More tests [Was: Problem with read blocking for a long time on /dev/scd1] Greg Stark
2002-12-22 20:13     ` Jakob Oestergaard
2002-12-23  8:58       ` Greg Stark
2002-12-27 15:36         ` Jakob Oestergaard
2003-01-08  4:03         ` Jakob Oestergaard
2002-12-23 18:02 ` Problem with read blocking for a long time on /dev/scd1 Krzysztof Halasa
2002-12-21  0:51 Gregory Stark

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=87u1h799v5.fsf@stark.dyndns.tv \
    --to=gsstark@mit.edu \
    --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

all inboxes | Powered by JetHome®