From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
To: kus Kusche Klaus <kus@keba.com>
Cc: linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org
Subject: Re: 2.6.11, IDE: Strange scheduling behaviour: high-pri RT process not scheduled?
Date: Wed, 30 Mar 2005 14:06:37 +0200 [thread overview]
Message-ID: <58cb370e05033004065b14da51@mail.gmail.com> (raw)
In-Reply-To: <AAD6DA242BC63C488511C611BD51F3673231C2@MAILIT.keba.co.at>
On Wed, 30 Mar 2005 13:52:05 +0200, kus Kusche Klaus <kus@keba.com> wrote:
> However, things break seriously when exercising the CF card in parallel
> (e.g. with a dd if=/dev/hda of=/dev/null):
>
> * The rtc *interrupt handler* is delayed for up to 250 *micro*seconds.
> This is very bad for my purpose, but easy to explain: It is roughly the
> time needed to transfer 512 Bytes from a CF card which can transfer 2
> Mbyte/sec, and obviously, the CPU blocks all interrupts while making pio
>
> transfers. (Why? Is this really necessary?)
>
> (I know because I instrumented the rtc irq handler with rdtscl(), too)
hdparm -u1 /dev/hda
should help
next prev parent reply other threads:[~2005-03-30 12:06 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-30 11:52 2.6.11, IDE: Strange scheduling behaviour: high-pri RT process not scheduled? kus Kusche Klaus
2005-03-30 11:52 ` kus Kusche Klaus
2005-03-30 12:06 ` Bartlomiej Zolnierkiewicz [this message]
2005-03-30 14:41 ` Mark Hahn
2005-03-30 14:41 ` Mark Hahn
2005-03-30 20:37 ` Lee Revell
2005-03-31 11:35 ` Ingo Molnar
-- strict thread matches above, loose matches on Subject: below --
2005-03-30 12:21 kus Kusche Klaus
2005-03-30 12:21 ` kus Kusche Klaus
2005-03-31 11:05 kus Kusche Klaus
2005-03-31 11:05 ` kus Kusche Klaus
2005-03-31 15:19 kus Kusche Klaus
2005-03-31 15:19 ` kus Kusche Klaus
2005-03-31 15:22 ` Ingo Molnar
2005-04-01 9:07 kus Kusche Klaus
2005-04-01 9:07 ` kus Kusche Klaus
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=58cb370e05033004065b14da51@mail.gmail.com \
--to=bzolnier@gmail.com \
--cc=kus@keba.com \
--cc=linux-ide@vger.kernel.org \
--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 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.