public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: George Anzinger <george@mvista.com>
To: Clayton Weaver <cgweav@email.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Circular Convolution scheduler
Date: Tue, 07 Oct 2003 15:19:50 -0700	[thread overview]
Message-ID: <3F833C06.7000802@mvista.com> (raw)
In-Reply-To: <20031006161733.24441.qmail@email.com>

Ok, I'll admit my ignorance.  What is circular convolution?  Where can 
I learn more?

-g

Clayton Weaver wrote:
> Though the mechanism is doubtless familiar
> to signal processing and graphics implementers,
> it's probably not thought of much in a
> process scheduling contex (although there was
> the Evolution Scheduler of a few years ago,
> whose implementer may have had something like
> circular convolution in mind). It just seems to me
> (intuition) that the concept of what circular convolution does is akin to what we've been
> feeling around for with these ad hoc heuristic
> tweaks to the scheduler to adjust for interactivity
> and batch behavior, searching for an incremental self-adjusting mechanism that favors interactivity
> on demand.
> 
> I've never implemented a circular convolver in
> any context, so I was wondering if anyone who
> has thinks scheduler prioritization would be
> simpler if implemented directly as a circular convolution.
> 
> (If nothing else, it seems to me that the abstract model of what the schedule prioritizer is doing
> would be more coherent than it is with ad hoc
> code. This perhaps reduces the risk of unexpected side-effects of incremental tweaks to the scheduler. The behavior of an optimizer that implements
> an integer approximation of a known mathematical transform when you change its inputs is fairly predictable.)
> 
> Regards,
> 
> Clayton Weaver
> <mailto: cgweav@email.com>
> 
> 

-- 
George Anzinger   george@mvista.com
High-res-timers:  http://sourceforge.net/projects/high-res-timers/
Preemption patch: http://www.kernel.org/pub/linux/kernel/people/rml


  reply	other threads:[~2003-10-07 22:20 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-06 16:17 Circular Convolution scheduler Clayton Weaver
2003-10-07 22:19 ` George Anzinger [this message]
2003-10-14  8:37   ` Piet Delaney
2003-10-14  9:46     ` Jamie Lokier
2003-10-14 10:06       ` Nick Piggin
2003-10-14 10:18         ` Jamie Lokier
2003-10-14 10:28           ` Nick Piggin
2003-10-16  8:34             ` Piet Delaney
2003-10-16  9:03               ` Nick Piggin
2003-10-21 18:09         ` bill davidsen
  -- strict thread matches above, loose matches on Subject: below --
2003-10-07 20:47 Clayton Weaver
2003-10-16  1:51 Clayton Weaver
2003-10-21 18:44 ` bill davidsen
2003-10-21 20:15   ` Richard B. Johnson
2003-10-21 20:54     ` bill davidsen
2003-10-19  8:50 Clayton Weaver
2003-10-21 18:51 ` bill davidsen

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=3F833C06.7000802@mvista.com \
    --to=george@mvista.com \
    --cc=cgweav@email.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