From: "Guillaume Chazarain" <guichaz@yahoo.fr>
To: vatsa@linux.vnet.ibm.com
Cc: "Ingo Molnar" <mingo@elte.hu>,
LKML <linux-kernel@vger.kernel.org>,
a.p.zijlstra@chello.nl, dhaval@linux.vnet.ibm.com
Subject: Re: High wake up latencies with FAIR_USER_SCHED
Date: Mon, 28 Jan 2008 17:57:49 +0100 [thread overview]
Message-ID: <3d8471ca0801280857m2ea8518ds2ad8d5346f756a0e@mail.gmail.com> (raw)
In-Reply-To: <20080128023129.GD1044@linux.vnet.ibm.com>
Hi Srivatsa,
On Jan 28, 2008 3:31 AM, Srivatsa Vaddagiri <vatsa@linux.vnet.ibm.com> wrote:
> Given that sysctl_sched_wakeup_granularity is set to 10ms by default,
> this doesn't sound abnormal.
Indeed, by lowering sched_wakeup_granularity I get much better
latencies, but lowering sched_latency seems to be more effective.
> NEW_FAIR_SLEEPERS feature gives credit for sleeping only to tasks and
> not group-level entities. With the patch attached, I could see that wakeup
> latencies with FAIR_USER_SCHED are restored to the same level as
> !FAIR_USER_SCHED.
Thanks for the patch, it works perfectly.
> However I am not sure whether that is the way to go. We want to let one group of
> tasks running as much as possible until the fairness/wakeup-latency threshold is
> exceeded. If someone does want better wakeup latencies between groups too, they
> can always tune sysctl_sched_wakeup_granularity.
Having an inconsistency here between FAIR_USER_SCHED and
!FAIR_USER_SCHED sounds strange, but Ingo took the patch, so I'm happy
:-)
Thanks for the replies.
--
Guillaume
next prev parent reply other threads:[~2008-01-28 16:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-27 20:01 Guillaume Chazarain
2008-01-28 2:31 ` Srivatsa Vaddagiri
2008-01-28 12:27 ` Ingo Molnar
2008-01-28 16:57 ` Guillaume Chazarain [this message]
2008-01-28 20:13 ` Guillaume Chazarain
2008-01-29 5:47 ` Srivatsa Vaddagiri
2008-01-29 15:53 ` Guillaume Chazarain
2008-01-29 16:26 ` Srivatsa Vaddagiri
2008-01-31 10:47 ` Peter Zijlstra
2008-01-31 12:49 ` Guillaume Chazarain
2008-01-31 13:00 ` Peter Zijlstra
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=3d8471ca0801280857m2ea8518ds2ad8d5346f756a0e@mail.gmail.com \
--to=guichaz@yahoo.fr \
--cc=a.p.zijlstra@chello.nl \
--cc=dhaval@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=vatsa@linux.vnet.ibm.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
all inboxes | Powered by JetHome®