public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ed Tomlinson <tomlins@cam.org>
To: David Schwartz <davids@webmaster.com>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH,RFC] fix o(1) handling of threads
Date: Mon, 30 Dec 2002 23:03:50 -0500	[thread overview]
Message-ID: <200212302303.50119.tomlins@cam.org> (raw)
In-Reply-To: <20021230230030.AAA103@shell.webmaster.com@whenever>

On December 30, 2002 06:00 pm, David Schwartz wrote:
> On Mon, 30 Dec 2002 16:45:50 -0500, Ed Tomlinson wrote:
> >What this patches does is recognise threads as process that clone both
> >mm and files.  For these 'threads' it tracks how many are active in a
> >given group.  When many are active it reduces their timeslices as below
>
> 	In general, changes that cause the system to become less efficient as load
> increases are not such a good idea. By reducing timeslices, you increase
> context-switching overhead. So the busier you are, the less efficient you
> get. I think it would be wiser to keep the timeslice the same but assign
> fewer timeslices.

That would be better - I cannot see a way to do it using O(1).  What might
be possible (not sure how) is only to decrease the timeslices IF there are
other tasks being slowed down by the thread group...

Ed


  reply	other threads:[~2002-12-31  3:55 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
2002-12-30 23:00 ` David Schwartz
2002-12-31  4:03   ` Ed Tomlinson [this message]
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=200212302303.50119.tomlins@cam.org \
    --to=tomlins@cam.org \
    --cc=davids@webmaster.com \
    --cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox