From: Ingo Molnar <mingo@elte.hu>
To: "Oliver Pinter (Pintér Olivér)" <oliver.pntr@gmail.com>
Cc: Al Boldi <a1426z@gawab.com>,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: konqueror deadlocks on 2.6.22
Date: Tue, 22 Jan 2008 11:10:15 +0100 [thread overview]
Message-ID: <20080122101014.GD5722@elte.hu> (raw)
In-Reply-To: <6101e8c40801191417k7906422chf657895152b61a2d@mail.gmail.com>
* Oliver Pinter (Pintér Olivér) <oliver.pntr@gmail.com> wrote:
> and then please update to CFS-v24.1
> http://people.redhat.com/~mingo/cfs-scheduler/sched-cfs-v2.6.22.15-v24.1.patch
> > Yes with CFSv20.4, as in the log.
> >
> > It also hangs on 2.6.23.13
my feeling is that this is some sort of timing dependent race in
konqueror/kde/qt that is exposed when a different scheduler is put in.
If it disappears with CFS-v24.1 it is probably just because the timings
will change again. Would be nice to debug this on the konqueror side and
analyze why it fails and how. You can probably tune the timings by
enabling SCHED_DEBUG and tweaking /proc/sys/kernel/*sched* values - in
particular sched_latency and the granularity settings. Setting wakeup
granularity to 0 might be one of the things that could make a
difference.
Ingo
next prev parent reply other threads:[~2008-01-22 10:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-19 18:14 konqueror deadlocks on 2.6.22 Al Boldi
2008-01-19 18:53 ` Oliver Pinter (Pintér Olivér)
2008-01-19 20:57 ` Al Boldi
2008-01-19 22:17 ` Oliver Pinter (Pintér Olivér)
2008-01-22 10:10 ` Ingo Molnar [this message]
2008-01-22 13:23 ` Al Boldi
2008-01-22 14:25 ` Chris Mason
2008-01-22 18:54 ` Al Boldi
2008-01-22 19:13 ` Chris Mason
[not found] ` <1200802290.4166.2.camel@homer.simson.net>
2008-01-20 5:41 ` Al Boldi
2008-01-20 7:23 ` Mike Galbraith
2008-01-20 7:30 ` Mike Galbraith
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=20080122101014.GD5722@elte.hu \
--to=mingo@elte.hu \
--cc=a1426z@gawab.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oliver.pntr@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).