From: "Stephen C. Tweedie" <sct@redhat.com>
To: Rik van Riel <riel@nl.linux.org>
Cc: Andi Kleen <ak@muc.de>, Jeff Garzik <jgarzik@pobox.com>,
linux-mm@kvack.org
Subject: Re: simple slab alloc question
Date: Mon, 11 Oct 1999 23:19:14 +0100 (BST) [thread overview]
Message-ID: <14338.25186.861908.523998@dukat.scot.redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.10.9910112007250.26190-100000@imladris.dummy.home>
Hi,
On Mon, 11 Oct 1999 20:11:38 +0200 (CEST), Rik van Riel
<riel@nl.linux.org> said:
>> Even other major users get their pages from the page allocator
>> directly (inodes, dcache). These used to be (still are?) a major
>> source of fragmentation, because they tend to wire whole pages
>> down even where there is only a single active inode/dentry on it.
> A zone allocator would not help in this case. A zone
> which has only one active inode/dentry on it is just
> as wired down as a normal page.
It would help. The problem is that single wired pages make it
impossible to use the adjacent page for larger allocations such as for
kernel stacks or big network frames. The VM causes the same problem but
to a much lesser extend, as in general we can swap out any VM page given
enough effort. The fragmentation caused by a pinned inode or dcache
page causes unrecoverable fragmentation.
With a zoned allocater, we can keep these two cases in separate zones
and enormously increase our ability to defragment memory by cleaning VM
pages.
--Stephen
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://humbolt.geo.uu.nl/Linux-MM/
prev parent reply other threads:[~1999-10-11 22:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-10-10 22:09 Jeff Garzik
1999-10-11 11:10 ` Andi Kleen
1999-10-11 18:11 ` Rik van Riel
1999-10-11 22:19 ` Stephen C. Tweedie [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=14338.25186.861908.523998@dukat.scot.redhat.com \
--to=sct@redhat.com \
--cc=ak@muc.de \
--cc=jgarzik@pobox.com \
--cc=linux-mm@kvack.org \
--cc=riel@nl.linux.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