From: Dongsheng Yang <yangds.fnst@cn.fujitsu.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Dongsheng Yang <dongsheng081251@gmail.com>, <mingo@redhat.com>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/2] treewide: remove all open implementation of nice_to_rlimit()/rlimit_to_nice().
Date: Fri, 9 May 2014 09:10:00 +0900 [thread overview]
Message-ID: <536C1CD8.2030602@cn.fujitsu.com> (raw)
In-Reply-To: <20140508152614.GC30445@twins.programming.kicks-ass.net>
On 05/09/2014 12:26 AM, Peter Zijlstra wrote:
> On Thu, May 08, 2014 at 10:51:13PM +0800, Dongsheng Yang wrote:
>> Just want to avoid using hardcoding of 20. If no, there is no meaning we
>> collect
>> priority related information into prio.h. And convertion between nice
>> value [-20,19]
>> and rlimit style value [0,40] is used by several callers currently.
>>
> Yeah, not really a comment on your patch, just a general observation on
> the thing you touched :-)
Ha, okey, thanx for your reply. :)
next prev parent reply other threads:[~2014-05-09 1:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-08 9:33 [PATCH 1/2] sched/prio: Add two inline function named nice_to_rlimit() and rlimit_to_nice() in prio.h Dongsheng Yang
2014-05-08 9:33 ` [PATCH 2/2] treewide: remove all open implementation of nice_to_rlimit()/rlimit_to_nice() Dongsheng Yang
2014-05-08 14:34 ` Peter Zijlstra
[not found] ` <CA+qeAOqCo9g=tNARWf4JESLZU6sAoSKYDvmfGE6OOmJQhajyDw@mail.gmail.com>
2014-05-08 15:26 ` Peter Zijlstra
2014-05-09 0:10 ` Dongsheng Yang [this message]
2014-05-19 13:10 ` [tip:sched/core] sched: Remove " tip-bot for Dongsheng Yang
2014-05-22 12:28 ` [tip:sched/core] sched: Consolidate open coded implementations of nice level frobbing into nice_to_rlimit () and rlimit_to_nice() tip-bot for Dongsheng Yang
2014-05-19 13:10 ` [tip:sched/core] sched/prio: Add two inline function named nice_to_rlimit() and rlimit_to_nice() in prio.h tip-bot for 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=536C1CD8.2030602@cn.fujitsu.com \
--to=yangds.fnst@cn.fujitsu.com \
--cc=dongsheng081251@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.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