From: Andrew Morton <akpm@osdl.org>
To: William Lee Irwin III <wli@holomorphy.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [oom]: [3/4] track wired pages on a per-zone basis
Date: Wed, 23 Jun 2004 15:15:36 -0700 [thread overview]
Message-ID: <20040623151536.023404fc.akpm@osdl.org> (raw)
In-Reply-To: <0406231407.1a2a3aHb2aIbHbLbHb5a0a5a0aWaJbJbLbIbXaJbLbIbWaKbXa0a4aMbJbHb4aXa342@holomorphy.com>
William Lee Irwin III <wli@holomorphy.com> wrote:
>
> Index: linux-2.6.7/include/linux/mmzone.h
> ===================================================================
> --- linux-2.6.7.orig/include/linux/mmzone.h 2004-06-16 05:19:36.000000000 +0000
> +++ linux-2.6.7/include/linux/mmzone.h 2004-06-23 18:58:13.000000000 +0000
> @@ -170,6 +170,7 @@
> ZONE_PADDING(_pad3_)
>
> struct per_cpu_pageset pageset[NR_CPUS];
> + unsigned long nr_wired[NR_CPUS];
These will share cachelines of course, so the percpuification won't be very
effective. I wonder if there's some way in which the nr_wired accounting
can be batched up and then dumped into a single per-zone counter when we
have the zone->lru_lock.
How come there are all those PageWired() tests in the LRU manipulation
functions?
next prev parent reply other threads:[~2004-06-23 22:15 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-23 21:07 [oom]: [0/4] fix OOM deadlock running OAST William Lee Irwin III
2004-06-23 21:07 ` [oom]: [1/4] add __GFP_WIRED to pinned allocations William Lee Irwin III
2004-06-23 21:07 ` [oom]: [2/4] add nr_wired to page_state William Lee Irwin III
2004-06-23 21:07 ` [oom]: [3/4] track wired pages on a per-zone basis William Lee Irwin III
2004-06-23 21:07 ` [oom]: [4/4] check __GFP_WIRED in out_of_memory() William Lee Irwin III
2004-06-23 21:29 ` [oom]: [3/4] track wired pages on a per-zone basis William Lee Irwin III
2004-06-23 22:15 ` Andrew Morton [this message]
2004-06-23 22:28 ` William Lee Irwin III
2004-06-23 22:05 ` [oom]: [1/4] add __GFP_WIRED to pinned allocations Andrew Morton
2004-06-23 22:22 ` William Lee Irwin III
2004-06-23 22:36 ` Andrew Morton
2004-06-23 22:16 ` [oom]: [0/4] fix OOM deadlock running OAST Andrew Morton
2004-06-23 22:31 ` William Lee Irwin III
2004-06-23 22:37 ` Andrew Morton
2004-06-23 23:07 ` William Lee Irwin III
2004-06-23 23:38 ` Andrew Morton
2004-06-24 0:03 ` William Lee Irwin III
2004-06-24 0:18 ` Andrew Morton
2004-06-24 0:26 ` William Lee Irwin III
2004-06-24 0:32 ` William Lee Irwin III
2004-06-24 1:07 ` Andrew Morton
2004-06-24 1:24 ` William Lee Irwin III
2004-06-24 1:52 ` William Lee Irwin III
2004-06-24 2:01 ` Andrew Morton
2004-06-24 2:15 ` William Lee Irwin III
2004-06-24 14:16 ` Marcelo Tosatti
2004-06-24 15:18 ` William Lee Irwin III
2004-06-24 15:19 ` William Lee Irwin III
2004-06-24 15:23 ` William Lee Irwin III
2004-06-24 16:55 ` Marcelo Tosatti
2004-06-25 15:18 ` Rik van Riel
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=20040623151536.023404fc.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wli@holomorphy.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
all inboxes | Powered by JetHome®