From: Max Hailperin <max@gustavus.edu>
To: Con Kolivas <kernel@kolivas.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC] Re: Blender profiling-1 O16.2int
Date: Mon, 18 Aug 2003 07:52:35 -0500 [thread overview]
Message-ID: <200308181252.h7ICqZh8003767@mccormic.mcs.gac.edu> (raw)
In-Reply-To: <20030818110001.6564.64238.Mailman@lists.us.dell.com> (linux-kernel-daily-digest-request@lists.us.dell.com)
From: Con Kolivas <kernel@kolivas.org>
To: Voluspa <voluspa@comhem.se>
Subject: [RFC] Re: Blender profiling-1 O16.2int
Date: Sun, 17 Aug 2003 23:36:42 +1000
Cc: linux kernel mailing list <linux-kernel@vger.kernel.org>,
Mike Galbraith <efault@gmx.de>, Andrew Morton <akpm@osdl.org>,
William Lee Irwin III <wli@holomorphy.com>
... I do have some ideas about how to progress with this (some Mike
has suggested to me previously), but so far most of them involve
some detriment to the interactive performance on other apps. So I'm
appealing to others for ideas.
Comments?
Con
I suggest you put a small limit on the number of times that a task can
be requeued onto the active array before it needs to go to the expired
array. -max
next parent reply other threads:[~2003-08-18 12:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20030818110001.6564.64238.Mailman@lists.us.dell.com>
2003-08-18 12:52 ` Max Hailperin [this message]
2003-08-18 13:05 ` [RFC] Re: Blender profiling-1 O16.2int Con Kolivas
2003-08-18 14:43 ` William Lee Irwin III
2003-08-26 2:54 Kester Maddock
2003-08-26 5:03 ` Con Kolivas
[not found] <20030817003128.04855aed.voluspa@comhem.se>
[not found] ` <200308171142.33131.kernel@kolivas.org>
[not found] ` <20030817073859.51021571.voluspa@comhem.se>
2003-08-17 13:36 ` Con Kolivas
2003-08-17 16:34 ` Con Kolivas
2003-08-18 0:30 ` William Lee Irwin III
2003-08-19 0:14 ` Wes Janzen
2003-08-19 0:28 ` Con Kolivas
2003-08-19 0:37 ` Richard A Nelson
2003-08-19 8:39 ` Rob Landley
2003-08-19 0:31 ` William Lee Irwin III
2003-08-19 0:58 ` Wes Janzen
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=200308181252.h7ICqZh8003767@mccormic.mcs.gac.edu \
--to=max@gustavus.edu \
--cc=kernel@kolivas.org \
--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;
as well as URLs for NNTP newsgroup(s).