From: Andrew Hamilton-Wright andrewhw@uoguelph.ca
Subject: Graphics issues
Date: Sun, 19 Nov 1995 14:23:31 -0500 [thread overview]
Message-ID: <19951119192331.8B9g8TXUNv3nVMVp1uGjVBqQIgZxRSgIhbc1mfh1Oks@z> (raw)
John Carmack (johnc@idnewt.idsoftware.COM) wrote:
>Interactive priority scheduling would be an interesting thing to =
[ deletia ]
>compute bound. A compile running in the background should only =
>get cycles when all interactive applications are blocked on user =
>devices. Perhapse processes could be classified "compute bound" =
>if they last blocked on a non-user IO device, and "interactive" if =
>they last blocked on mouse/keyboard. If an interactive process =
>goes it's full (generous) timeslice without blocking again, =
>reclassify it until it again hits a user device.
The danger here is to forget that the processes associated with the
terminal may not be the only ones of importance on the machine.
There is a lot of good in plan9 for its ability to handle
processes dealing with either remote or no, terminal in a 'fair'
way.
While game handling is important (!) -- we still want to be able
to handle large computational 'compiler type' sequences in the
background; and have them actually get a fair chunk of the CPU.
--
andrew@snowhite.cis.uoguelph.ca andrewhw@uoguelph.ca
next reply other threads:[~1995-11-19 19:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
1995-11-19 19:23 Andrew [this message]
-- strict thread matches above, loose matches on Subject: below --
1995-11-30 16:03 Al
1995-11-19 15:31 Dan
1995-11-17 11:05 John
1995-11-16 17:39 rob
1995-11-14 12:24 dhog
1995-11-14 0:48 John
1995-11-12 12:28 John
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=19951119192331.8B9g8TXUNv3nVMVp1uGjVBqQIgZxRSgIhbc1mfh1Oks@z \
--to=9fans@9fans.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;
as well as URLs for NNTP newsgroup(s).