From: Ingo Molnar <mingo@elte.hu>
To: hechacker1 <hechacker1@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: "REPORT: sd-0.46 vs cfs-v6 vs mainline 2.6.21-rc7 Beryl + Video + Audio"
Date: Fri, 27 Apr 2007 16:05:20 +0200 [thread overview]
Message-ID: <20070427140520.GA27854@elte.hu> (raw)
In-Reply-To: <6700d24e0704262101v132bec29nf9fd6c93fe8748a@mail.gmail.com>
* hechacker1 <hechacker1@gmail.com> wrote:
> "REPORT: sd-0.46 vs cfs-v6 vs mainline 2.6.21-rc7 Beryl + Video + Audio"
thanks for testing it out.
one immediate observation i have is that you used a 2msec granularity
setting on CFS, but even that did not cause context-switching as high as
SD's rr_interval==2 setting:
> cfs-v6:
> 700m kernel # cat sched_granularity_ns
> 2000000
> r b swpd free buff cache si so bi bo in cs us sy id
> 1 0 0 100412 44 1519364 0 0 0 0 7426 7634 62 4 34
> 4 0 0 100288 44 1519364 0 0 0 0 7039 7442 60 6 34
> sd-0.46:
> 700m kernel # cat rr_interval
> 2
> r b swpd free buff cache si so bi bo in cs us sy id
> 5 0 0 918052 536 832840 0 0 411 0 2387 15242 89 11 0
> 4 1 0 915600 536 834908 0 0 388 0 2283 15428 90 10 0
so SD context-switched twice as much and saturated the CPU fully, while
under cfs-v6 there was 34% idle time left. That double context-switch
rate and higher CPU utilization could easily result in you experiencing
a 'smoother' desktop (and smoother video playback) on SD.
could you try to maximize the preemption ratio on CFS by using a
sched_granularity_ns of 0? Does that result in a higher context-switch
rate and in better CPU utilization? Thanks,
Ingo
next prev parent reply other threads:[~2007-04-27 14:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-27 4:01 "REPORT: sd-0.46 vs cfs-v6 vs mainline 2.6.21-rc7 Beryl + Video + Audio" hechacker1
2007-04-27 8:42 ` Kasper Sandberg
2007-04-27 14:05 ` Ingo Molnar [this message]
2007-04-28 1:09 ` Con Kolivas
-- strict thread matches above, loose matches on Subject: below --
2007-04-28 8:39 hechacker1
2007-04-30 0:21 ` hechacker1
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=20070427140520.GA27854@elte.hu \
--to=mingo@elte.hu \
--cc=hechacker1@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox