From: jmk@plan9.bell-labs.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] xspanalloc?
Date: Mon, 3 Jan 2005 23:15:03 -0500 [thread overview]
Message-ID: <44e5ecec9c314a4df263ce79e8e8c6ee@plan9.bell-labs.com> (raw)
This is the comment used to be at the beginning
of the alloc code:
/*
* Plan 9 has two kernel allocators, the x... routines provide a first
* fit hole allocator which should be used for permanent or large structures.
* Routines are provided to allocate aligned memory which does not cross
* arbitrary 2^n boundaries. A second allocator malloc, smalloc, free is
* a 2n bucket allocator which steals from the x routines. This should
* be used for small frequently used structures.
*/
That was before the 2n bucket allocator was replaced by the pool allocator.
This comment used to be before the the xspanalloc function:
/*
* NB. spanalloc memory will cause a panic if free'd
*/
Ron Minnich and Andrey Mirtchovski recently found a bug in the xalloc
code introduced during the conversion to the pool allocator which caused
bad things to happen.
next reply other threads:[~2005-01-04 4:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-04 4:15 jmk [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-01-03 22:00 [9fans] usb audio devices list on supported pc hardware wiki page Axel Belinfante
2005-01-04 1:21 ` [9fans] xspanalloc? Tim Newsham
2005-01-04 1:50 ` Russ Cox
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=44e5ecec9c314a4df263ce79e8e8c6ee@plan9.bell-labs.com \
--to=jmk@plan9.bell-labs.com \
--cc=9fans@cse.psu.edu \
/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).