From: Peter Zijlstra <peterz@infradead.org>
To: Dongsheng Yang <dongsheng081251@gmail.com>
Cc: Dongsheng Yang <yangds.fnst@cn.fujitsu.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: Thu, 8 May 2014 17:26:14 +0200 [thread overview]
Message-ID: <20140508152614.GC30445@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <CA+qeAOqCo9g=tNARWf4JESLZU6sAoSKYDvmfGE6OOmJQhajyDw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 421 bytes --]
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 :-)
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2014-05-08 15:26 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 [this message]
2014-05-09 0:10 ` Dongsheng Yang
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=20140508152614.GC30445@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=dongsheng081251@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=yangds.fnst@cn.fujitsu.com \
/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.