On Fri, Nov 23, 2001 at 10:23:38AM +0100, Daniel Phillips wrote:
> First, what are functional requirements? A quick survey of the web shows
> that most of us haven't got a clue. You can find some basic definitions here:
>
> Our vm shall:
>
[ ... ]
- The vm should honour admin-provided priorities in regard to
relative importance between apps. In actual code, something
like the "nice value" for vm behaviour.
- Be good at detecting streaming IO so that, for example, an mp3
or video player will not throw out more memory than necesary.
Perhaps give an special admin-provided flag to the programs
which should get honoured as streamers in case auto-detection
fails.
- Be sure to grant enough memory to streaming IO so that they
can work as intended (read data, process, perhaps write,
all sequentially). Maybe an admin-provided low-watermark
for an initial implementation.
> --
> Daniel
> --
[OT: daniel, what happens with tux2? i've got some working userspace code
(block {alloc,free}, automatic recursive branching, delayed allocation)
and I recall you had some code also... any light?]
--
every day, every year
you have to work -- you have to study -- you have to scene
wind^network - a network release in MMI
--
Kernelnewbies: Help each other learn about the Linux kernel.
Archive: http://mail.nl.linux.org/kernelnewbies/
IRC Channel: irc.openprojects.net / #kernelnewbies
Web Page: http://www.kernelnewbies.org/
