All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Juri Lelli <juri.lelli@gmail.com>
Cc: tglx@linutronix.de, mingo@redhat.com, rostedt@goodmis.org,
	oleg@redhat.com, fweisbec@gmail.com, darren@dvhart.com,
	johan.eker@ericsson.com, p.faure@akatech.ch,
	linux-kernel@vger.kernel.org, claudio@evidence.eu.com,
	michael@amarulasolutions.com, fchecconi@gmail.com,
	tommaso.cucinotta@sssup.it, nicola.manica@disi.unitn.it,
	luca.abeni@unitn.it, dhaval.giani@gmail.com, hgu1972@gmail.com,
	paulmck@linux.vnet.ibm.com, raistlin@linux.it,
	insop.song@ericsson.com, liming.wang@windriver.com,
	jkacur@redhat.com, harald.gustafsson@ericsson.com
Subject: Re: [PATCH 13/15] sched: add bandwidth management for sched_dl.
Date: Tue, 29 May 2012 11:58:06 +0200	[thread overview]
Message-ID: <1338285486.26856.16.camel@twins> (raw)
In-Reply-To: <4FC0B95C.5060207@gmail.com>

On Sat, 2012-05-26 at 13:07 +0200, Juri Lelli wrote:
> Hi,
> 
> On 05/25/2012 12:38 PM, Peter Zijlstra wrote:
> > On Wed, 2012-05-23 at 23:42 +0200, Juri Lelli wrote:
> >> +/*
> >> + * Coupling of -dl and -rt bandwidth.
> >> + *
> >> + * Here we check, while setting the system wide bandwidth available
> >> + * for -dl tasks and groups, if the new values are consistent with
> >> + * the system settings for the bandwidth available to -rt entities.
> >> + *
> >> + * IOW, we want to enforce that
> >> + *
> >> + *   rt_bandwidth + dl_bandwidth<= 100%
> >> + *
> >> + * is always true.
> >> + */
> >
> > I was thinking we could do it the other way around, have have
> > dl_bandwidth included in rt_bandwidth.
> >
> 
> If I understand correctly, you are proposing to treat -dl tasks as a
> special case of "real-time" tasks. Then we could reserve some bw to
> "real-time" (rt_bandwidth cap) activities and give a piece of this
> bw to -dl tasks (what remains is for -rt tasks). This is in principle
> nice and useful, but I'm not quite sure that this is the right point
> to achieve this logical behavior.
> I mean, -dl and -rt tasks are separately treated, so it is probably
> cleaner to manage their knobs separately. They have to coexist rather
> than be considered one a sub-case of the other. A better way to go
> for a common cap for them is probably the (long-term) hierarchical
> scheduling mechanism.
> 
> So, I would prefer to keep the interface as is for now, but I can also
> completely misunderstood your thoughts :-P.

The thing is, keeping it separate makes for an impossible configuration
scenario. Esp. once we enable !root usage. The proposed 5% is very
limiting and regular users won't have sufficient privilege to change it.

Also lowering FIFO/RR by default isn't a real option since people expect
that to get all time already (however silly that expectation is).






  reply	other threads:[~2012-05-29  9:59 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-23 21:42 [RFC][PATCH 00/15] sched: SCHED_DEADLINE v5 Juri Lelli
2012-05-23 21:42 ` [PATCH 01/15] math128: Introduce various 128bit primitives Juri Lelli
2012-05-23 21:42 ` [PATCH 02/15] math128, x86_64: Implement {mul,add}_u128 in 64bit asm Juri Lelli
2012-05-23 21:42 ` [PATCH 03/15] sched: add sched_class->task_dead Juri Lelli
2012-05-23 21:42 ` [PATCH 04/15] sched: add extended scheduling interface Juri Lelli
2012-05-23 21:42 ` [PATCH 05/15] sched: SCHED_DEADLINE structures & implementation Juri Lelli
2012-05-23 21:42 ` [PATCH 06/15] sched: SCHED_DEADLINE SMP-related data structures & logic Juri Lelli
2012-05-23 21:42 ` [PATCH 07/15] sched: SCHED_DEADLINE avg_update accounting Juri Lelli
2012-05-23 21:42 ` [PATCH 08/15] sched: add period support for -deadline tasks Juri Lelli
2012-05-23 21:42 ` [PATCH 09/15] sched: add schedstats " Juri Lelli
2012-05-23 21:42 ` [PATCH 10/15] sched: add latency tracing " Juri Lelli
2012-05-23 21:42 ` [PATCH 11/15] rtmutex: turn the plist into an rb-tree Juri Lelli
2012-05-23 21:42 ` [PATCH 12/15] sched: drafted deadline inheritance logic Juri Lelli
2012-05-23 21:42 ` [PATCH 13/15] sched: add bandwidth management for sched_dl Juri Lelli
2012-05-25 10:38   ` Peter Zijlstra
2012-05-26 11:07     ` Juri Lelli
2012-05-29  9:58       ` Peter Zijlstra [this message]
2012-05-29 12:18         ` Juri Lelli
2012-05-29 12:31           ` Peter Zijlstra
2012-05-30 15:34             ` Juri Lelli
2012-05-23 21:42 ` [PATCH 14/15] sched: speed up -dl pushes with a push-heap Juri Lelli
2012-05-23 21:42 ` [PATCH 15/15] sched: add sched_dl documentation Juri Lelli
2012-05-25 10:42 ` [RFC][PATCH 00/15] sched: SCHED_DEADLINE v5 Peter Zijlstra
2012-05-25 11:04   ` Thomas Gleixner
2012-05-28  9:06   ` Juri Lelli
2012-05-29 10:07     ` Peter Zijlstra

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=1338285486.26856.16.camel@twins \
    --to=peterz@infradead.org \
    --cc=claudio@evidence.eu.com \
    --cc=darren@dvhart.com \
    --cc=dhaval.giani@gmail.com \
    --cc=fchecconi@gmail.com \
    --cc=fweisbec@gmail.com \
    --cc=harald.gustafsson@ericsson.com \
    --cc=hgu1972@gmail.com \
    --cc=insop.song@ericsson.com \
    --cc=jkacur@redhat.com \
    --cc=johan.eker@ericsson.com \
    --cc=juri.lelli@gmail.com \
    --cc=liming.wang@windriver.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luca.abeni@unitn.it \
    --cc=michael@amarulasolutions.com \
    --cc=mingo@redhat.com \
    --cc=nicola.manica@disi.unitn.it \
    --cc=oleg@redhat.com \
    --cc=p.faure@akatech.ch \
    --cc=paulmck@linux.vnet.ibm.com \
    --cc=raistlin@linux.it \
    --cc=rostedt@goodmis.org \
    --cc=tglx@linutronix.de \
    --cc=tommaso.cucinotta@sssup.it \
    /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.