From: Peter Zijlstra <peterz@infradead.org>
To: byungchul.park@lge.com
Cc: mingo@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] sched: modify how to compute a slice and check a preemptability
Date: Sun, 19 Jul 2015 13:15:09 +0200 [thread overview]
Message-ID: <20150719111509.GV19282@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <1437297060-25378-1-git-send-email-byungchul.park@lge.com>
On Sun, Jul 19, 2015 at 06:11:00PM +0900, byungchul.park@lge.com wrote:
> doesn't it make sense?
No, people have already given you all kinds of reasons why this isn't a
good change. It is also a very invasive change and you have no
performance numbers one way or another.
I'm going to fully ignore this thread from now on.
next prev parent reply other threads:[~2015-07-19 11:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-19 9:11 byungchul.park
2015-07-19 11:15 ` Peter Zijlstra [this message]
2015-07-20 0:08 ` Byungchul Park
2015-07-19 11:57 ` Mike Galbraith
2015-07-20 0:34 ` Byungchul Park
2015-07-20 3:42 ` Mike Galbraith
2015-07-20 4:47 ` Byungchul Park
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=20150719111509.GV19282@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=byungchul.park@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.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
Powered by JetHome