All of lore.kernel.org
 help / color / mirror / Atom feed
From: Artur Skawina <art_k@o2.pl>
To: Jeffrey Hundstad <jeffrey.hundstad@mnsu.edu>
Cc: Con Kolivas <kernel@kolivas.org>,
	linux list <linux-kernel@vger.kernel.org>,
	ck list <ck@vds.kolivas.org>, Ingo Molnar <mingo@elte.hu>
Subject: Re: [PATCH] sched: rsdl improvements
Date: Thu, 22 Mar 2007 01:15:24 +0100	[thread overview]
Message-ID: <4601CA9C.6050708@o2.pl> (raw)
In-Reply-To: <4601C44B.9060705@mnsu.edu>

Jeffrey Hundstad wrote:
>> I'm not sure this is going in the right direction... I'm writing
>> this while compiling a kernel w/ "nice -20 make -j2" and X is almost
>>   
> Did you mean "nice -20"?  If so, that should have slowed X quite a bit. 
> Try "nice 19" instead.

i did try "nice --20" too :) Resulted in long X stalls, but i don't
think that's a reasonable load so I did not mention it.
"nice -20 cmd" runs cmd at nice==19.

Usage: nice [OPTION] [COMMAND [ARG]...]
Run COMMAND with an adjusted niceness, which affects process scheduling.
With no COMMAND, print the current niceness.  Nicenesses range from
-20 (most favorable scheduling) to 19 (least favorable).

  -n, --adjustment=N   add integer N to the niceness (default 10)

  reply	other threads:[~2007-03-22  0:15 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-21 17:29 [PATCH] sched: rsdl improvements Con Kolivas
2007-03-21 23:27 ` Artur Skawina
2007-03-21 23:48   ` Jeffrey Hundstad
2007-03-22  0:15     ` Artur Skawina [this message]
2007-03-22  0:24     ` Con Kolivas
2007-03-22  0:52       ` Con Kolivas
2007-03-22  2:04         ` [PATCH] sched: rsdl check for niced tasks lowering prio level Con Kolivas
2007-03-22 13:34           ` Artur Skawina
2007-03-21 23:36 ` [PATCH] sched: rsdl improvements Andrew Morton
2007-03-22  5:03   ` Con Kolivas
2007-03-22 14:46 ` Christian

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=4601CA9C.6050708@o2.pl \
    --to=art_k@o2.pl \
    --cc=ck@vds.kolivas.org \
    --cc=jeffrey.hundstad@mnsu.edu \
    --cc=kernel@kolivas.org \
    --cc=linux-kernel@vger.kernel.org \
    --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 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.