From: Andrea Arcangeli <andrea@suse.de>
To: Timur Tabi <ttabi@interactivesi.com>
Cc: Linux MM mailing list <linux-mm@kvack.org>
Subject: Re: Why is the free_list not null-terminated?
Date: Tue, 27 Jun 2000 03:27:15 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.21.0006270323540.2591-100000@inspiron.random> (raw)
In-Reply-To: <20000623193609Z131187-21004+54@kanga.kvack.org>
On Fri, 23 Jun 2000, Timur Tabi wrote:
>Question #1: Does this mean that there are no free zones of Order 2 (16KB)?
It means there are no free contigous chunks of memory of order 2 in such
zone.
>Question #2: Why are prev and next not set to null? Why do they point
because of linux/include/list.h ;), more seriously that avoids a path in
the list insert/remove code but the head of the list is double size (and
this is not an issue except for large hashtables).
(btw give a try also to SYSRQ+M if you are interested about similar info)
Andrea
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux.eu.org/Linux-MM/
next prev parent reply other threads:[~2000-06-27 1:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-23 19:28 Timur Tabi
2000-06-27 1:27 ` Andrea Arcangeli [this message]
2000-06-27 15:39 ` Timur Tabi
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=Pine.LNX.4.21.0006270323540.2591-100000@inspiron.random \
--to=andrea@suse.de \
--cc=linux-mm@kvack.org \
--cc=ttabi@interactivesi.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