From: Pierre Ossman <drzeus-list@drzeus.cx>
To: Pavel Machek <pavel@ucw.cz>
Cc: huggie@earth.li, linux-kernel@vger.kernel.org
Subject: Re: Scheduler broken? sdhci issues with scheduling
Date: Mon, 3 Mar 2008 22:05:30 +0100 [thread overview]
Message-ID: <20080303220530.49201544@mjolnir.drzeus.cx> (raw)
In-Reply-To: <20080303203808.GH13869@elf.ucw.cz>
On Mon, 3 Mar 2008 21:38:08 +0100
Pavel Machek <pavel@ucw.cz> wrote:
> On Mon 2008-03-03 20:43:00, Pierre Ossman wrote:
> > The problem is that the kernel sleeps _less_ than asked for, not more. No hardware can be expected to work if its needed delays aren't respected.
> >
>
> Oops, that's bad. Can you perhaps create small testcase for
> scheduler/timer people to play with?
>
> Also... you may want to switch timesources. notsc fixed "wait for much
> too long" for me.
I'm afraid I could never reproduce the problem. So it's Simon that will have to do the tests for now..
--
-- Pierre Ossman
Linux kernel, MMC maintainer http://www.kernel.org
PulseAudio, core developer http://pulseaudio.org
rdesktop, core developer http://www.rdesktop.org
next prev parent reply other threads:[~2008-03-03 21:07 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-29 11:52 Scheduler broken? sdhci issues with scheduling Simon Huggins
2008-02-29 13:34 ` Ingo Molnar
2008-02-29 13:51 ` Ingo Molnar
2008-02-29 14:00 ` Ingo Molnar
2008-02-29 19:39 ` Simon Huggins
2008-02-29 20:39 ` Ingo Molnar
2008-03-01 12:42 ` Simon Huggins
2008-03-01 14:08 ` Pierre Ossman
2008-03-02 10:40 ` Pavel Machek
2008-03-02 18:04 ` Simon Huggins
2008-03-03 19:43 ` Pierre Ossman
2008-03-03 20:38 ` Pavel Machek
2008-03-03 21:05 ` Pierre Ossman [this message]
2008-03-13 21:17 ` Simon Huggins
2008-03-15 15:04 ` Pierre Ossman
2008-04-20 21:07 ` Simon Huggins
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=20080303220530.49201544@mjolnir.drzeus.cx \
--to=drzeus-list@drzeus.cx \
--cc=huggie@earth.li \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
/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.