From: Michael Buesch <mbuesch@freenet.de>
To: Chris Friesen <cfriesen@nortelnetworks.com>
Cc: Con Kolivas <kernel@kolivas.org>,
Timothy Miller <miller@techsource.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Nice 19 process still gets some CPU
Date: Mon, 28 Jun 2004 18:23:59 +0200 [thread overview]
Message-ID: <200406281824.01836.mbuesch@freenet.de> (raw)
In-Reply-To: <40E0449F.5050104@nortelnetworks.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Quoting Chris Friesen <cfriesen@nortelnetworks.com>:
> Timothy Miller wrote:
> >
> >
> > Con Kolivas wrote:
> >
> > >
> > > It definitely should _not_ starve. That is the unixy way of doing
> > > things. Everything must go forward. Around 5% cpu for nice 19 sounds
> > > just right. If you want scheduling only when there's spare cpu cycles
> > > you need a sched batch(idle) implementation.
> > >
> > >
> >
> > Well, since I can't rewrite the app, I can't make it sched batch. Nice
> > values are an easy thing to get at for anything that's running.
>
> Sure you can. You can set the scheduler policy on any process in the system,
> while its running.
>
> int sched_setscheduler(pid_t pid, int policy, const struct sched_param *p);
>
> Takes about two minutes to write an equivalent to "nice" to set scheduler
> policies and priorities.
Sounds cool. I was searching this syscall for a long time, now. :)
But batch scheduling is available in -ck only, so this works only
with -ck kernels. Correct?
> Chris
- --
Regards Michael Buesch [ http://www.tuxsoft.de.vu ]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
iD8DBQFA4EYfFGK1OIvVOP4RAogAAKCQ8oYHshIKPXYNAVptHh1QJRRfywCfX8Cg
GxzK64XtYdtnJLReOMrzR3o=
=ithN
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2004-06-28 16:26 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-28 15:14 Nice 19 process still gets some CPU Timothy Miller
2004-06-28 15:04 ` Con Kolivas
2004-06-28 15:41 ` Timothy Miller
2004-06-28 15:24 ` Con Kolivas
2004-06-28 15:42 ` Richard B. Johnson
2004-06-28 15:47 ` Con Kolivas
2004-06-28 15:48 ` Kalin KOZHUHAROV
2004-06-28 15:51 ` Con Kolivas
2004-06-28 16:17 ` Chris Friesen
2004-06-28 16:23 ` Michael Buesch [this message]
2004-06-28 16:36 ` Chris Friesen
2004-06-28 21:15 ` Con Kolivas
2004-06-29 16:56 ` Kurt Garloff
2004-06-28 23:38 ` Peter Williams
2004-06-29 6:26 ` Benoît Dejean
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=200406281824.01836.mbuesch@freenet.de \
--to=mbuesch@freenet.de \
--cc=cfriesen@nortelnetworks.com \
--cc=kernel@kolivas.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miller@techsource.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 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.