[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1416889208.4335.127.camel@maggy.simpson.net>
Date: Mon, 24 Nov 2014 21:20:08 -0700
From: Mike Galbraith <umgwanakikbuti@...il.com>
To: Thomas Gleixner <tglx@...utronix.de>
Cc: Khalid Aziz <khalid.aziz@...cle.com>, corbet@....net,
mingo@...hat.com, hpa@...or.com, peterz@...radead.org,
riel@...hat.com, akpm@...ux-foundation.org, rientjes@...gle.com,
ak@...ux.intel.com, mgorman@...e.de, liwanp@...ux.vnet.ibm.com,
raistlin@...ux.it, kirill.shutemov@...ux.intel.com,
atomlin@...hat.com, avagin@...nvz.org, gorcunov@...nvz.org,
serge.hallyn@...onical.com, athorlton@....com, oleg@...hat.com,
vdavydov@...allels.com, daeseok.youn@...il.com,
keescook@...omium.org, yangds.fnst@...fujitsu.com,
sbauer@....utah.edu, vishnu.ps@...sung.com, axboe@...com,
paulmck@...ux.vnet.ibm.com, linux-kernel@...r.kernel.org,
linux-doc@...r.kernel.org, linux-api@...r.kernel.org
Subject: Re: [PATCH v3] sched/fair: Add advisory flag for borrowing a
timeslice (was: Pre-emption control for userspace)
On Tue, 2014-11-25 at 00:35 +0100, Thomas Gleixner wrote:
> Aside of the general issues I have with this (see the inline replies
> to your changelog) the overall impression of this patch is that it is
> a half baken and carelessly cobbled together extract of some data base
> specific kernel hackery, which I prefer not to see at all.
It culminates in a lumbering pseudo RT class of task disguised as a fair
class task. I'd expect more gain by twiddling knobs to let last buddy
do its job than the 3% mentioned.
You could perhaps create a SUPER_BATCH class that is not wakeup
preempted by any fair class task of <= priority, not only BATCH and
IDLE, but that's as nasty as this patch, though loads prettier. The
tick time thing doesn't feel right at all... if you're hurt badly by the
tick, you're likely holding the lock too long methinks.
-Mike
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists