From: "David S. Miller" <davem@redhat.com>
To: torvalds@transmeta.com
Cc: hugh@veritas.com, Frank.dekervel@student.kuleuven.ac.Be,
andrea@suse.de, marcelo@conectiva.com.br,
linux-kernel@vger.kernel.org
Subject: Re: need help interpreting 'free' output.
Date: Tue, 30 Oct 2001 12:47:40 -0800 (PST) [thread overview]
Message-ID: <20011030.124740.77059418.davem@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0110300839360.8603-200000@penguin.transmeta.com>
In-Reply-To: <Pine.LNX.4.21.0110301557560.1229-100000@localhost.localdomain> <Pine.LNX.4.33.0110300839360.8603-200000@penguin.transmeta.com>
From: Linus Torvalds <torvalds@transmeta.com>
Date: Tue, 30 Oct 2001 08:52:58 -0800 (PST)
My _preferred_ approach would actually be to move the slab pages to the
LRU list too, and have a special "slab" address space (we don't need to
actually hash them, we just make page->mapping point to it), and have the
cache shrink be done naturally as part of writepage().
This is a cool idea.
So when a SLAB block gets allocated from, we "reference" the
underlying page?
Franks a lot,
David S. Miller
davem@redhat.com
next prev parent reply other threads:[~2001-10-30 20:47 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-30 11:32 need help interpreting 'free' output Frank Dekervel
2001-10-30 11:46 ` Mike Fedyk
2001-10-30 14:02 ` Frank Dekervel
2001-10-30 16:07 ` Hugh Dickins
2001-10-30 16:51 ` Andrea Arcangeli
2001-10-30 16:52 ` Linus Torvalds
2001-10-30 17:06 ` Andrea Arcangeli
2001-10-30 17:28 ` Linus Torvalds
2001-10-30 17:39 ` Andrea Arcangeli
2001-10-30 17:53 ` Linus Torvalds
2001-10-30 18:16 ` Andrea Arcangeli
2001-10-30 18:28 ` Linus Torvalds
2001-10-30 18:58 ` Andrea Arcangeli
2001-10-30 19:21 ` Linus Torvalds
2001-10-30 20:05 ` Andrea Arcangeli
2001-10-30 20:25 ` Linus Torvalds
2001-10-30 18:05 ` Eric W. Biederman
2001-10-30 20:47 ` David S. Miller [this message]
2001-10-30 18:11 ` Frank Dekervel
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=20011030.124740.77059418.davem@redhat.com \
--to=davem@redhat.com \
--cc=Frank.dekervel@student.kuleuven.ac.Be \
--cc=andrea@suse.de \
--cc=hugh@veritas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
--cc=torvalds@transmeta.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.