From: Andrew Morton <akpm@osdl.org>
To: William Lee Irwin III <wli@holomorphy.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [oom]: [0/4] fix OOM deadlock running OAST
Date: Wed, 23 Jun 2004 19:01:50 -0700 [thread overview]
Message-ID: <20040623190150.4a182cfc.akpm@osdl.org> (raw)
In-Reply-To: <20040624015229.GP1552@holomorphy.com>
William Lee Irwin III <wli@holomorphy.com> wrote:
>
> Also, you mentioned at one point extending committed memory accounting
> to account for unreclaimable pages (the term you suggested). Would you
> also like that to be looked into? It might take longer than overnight
> to brew up, mostly due to testing turnaround.
Well let's see how the patch ends up looking.
I have bad feelings about the overcommit logic - several times we have
accidentally noticed (and fixed) gross inaccuracies in it, and I am sure
others remain.
I am not aware of anyone getting down and explicitly testing it in lots of
different scenarios (including mlock), and perhaps it gets inaccurate when
zone fallbacks are involved.
If you're prepared to undertake that level of thinking and coverage testing
and fix up the fallout, that would certainly be good. If you think it's
worth the effort, and, again, depending upon the performance and ickiness
impact of the patches.
next prev parent reply other threads:[~2004-06-24 2:02 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-23 21:07 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
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 [this message]
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=20040623190150.4a182cfc.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®