From: William Lee Irwin III <wli@holomorphy.com>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org, mingo@elte.hu
Subject: Re: 2.6.0-test2-mm4
Date: Mon, 4 Aug 2003 07:08:14 -0700 [thread overview]
Message-ID: <20030804140814.GJ32488@holomorphy.com> (raw)
In-Reply-To: <20030804013036.16d9fa3a.akpm@osdl.org>
On Mon, Aug 04, 2003 at 01:30:36AM -0700, Andrew Morton wrote:
> +4g4g-pmd-fix.patch
If you're going to back out pgd preconstruction, at least back it out
all the way so list poison isn't tripped over randomly on PAE. This is
actually worse than before, since you're basically doing list_del()
on whatever value of page->lru was handed to mm/slab.c from page_alloc.c
in pgd_dtor() multiple times per-page and pounding the lock for no
reason whatsoever on PAE. It's also degrading performance on non-PAE
due to the fact no preconstruction is done there, though harmless due
to the fact the only trace of pgd preconstruction left is the AGP fix.
Someone please tell me they realize this is a backout because absolutely
zero data structure initialization is done in ->ctor() and the entire
thing is memcpy()'d and memset()'d over in the front end to the slab.
I have no idea what, if anything has been absorbed from my prior posts
on this subject. AFAICT I'm getting dead air (or worse) back from
everyone else and no one's even bothering to read the code. i.e. either
no one understands a word I'm saying or no one's listening.
-- wli
prev parent reply other threads:[~2003-08-04 14:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-04 8:30 2.6.0-test2-mm4 Andrew Morton
2003-08-04 11:56 ` 2.6.0-test2-mm4 Daniele Bellucci
2003-08-04 14:08 ` William Lee Irwin III [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=20030804140814.GJ32488@holomorphy.com \
--to=wli@holomorphy.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@elte.hu \
/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;
as well as URLs for NNTP newsgroup(s).