LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Simon Huggins <huggie@earth.li>
To: Ingo Molnar <mingo@elte.hu>
Cc: linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
Pierre Ossman <drzeus@drzeus.cx>
Subject: Re: Scheduler broken? sdhci issues with scheduling
Date: Sat, 1 Mar 2008 12:42:04 +0000 [thread overview]
Message-ID: <20080301124203.GL24533@paranoidfreak.co.uk> (raw)
In-Reply-To: <20080229203914.GD27212@elte.hu>
(please cc me)
On Fri, Feb 29, 2008 at 09:39:14PM +0100, Ingo Molnar wrote:
> * Simon Huggins <huggie@earth.li> wrote:
> > On Fri, Feb 29, 2008 at 02:34:33PM +0100, Ingo Molnar wrote:
> > > * Simon Huggins <huggie@earth.li> wrote:
> > > > [ Please Cc me on replies ]
> > > > I had a bug with sdhci which Pierre Ossman looked at for me.
> > > > In the end essentially the fix was to use HZ=1000 and nothing else.
> > > > Pierre seemed to think that this was a bug in the scheduler.
> > > does the patch below help, even if you keep HZ=100? This doesnt look
> > > like a scheduler issue, it's more of a timer/timing issue. Different HZ
> > > means different msleep() results - and the mmc code does a loop of small
> > > msleep delays.
> > Thanks for looking at it.
> > I did tests with 2.6.24.3 with HZ=1000 and HZ=100 and as expected the
> > latter didn't work.
[..]
> > That doesn't work. I did a test with HZ=100 and this patch. I've
> > attached the log as patch1-log.
> > Anything else I can try?
> so neither precise, nor imprecise timings help??
I don't know. I don't really understand the patches I applied I'm
afraid; I'm just reporting the results.
I've cc'd Pierre Ossman so he might have a look from the sdhci point of
view.
Pierre, the thread starts here:
http://lkml.org/lkml/2008/2/29/118
Simon.
--
Just another wannabie | "It's so nice to have a big | Just another fool
----------------------+ strong spud around the house." +-------------------
This message was brought to you by the letter E and the number 13.
htag.pl 0.0.22 -- http://www.earth.li/projectpurple/progs/htag.html
next prev parent reply other threads:[~2008-03-01 12:42 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-29 11:52 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 [this message]
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
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=20080301124203.GL24533@paranoidfreak.co.uk \
--to=huggie@earth.li \
--cc=drzeus@drzeus.cx \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--subject='Re: Scheduler broken? sdhci issues with scheduling' \
/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
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).