From: Mike Galbraith <mgalbraith@suse.de>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Peter Zijlstra <peterz@infradead.org>,
RT <linux-rt-users@vger.kernel.org>
Subject: Re: [RFC][PATCH 0/3] update to cpupri algorithm
Date: Fri, 29 Jul 2011 17:38:47 +0200 [thread overview]
Message-ID: <1311953927.30862.64.camel@marge.simson.net> (raw)
In-Reply-To: <20110729151340.419467771@goodmis.org>
On Fri, 2011-07-29 at 11:13 -0400, Steven Rostedt wrote:
> Hi Mike,
>
> Could you try this patch set out. Add the first patch and then
> run your tests. The first patch only adds benchmarking, and does not
> modify the scheduler algorithm.
I will happily do all of the below.
> Do this:
>
> 1. apply first patch, build and boot
> 2. # mount -t debugfs nodev /sys/kernel/debug
> 3. # echo 0 > /sys/kernel/debug/cpupri; ./runtest; cat /sys/kernel/debug/cpupri > output
>
> The output will give you the contention of the vector locks in the
> cpupri algorithm.
>
> Then apply the second patch and do the same thing.
>
> Then apply the third patch and do the same thing.
>
> After that, could you send me the results of the output file for all
> three runs? The final patch should probably be the best overall
> results.
>
> Thanks!
Thank you.
-Mike
next prev parent reply other threads:[~2011-07-29 15:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-29 15:13 [RFC][PATCH 0/3] update to cpupri algorithm Steven Rostedt
2011-07-29 15:13 ` [RFC][PATCH 1/3] cpupri: Add profiling Steven Rostedt
2011-07-29 15:13 ` [RFC][PATCH 2/3] cpupri: Remove vector locks and read entire loop Steven Rostedt
2011-07-29 15:13 ` [RFC][PATCH 3/3] cpupri: Add atomic vector count to speed up loop Steven Rostedt
2011-07-29 15:38 ` Mike Galbraith [this message]
2011-07-29 18:24 ` [RFC][PATCH 0/3] update to cpupri algorithm Mike Galbraith
2011-07-30 7:12 ` Mike Galbraith
2011-07-30 8:16 ` Mike Galbraith
2011-07-30 9:19 ` Mike Galbraith
2011-08-01 14:18 ` Steven Rostedt
2011-08-01 18:41 ` Mike Galbraith
2011-08-01 18:54 ` Steven Rostedt
2011-08-01 19:06 ` Mike Galbraith
2011-08-02 8:59 ` Mike Galbraith
2011-08-02 8:46 ` 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=1311953927.30862.64.camel@marge.simson.net \
--to=mgalbraith@suse.de \
--cc=linux-rt-users@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.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 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.