From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Martin Herrman <martin@tuxserver.dyndns.org>
Cc: linux-8086@vger.kernel.org
Subject: Re: buddy algorithm
Date: 11 Jan 2003 02:41:38 +0000 [thread overview]
Message-ID: <1042252897.32431.25.camel@irongate.swansea.linux.org.uk> (raw)
In-Reply-To: <Pine.LNX.4.44.0301102301320.16753-100000@tuxserver.dyndns.org>
On Fri, 2003-01-10 at 22:16, Martin Herrman wrote:
> pass the course. We heard about the 'buddy algorithm', which assigns
> memory to processes. Now the question is: how does the ELKS project deal
> with it? Does it use the same algorithm as the official linux kernel does?
ELKS draws on v7 and on Minix for its origins. It takes an old v7 unix
type view of kernel dynamic memory allocators (that is -don't do it-),
user space memory is handled by a simple linked list of holes. We have
two entries per process maximum (data and code) so kernel side its just
not worth the clever stuff.
Much of the other ELKS stuff is like this. We have no hash for the
buffer cache because we tend to have about ten buffers cached...
prev parent reply other threads:[~2003-01-11 2:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20030110214652Z266323-22911+21374@vger.kernel.org>
2003-01-10 22:16 ` buddy algorithm Martin Herrman
2003-01-10 22:36 ` Dan Olson
2003-01-10 22:37 ` Harry Kalogirou
2003-01-11 2:41 ` Alan Cox [this message]
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=1042252897.32431.25.camel@irongate.swansea.linux.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=linux-8086@vger.kernel.org \
--cc=martin@tuxserver.dyndns.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