public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dongsheng Yang <yangds.fnst@cn.fujitsu.com>
To: unlisted-recipients:; (no To-header on input)
Cc: Dongsheng Yang <yangds.fnst@cn.fujitsu.com>,
	linux-kernel@vger.kernel.org,
	Steven Rostedt <rostedt@goodmis.org>,
	Frederic Weisbecker <fweisbec@gmail.com>,
	Ingo Molnar <mingo@redhat.com>,
	Peter Zijlstra <peterz@infradead.org>
Subject: Re: [PATCH 9/9] trace: Replace hardcoding of 19 with MAX_NICE.
Date: Sat, 22 Feb 2014 17:05:36 +0800	[thread overview]
Message-ID: <53086860.2010209@cn.fujitsu.com> (raw)
In-Reply-To: <eeb2a85d74c71e0d50c88789f99ad857a6b4b7b4.1392103744.git.yangds.fnst@cn.fujitsu.com>

Hi Peter.
     It seems the all other patches in this set were all applied to tip 
except this one.
What is the problem with the [9/9]? Is there any thing I can do?

Thanx


On 02/11/2014 03:34 PM, Dongsheng Yang wrote:
> Signed-off-by: Dongsheng Yang <yangds.fnst@cn.fujitsu.com>
> cc: Steven Rostedt <rostedt@goodmis.org>
> cc: Frederic Weisbecker <fweisbec@gmail.com>
> cc: Ingo Molnar <mingo@redhat.com>
> ---
>   kernel/trace/ring_buffer_benchmark.c | 6 +++---
>   1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/kernel/trace/ring_buffer_benchmark.c b/kernel/trace/ring_buffer_benchmark.c
> index a5457d5..0434ff1 100644
> --- a/kernel/trace/ring_buffer_benchmark.c
> +++ b/kernel/trace/ring_buffer_benchmark.c
> @@ -40,8 +40,8 @@ static int write_iteration = 50;
>   module_param(write_iteration, uint, 0644);
>   MODULE_PARM_DESC(write_iteration, "# of writes between timestamp readings");
>   
> -static int producer_nice = 19;
> -static int consumer_nice = 19;
> +static int producer_nice = MAX_NICE;
> +static int consumer_nice = MAX_NICE;
>   
>   static int producer_fifo = -1;
>   static int consumer_fifo = -1;
> @@ -308,7 +308,7 @@ static void ring_buffer_producer(void)
>   
>   	/* Let the user know that the test is running at low priority */
>   	if (producer_fifo < 0 && consumer_fifo < 0 &&
> -	    producer_nice == 19 && consumer_nice == 19)
> +	    producer_nice == MAX_NICE && consumer_nice == MAX_NICE)
>   		trace_printk("WARNING!!! This test is running at lowest priority.\n");
>   
>   	trace_printk("Time:     %lld (usecs)\n", time);


  reply	other threads:[~2014-02-22  9:08 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-11  7:34 [PATCH 0/9] Add MAX_NICE, MIN_NICE and NICE_WIDTH macros in prio.h Dongsheng Yang
2014-02-11  7:34 ` [PATCH 1/9] sched: Prio: Use DEFAULT_PRIO to define NICE_TO_PRIO and PRIO_TO_NICE Dongsheng Yang
2014-02-21 21:32   ` [tip:sched/core] " tip-bot for Dongsheng Yang
2014-02-22 18:03   ` [tip:sched/core] sched/prio: Use DEFAULT_PRIO to define NICE_TO_PRIO() and PRIO_TO_NICE() tip-bot for Dongsheng Yang
2014-02-11  7:34 ` [PATCH 2/9] sched: prio: Add 3 macros of MAX_NICE, MIN_NICE and NICE_WIDTH in prio.h Dongsheng Yang
2014-02-21 21:33   ` [tip:sched/core] " tip-bot for Dongsheng Yang
2014-02-22 18:03   ` [tip:sched/core] sched/prio: " tip-bot for Dongsheng Yang
2014-02-11  7:34 ` [PATCH 3/9] sched: prio: Use NICE_WIDTH macro to avoid using of hard coding of 40 and 20 " Dongsheng Yang
2014-02-21 21:33   ` [tip:sched/core] " tip-bot for Dongsheng Yang
2014-02-11  7:34 ` [PATCH 4/9] sched: prio: Add spaces before and after operator of '-' Dongsheng Yang
2014-02-21 21:33   ` [tip:sched/core] " tip-bot for Dongsheng Yang
2014-02-11  7:34 ` [PATCH 5/9] rcu: Use MAX_NICE to replace hard coding of 19 Dongsheng Yang
2014-02-11 15:37   ` Josh Triplett
2014-02-11 16:13     ` Paul E. McKenney
2014-02-11 16:42       ` Peter Zijlstra
2014-02-11 17:42         ` Paul E. McKenney
2014-02-21 21:33   ` [tip:sched/core] " tip-bot for Dongsheng Yang
2014-02-22 18:03   ` [tip:sched/core] rcu: Use MAX_NICE to replace hardcoding " tip-bot for Dongsheng Yang
2014-02-11  7:34 ` [PATCH 6/9] sched: Replace hardcoding of -20 and 19 with MIN_NICE and MAX_NICE Dongsheng Yang
2014-02-21 21:33   ` [tip:sched/core] " tip-bot for Dongsheng Yang
2014-02-22 18:03   ` tip-bot for Dongsheng Yang
2014-02-11  7:34 ` [PATCH 7/9] sys: " Dongsheng Yang
2014-02-11 18:27   ` Kees Cook
2014-02-12  3:59     ` Dongsheng Yang
2014-02-12  6:40       ` Kees Cook
2014-02-21 21:34   ` [tip:sched/core] " tip-bot for Dongsheng Yang
2014-02-22 18:04   ` tip-bot for Dongsheng Yang
2014-02-11  7:34 ` [PATCH 8/9] workqueue: " Dongsheng Yang
2014-02-11 17:50   ` Tejun Heo
2014-02-21 21:34   ` [tip:sched/core] " tip-bot for Dongsheng Yang
2014-02-22 18:04   ` tip-bot for Dongsheng Yang
2014-02-11  7:34 ` [PATCH 9/9] trace: Replace hardcoding of 19 with MAX_NICE Dongsheng Yang
2014-02-22  9:05   ` Dongsheng Yang [this message]
2014-02-22  9:27     ` Peter Zijlstra
2014-02-24 10:46     ` Peter Zijlstra
2014-02-24 14:08       ` Dongsheng Yang
2014-02-24 14:12   ` [PATCH Resend] " Dongsheng Yang
2014-02-24 14:22     ` Peter Zijlstra
2014-02-24 14:29     ` Steven Rostedt
2014-02-24 14:48       ` Peter Zijlstra
2014-02-27 13:33     ` [tip:sched/core] " tip-bot for Dongsheng Yang
2014-02-14  9:22 ` [PATCH 0/9] Add MAX_NICE, MIN_NICE and NICE_WIDTH macros in prio.h Dongsheng Yang
2014-02-14  9:51   ` Peter Zijlstra
2014-02-14  9:54     ` Dongsheng Yang

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=53086860.2010209@cn.fujitsu.com \
    --to=yangds.fnst@cn.fujitsu.com \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox