From: Jeff Sipek <jeffpc@optonline.net>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: Timothy Miller <miller@techsource.com>
Subject: Fwd: Re: Use of AI for process scheduling
Date: Mon, 08 Sep 2003 19:44:04 -0400 [thread overview]
Message-ID: <200309081944.11736.jeffpc@optonline.net> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Monday 08 September 2003 18:56, you wrote:
> Well, we have this to deal with: Someone is exercising the scheduler
> and notices some kind of misscheduling which causes the system to crawl.
>
> How are they going to get to the /proc and /sys directories to do much
> of anything? The system is completely unresponsive. Furthermore, even
> if the system IS responsive, we need some way to for the user to hit a
> key and freeze the current state for examination. Some slow-downs last
> only seconds, but we need to be able to catch them.
Agreed.
> You talk about weights. Would the linux community be willing to put a
> neural net into the kernel? I'm sure we could optimize it to not take a
> lot of processing overhead, but it's an "unknown". It would be scary to
> some people to be unable to disect the actual workings of it and have no
> way of determining corner-case behavior from examining code. But if we
> have, say, only a 2-layer neural net, we might still be able to
> reverse-engineer it.
I meant weights in a more general way - variables in calculations is more
appropriate. Neural nets can do a lot of interesting things, but they really
need optimization. If we were to use them, we should make it a config option
in the kernel (nnet or standard scheduler.)
Jeff.
- --
Trust me, you don't want me doing _anything_ first thing in the morning.
- Linus Torvalds
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
iD8DBQE/XRRHwFP0+seVj/4RAs3KAJ9IISM5bALaOTCJtSWxPDlHxOGVEwCfedgD
bCPO9/Mf1dtmA4zVgGP2Tcc=
=vrNw
-----END PGP SIGNATURE-----
reply other threads:[~2003-09-08 23:44 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200309081944.11736.jeffpc@optonline.net \
--to=jeffpc@optonline.net \
--cc=linux-kernel@vger.kernel.org \
--cc=miller@techsource.com \
/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
all inboxes | Powered by JetHome®