From: "Martin J. Bligh" <mbligh@aracnet.com>
To: Amol Kumar Lad <amolk@ishoni.com>, linux-mm@kvack.org
Subject: Re: hot and cold pages
Date: Mon, 10 Feb 2003 21:02:32 -0800 [thread overview]
Message-ID: <74860000.1044939751@[10.10.2.4]> (raw)
In-Reply-To: <1044976347.13957.19.camel@amol.in.ishoni.com>
> I have a small question regarding 'per_cpu_pages' . What is
> significance if maintaining 'hot' pages and 'cold' pages list. Are hot
> pages something to do with L2 cache (on x86) ?
Yup, pages that are thought to be L2 cache hot (or cold, respectively) for
that CPU as a lifo stack.
> After going through code, I found out, any new page allocation (for file
> read)is from cold page list and zero order pages are generally freed to
> hot page list
Right ... if you're going to DMA into it, you might as well use a cold page
- no advantage to using a hot one. Pages newly freed stand a good chance of
being hot, so they're put into the hot list.
M.
--
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-mm.org/
prev parent reply other threads:[~2003-02-11 5:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-11 15:12 Amol Kumar Lad
2003-02-11 5:02 ` Martin J. Bligh [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='74860000.1044939751@[10.10.2.4]' \
--to=mbligh@aracnet.com \
--cc=amolk@ishoni.com \
--cc=linux-mm@kvack.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