All of lore.kernel.org
 help / color / mirror / Atom feed
From: michi1@michaelblizek.twilightparadox.com (michi1 at michaelblizek.twilightparadox.com)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Why the niceness is not always taken into account ?
Date: Tue, 16 Apr 2013 17:58:01 +0200	[thread overview]
Message-ID: <20130416155800.GA2245@grml> (raw)
In-Reply-To: <1740ed2d02fbaad883418ad506ae4ec0@uvsq.fr>

Hi!

On 10:35 Tue 16 Apr     , Alexandre Laurent wrote:
...
> I am running the same test, but connecting twice on the remote machine
> (one connection by test instance). I am using exactly the same commands
> than during the others experiments. But, by using two SSH instances, 
> the
> niceness will not be taken into account. The CPU will be shared equally
> between both instances even if htop is showing a niceness of 19 / -20
> for the low priority program and the privileged program respectively.

Can you check whether you have CONFIG_SCHED_AUTOGROUP enabled? If it is
enabled, try running the test again with this option turned off.

	-Michi
-- 
programing a layer 3+4 network protocol for mesh networks
see http://michaelblizek.twilightparadox.com

      parent reply	other threads:[~2013-04-16 15:58 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-16  8:35 Why the niceness is not always taken into account ? Alexandre Laurent
2013-04-16 11:03 ` Kristof Provost
2013-04-16 15:38   ` Alexandre Laurent
2013-04-16 17:59     ` Kristof Provost
2013-04-18 14:57       ` Alexandre Laurent
2013-04-18 15:32         ` Valdis.Kletnieks at vt.edu
2013-04-18 15:56           ` Alexandre Laurent
2013-04-18 17:30             ` Valdis.Kletnieks at vt.edu
2013-04-19 12:20               ` Alexandre Laurent
2013-04-16 15:58 ` michi1 at michaelblizek.twilightparadox.com [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=20130416155800.GA2245@grml \
    --to=michi1@michaelblizek.twilightparadox.com \
    --cc=kernelnewbies@lists.kernelnewbies.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 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.