public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Timothy Miller <miller@techsource.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Use of AI for process scheduling
Date: Mon, 08 Sep 2003 14:57:47 -0400	[thread overview]
Message-ID: <3F5CD12B.2060108@techsource.com> (raw)

I just got back from vacation and have 3278 list messages to sift 
through.  (Yay.)  I wouldn't be surprised, therefore, if others were 
already discussing this, but I've been thinking of some ideas over the 
past week that we may be helpful for the advancement of intelligent 
process scheduling.

To begin with, let's consider the parts of an intelligent system:

1) Inputs (ie. properties and behaviors of processes)
2) Heuristics
3) Outputs (ie. dynamic priorities, etc.)

Up to this point, the interactive scheduler has been designed in a very 
expert-system-like manner.  Human experts observe behaviors and define 
heuristics.  Ultimately, we do want a solid set of heuristics that are 
coded in C, and that's what the current development process has been 
working directly toward.

The progress has been slow, and there have been a lot of false starts 
and tangents which have been discarded.  This is all how development 
works, and it's important to explore all possibilities.  But what I 
would like to propose is that we work on a way to accelerate that 
process, and that is to make use of machine learning.  We move from 
expert systems to artificial intelligence, because the heuristics are 
determined by the machine and are therefore dynamic.

Basically, we need to write and install into the kernel an AI engine 
which uses user feedback about the "feel" of the system to adjust 
heuristics dynamically.  For instance, if the user sees that the system 
is misbehaving, they can pause the system in the kernel debugger, 
examine process priorities, and indicate what "outputs" from the AI 
engine are wrong.  It then learns from that.  Heuristics can be tweaked 
until things run as desired.  At that point, scheduler developers trade 
emails in the AI heuristic language.

Obviously, this AI engine will be slow and add a huge amount of 
processing overhead.  The idea is to determine what the heuristics are, 
and then to release a kernel, recode the heuristics in C.


             reply	other threads:[~2003-09-08 18:36 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-08 18:57 Timothy Miller [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-09-08 19:28 Use of AI for process scheduling Timothy Miller
2003-09-08 21:55 ` Jeff Sipek
2003-09-08 22:56   ` Timothy Miller
2003-09-08 22:28 ` Felipe Alfaro Solana
2003-09-08 23:01   ` Timothy Miller
2003-09-08 23:57     ` David Lang
2003-09-09  0:34       ` Timothy Miller
2003-09-09  1:40         ` Robin Rosenberg
2003-09-09  1:57           ` Robin Rosenberg
2003-09-09 15:16           ` Timothy Miller
2003-09-09 15:14             ` Robin Rosenberg
2003-09-08 22:57 ` William Lee Irwin III
2003-09-08 23:06   ` Mike Fedyk
2003-09-08 23:14     ` William Lee Irwin III
2003-09-09  0:22       ` Timothy Miller
2003-09-09  1:05         ` William Lee Irwin III
2003-09-09 15:08           ` Timothy Miller
2003-09-09 17:47             ` William Lee Irwin III
2003-09-09  0:06     ` Timothy Miller
2003-09-09  1:19       ` Rick Lindsley
2003-09-09 15:11         ` Timothy Miller
2003-09-09 19:05 John Yau

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=3F5CD12B.2060108@techsource.com \
    --to=miller@techsource.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