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: Mon, 01 Aug 2011 21:06:34 +0200 [thread overview]
Message-ID: <1312225594.8151.91.camel@marge.simson.net> (raw)
In-Reply-To: <1312224871.18583.72.camel@gandalf.stny.rr.com>
On Mon, 2011-08-01 at 14:54 -0400, Steven Rostedt wrote:
> On Mon, 2011-08-01 at 20:41 +0200, Mike Galbraith wrote:
>
> > > Thanks for testing! I'll redo the patches to remove the logging, and
> > > send them to you again. Could you return back a 'Tested-by' tag
> > > afterward.
> >
> > (I did the logging removal, the posted numbers were that, but..)
>
> Could you merge the two patches and diff them against the one I posted
> privately. Just to make sure that you really tested the one I plan on
> giving to Mainline.
Good idea, will do.
-Mike
next prev parent reply other threads:[~2011-08-01 19:06 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 ` [RFC][PATCH 0/3] update to cpupri algorithm Mike Galbraith
2011-07-29 18:24 ` 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 [this message]
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=1312225594.8151.91.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.