From: Ed Tomlinson <tomlins@cam.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Robert Love <rml@tech9.net>
Subject: Re: [PATCH,RFC] fix o(1) handling of threads
Date: Fri, 3 Jan 2003 07:50:26 -0500 [thread overview]
Message-ID: <200301030750.27040.tomlins@cam.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0301030120410.2226-100000@localhost.localdomain>
On January 2, 2003 07:22 pm, Ingo Molnar wrote:
> On Wed, 1 Jan 2003, Ed Tomlinson wrote:
> > Here is the scheduler-tunables patch updated to include USER_PENALTY and
> > THREAD_PENANTY. This on top of ptg_B0.
>
> there's no way we'll make the scheduler internal constants tunable in such
> a wide range. Such a patch has been submitted a couple of months ago
> already. I do use something like that to test tunings, but it's definitely
> not something we want to make tunable directly in the stock kernel.
Nor would I advocate doing so. I added two 'constants' I wanted to
be able to test them so I updated Robert's patch... Two questions
for you.
1. Do you have any comments/suggestsion on the ptg_B0 patch?
2. I have been playing with using user and thread penalties together.
- they often interact badly. Using just one works very well. This
can be fixed - but gets messy. Alternately, I am thinking about
implementing per user policies. ie.
a. govern thread groups
b. govern all threads, ignoring groups, for a user
c. govern processes for a user
This can be done cleanly. Would something along the lines of sys_nice
be the way to implement the kernel side of the user interface to this?
TIA,
Ed Tomlinson
next prev parent reply other threads:[~2003-01-03 12:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-30 21:45 [PATCH,RFC] fix o(1) handling of threads Ed Tomlinson
2002-12-30 22:12 ` William Lee Irwin III
2002-12-30 22:50 ` Alan Cox
2002-12-30 22:32 ` Ed Tomlinson
2002-12-31 14:33 ` Ed Tomlinson
2003-01-01 13:02 ` Ed Tomlinson
2003-01-03 0:22 ` Ingo Molnar
2003-01-03 12:50 ` Ed Tomlinson [this message]
2002-12-30 23:00 ` David Schwartz
2002-12-31 4:03 ` Ed Tomlinson
2002-12-31 4:45 ` Rik van Riel
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=200301030750.27040.tomlins@cam.org \
--to=tomlins@cam.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rml@tech9.net \
/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