From: Nick Piggin <piggin@cyberone.com.au>
To: Jamie Lokier <jamie@shareable.org>
Cc: Piet Delaney <piet@www.piet.net>,
George Anzinger <george@mvista.com>,
Clayton Weaver <cgweav@email.com>,
linux-kernel@vger.kernel.org
Subject: Re: Circular Convolution scheduler
Date: Tue, 14 Oct 2003 20:06:43 +1000 [thread overview]
Message-ID: <3F8BCAB3.2070609@cyberone.com.au> (raw)
In-Reply-To: <20031014094655.GC24812@mail.shareable.org>
Jamie Lokier wrote:
>Piet Delaney wrote:
>
>>circular convolution is used with the Fast Fourier Transform.
>>The frequency data goes from -N/2 ...0 ,,,, +N/2,
>>multiplying in the frequency domain is the same as
>>convolving in the time or space domain. The result of multiplying
>>a time series by say a filter is the same as convolving it
>>with the FFT of the filter. Both domains wrap around with the
>>FFT, so the normal convolution associated with the Fourier
>>transform is replace with the circular convolution.
>>
>>Many prediction algorithms are based on digital signal processing.
>>The Kalman filter for example was used by Harvey for forecasting
>>financial markets. The kernel likely has lots of time series that
>>could be used for system identification for predicting how to best
>>use system resources.
>>
>
>Ok, but what is "circular convolution scheduling"?
>
>
I don't know anything about it, but I don't see what exactly you'd be
trying to predict: the kernel's scheduler _dictates_ scheduling behaviour,
obviously. Also, "best use of system resources" wrt scheduling is a big
ask considering there isn't one ideal scheduling pattern for all but the
most trivial loads, even on a single processor computer (fairness, latency,
priority, thoughput, etc). Its difficult to even say one pattern is better
than another.
next prev parent reply other threads:[~2003-10-14 10:22 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
2003-10-14 8:37 ` Piet Delaney
2003-10-14 9:46 ` Jamie Lokier
2003-10-14 10:06 ` Nick Piggin [this message]
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=3F8BCAB3.2070609@cyberone.com.au \
--to=piggin@cyberone.com.au \
--cc=cgweav@email.com \
--cc=george@mvista.com \
--cc=jamie@shareable.org \
--cc=linux-kernel@vger.kernel.org \
--cc=piet@www.piet.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