public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mike Galbraith <efault@gmx.de>
To: Pedro Larroy <pedro.larroy.lists@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: unfair scheduling with tbb application observed, could it be a kernel issue?
Date: Mon, 06 Aug 2012 17:14:22 +0200	[thread overview]
Message-ID: <1344266062.6853.26.camel@marge.simpson.net> (raw)
In-Reply-To: <1344264419.6853.19.camel@marge.simpson.net>

Ok, with the sched_debug info you sent offline, booting with noautogroup
appended to the kernel command line should fix it up for you.  You've
got autogroup enabled, which creates automagic per session task groups.

-Mike  


      reply	other threads:[~2012-08-06 15:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-06 14:04 unfair scheduling with tbb application observed, could it be a kernel issue? Pedro Larroy
2012-08-06 14:25 ` Mike Galbraith
2012-08-06 14:28   ` Pedro Larroy
2012-08-06 14:38     ` Mike Galbraith
2012-08-06 14:46       ` Mike Galbraith
2012-08-06 15:14         ` Mike Galbraith [this message]

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=1344266062.6853.26.camel@marge.simpson.net \
    --to=efault@gmx.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pedro.larroy.lists@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox