All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jun Sun <jsun@mvista.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Iain Sandoe <iain@sandoe.co.uk>, linuxppc-dev@lists.linuxppc.org
Subject: Re: [ANN] IRQ Latency tool 0.1.3 release.
Date: Tue, 25 Jul 2000 11:23:50 -0700	[thread overview]
Message-ID: <397DDB36.DA5B68F9@mvista.com> (raw)
In-Reply-To: Pine.LNX.4.10.10007251413580.434-100000@cassiopeia.home


Geert Uytterhoeven wrote:
>
> On Mon, 24 Jul 2000, Iain Sandoe wrote:
> > BTW: on my system ll_rw_blk.c gets up to 750 us quite often when the system
> > is loaded... this **IS** a potential problem for audio use.
> >
> > log entry : 3  (16  history entries)
> >         Peak Block Time  :        430.0 us  (    7185) [ OK ]
> >         startFilename    : ll_rw_blk.c                    Line : 167
> >         endFileName      : ll_rw_blk.c                    Line : 179
> >
> > I still haven't found the "hard-block" that is effecting the overall audio
> > latency performance... ah well, back to the drawing board...
>
> Do you have IDE? The IDE driver turned out to be the major interrupt messing
> problem on m68k, since it can disable interrupts for quite a while.
>
> Gr{oetje,eeting}s,
>
>                                                 Geert

The IDE driver in v2.2.xx has a run-away cli(), which causes long
interrupt blocking times.  See my postings in linux-kernel mailing list
a while back (around March), if you can still find them.  A IDE driver
guys suggested a fix, but I am not sure if it there yet.  The function
is  do_rw_dis().

log entry : 3
(unplug_device in ll_rw_blk.c, calling dev->request_fn(),
 do_rw_disk() in ide-disk.c)
        blockingTime     : 39955
        startFileName    : ide-disk.c
        startFileLine    : 390
        startCount       : 3433912489
        endFileName      : ll_rw_blk.c
        endFileLine      : 172
        endCount         : 3433952444
        unused1,2        : 0, 0

I believe there is a user-land workaround, which involves using "hdparm"
to change some bits.

Jun

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2000-07-25 18:23 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-07-24 22:44 [ANN] IRQ Latency tool 0.1.3 release Iain Sandoe
2000-07-25 12:15 ` Geert Uytterhoeven
2000-07-25 18:23   ` Jun Sun [this message]
2000-07-25 21:39   ` Benjamin Herrenschmidt
2000-07-26 11:54     ` Geert Uytterhoeven
2000-07-28 10:13       ` Takashi Oe
2000-07-28 14:51         ` Geert Uytterhoeven
2000-07-29  0:47           ` [linux-fbdev] " James Simmons
  -- strict thread matches above, loose matches on Subject: below --
2000-07-25 18:29 Iain Sandoe
2000-07-25 21:53 Iain Sandoe
2000-07-26 18:42 Iain Sandoe

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=397DDB36.DA5B68F9@mvista.com \
    --to=jsun@mvista.com \
    --cc=geert@linux-m68k.org \
    --cc=iain@sandoe.co.uk \
    --cc=linuxppc-dev@lists.linuxppc.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 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.