public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mike Galbraith <efault@gmx.de>
To: Ani <asinha@zeugmasystems.com>
Cc: Lucas De Marchi <lucas.de.marchi@gmail.com>,
	linux-kernel@vger.kernel.org,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Ingo Molnar <mingo@elte.hu>
Subject: Re: question on sched-rt group allocation cap: sched_rt_runtime_us
Date: Sun, 06 Sep 2009 12:18:09 +0200	[thread overview]
Message-ID: <1252232289.29247.11.camel@marge.simson.net> (raw)
In-Reply-To: <1252218779.6126.17.camel@marge.simson.net>

On Sun, 2009-09-06 at 08:32 +0200, Mike Galbraith wrote:
> On Sat, 2009-09-05 at 19:32 -0700, Ani wrote: 
> > On Sep 5, 3:50 pm, Lucas De Marchi <lucas.de.mar...@gmail.com> wrote:
> > >
> > > Indeed. I've tested this same test program in a single core machine and it
> > > produces the expected behavior:
> > >
> > > rt_runtime_us / rt_period_us     % loops executed in SCHED_OTHER
> > > 95%                              4.48%
> > > 60%                              54.84%
> > > 50%                              86.03%
> > > 40%                              OTHER completed first
> > >
> > 
> > Hmm. This does seem to indicate that there is some kind of
> > relationship with SMP. So I wonder whether there is a way to turn this
> > 'RT bandwidth accumulation' heuristic off.
> 
> No there isn't, but maybe there should be, since this isn't the first
> time it's come up.  One pro argument is that pinned tasks are thoroughly
> screwed when an RT hog lands on their runqueue.  On the con side, the
> whole RT bandwidth restriction thing is intended (AFAIK) to allow an
> admin to regain control should RT app go insane, which the default 5%
> aggregate accomplishes just fine.
> 
> Dunno.  Fly or die little patchlet (toss). 

btw, a _kinda sorta_ pro is that it can prevent IO lockups like the
below.  Seems kjournald can end up depending on kblockd/3, which ain't
going anywhere with that 100% RT hog in the way, so the whole box is
fairly hosed.  (much better would be to wake some other kblockd)

top - 12:01:49 up 56 min, 20 users,  load average: 8.01, 4.96, 2.39
Tasks: 304 total,   4 running, 300 sleeping,   0 stopped,   0 zombie
Cpu(s): 25.8%us,  0.3%sy,  0.0%ni,  0.0%id, 73.7%wa,  0.3%hi,  0.0%si,  0.0%st

  PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  P COMMAND
13897 root      -2   0  7920  592  484 R  100  0.0   1:13.43 3 xx
12716 root      20   0  8868 1328  860 R    1  0.0   0:01.44 0 top
   14 root      15  -5     0    0    0 R    0  0.0   0:00.02 3 events/3
   94 root      15  -5     0    0    0 R    0  0.0   0:00.00 3 kblockd/3
 1212 root      15  -5     0    0    0 D    0  0.0   0:00.04 2 kjournald
14393 root      20   0  9848 2296  756 D    0  0.1   0:00.01 0 make
14404 root      20   0 38012  25m 5552 D    0  0.8   0:00.21 1 cc1
14405 root      20   0 20220 8852 2388 D    0  0.3   0:00.02 1 as
14437 root      20   0 24132  10m 2680 D    0  0.3   0:00.06 2 cc1
14448 root      20   0 18324 1724 1240 D    0  0.1   0:00.00 2 cc1
14452 root      20   0 12540  792  656 D    0  0.0   0:00.00 2 mv



  reply	other threads:[~2009-09-06 10:18 UTC|newest]

Thread overview: 56+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <dgRNo-3uc-5@gated-at.bofh.it>
     [not found] ` <dhb9j-1hp-5@gated-at.bofh.it>
     [not found]   ` <dhcf5-263-13@gated-at.bofh.it>
2009-09-06  2:32     ` question on sched-rt group allocation cap: sched_rt_runtime_us Ani
2009-09-06  6:32       ` Mike Galbraith
2009-09-06 10:18         ` Mike Galbraith [this message]
     [not found]           ` <DDFD17CC94A9BD49A82147DDF7D545C54DC482@exchange.ZeugmaSystems.local>
2009-09-06 15:09             ` Mike Galbraith
2009-09-07  0:41               ` Anirban Sinha
     [not found]               ` <1252311463.7586.26.camel@marge.simson.net>
2009-09-07 11:06                 ` [rfc] lru_add_drain_all() vs isolation Peter Zijlstra
2009-09-07 13:35                   ` Oleg Nesterov
2009-09-07 13:53                     ` Peter Zijlstra
2009-09-07 14:18                       ` Oleg Nesterov
2009-09-07 14:25                         ` Peter Zijlstra
2009-09-07 23:56                   ` KOSAKI Motohiro
2009-09-08  8:20                     ` Peter Zijlstra
2009-09-08 10:06                       ` KOSAKI Motohiro
2009-09-08 10:20                         ` Peter Zijlstra
2009-09-08 11:41                           ` KOSAKI Motohiro
2009-09-08 12:05                             ` Peter Zijlstra
2009-09-08 14:03                               ` Christoph Lameter
2009-09-08 14:20                                 ` Peter Zijlstra
2009-09-08 15:22                                   ` Christoph Lameter
2009-09-08 15:27                                     ` Peter Zijlstra
2009-09-08 15:32                                     ` Christoph Lameter
2009-09-09  4:27                                       ` KOSAKI Motohiro
2009-09-09 14:08                                         ` Christoph Lameter
2009-09-09 23:43                                           ` KOSAKI Motohiro
2009-09-10 18:03                                             ` Christoph Lameter
2009-09-09 15:39                                         ` Minchan Kim
2009-09-09 16:18                                           ` Lee Schermerhorn
2009-09-09 16:46                                             ` Minchan Kim
2009-09-09 23:58                                           ` KOSAKI Motohiro
2009-09-10  1:00                                             ` Minchan Kim
2009-09-10  1:15                                               ` KOSAKI Motohiro
2009-09-10  1:23                                                 ` Minchan Kim
2009-09-09  2:06                               ` KOSAKI Motohiro
     [not found]         ` <DDFD17CC94A9BD49A82147DDF7D545C54DC483@exchange.ZeugmaSystems.local>
     [not found]           ` <DDFD17CC94A9BD49A82147DDF7D545C54DC485@exchange.ZeugmaSystems.local>
2009-09-07  0:28             ` question on sched-rt group allocation cap: sched_rt_runtime_us Anirban Sinha
2009-09-07  6:54           ` Mike Galbraith
     [not found]             ` <DDFD17CC94A9BD49A82147DDF7D545C54DC489@exchange.ZeugmaSystems.local>
2009-09-08  7:10               ` Anirban Sinha
2009-09-08  9:26                 ` Mike Galbraith
2009-09-07  7:59         ` Peter Zijlstra
2009-09-07  8:24           ` Mike Galbraith
     [not found]           ` <DDFD17CC94A9BD49A82147DDF7D545C54DC487@exchange.ZeugmaSystems.local>
2009-09-08  7:08             ` Anirban Sinha
2009-09-08  8:42               ` Peter Zijlstra
2009-09-08 14:41                 ` Anirban Sinha
     [not found]         ` <DDFD17CC94A9BD49A82147DDF7D545C54DC48B@exchange.ZeugmaSystems.local>
2009-09-08 17:41           ` Anirban Sinha
2009-09-08 19:06             ` Mike Galbraith
2009-09-08 19:34               ` Anirban Sinha
2009-09-09  4:10                 ` Mike Galbraith
2009-09-05 17:13 Anirban Sinha
     [not found] <Acotv57vW6nkRxQOQLuBf8W5yfJIlwAAtMAw>
2009-09-05  0:55 ` Anirban Sinha
2009-09-05 17:43   ` Lucas De Marchi
2009-09-05 20:40   ` Fabio Checconi
2009-09-05 22:40     ` Lucas De Marchi
     [not found]     ` <DDFD17CC94A9BD49A82147DDF7D545C54DC481@exchange.ZeugmaSystems.local>
2009-09-06  0:47       ` Anirban Sinha
2009-09-06 13:21         ` Fabio Checconi
     [not found]           ` <DDFD17CC94A9BD49A82147DDF7D545C54DC484@exchange.ZeugmaSystems.local>
2009-09-07  0:26             ` Anirban Sinha
2009-09-08 17:26           ` Anirban Sinha
2009-09-08 21:37             ` Anirban Sinha

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=1252232289.29247.11.camel@marge.simson.net \
    --to=efault@gmx.de \
    --cc=a.p.zijlstra@chello.nl \
    --cc=asinha@zeugmasystems.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lucas.de.marchi@gmail.com \
    --cc=mingo@elte.hu \
    /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