From: William Lee Irwin III <wli@holomorphy.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Andi Kleen <ak@suse.de>, Hugh Dickins <hugh@veritas.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Christoph Lameter <clameter@sgi.com>,
linux-kernel@vger.kernel.org
Subject: Re: slub-i386-support.patch
Date: Fri, 11 May 2007 00:54:10 -0700 [thread overview]
Message-ID: <20070511075410.GT19966@holomorphy.com> (raw)
In-Reply-To: <20070511004200.6d30152e.akpm@linux-foundation.org>
At some point in the past, Hugh Dickins wrote:
>>> I'm guessing (haven't rechecked source) that the cpu_idle() call comes
>>> about because the top level pgd of a process gets freed very late in
>>> its exit, and after a great flurry of processes have just exited,
>>> perhaps there was nothing to free up the accumulation. Though
>>> it still strikes me as an odd place to do it.
On Fri, 11 May 2007 10:29:30 +0200 Andi Kleen <ak@suse.de> wrote:
>> I always found it odd and probably the wrong place too.
On Fri, May 11, 2007 at 12:42:00AM -0700, Andrew Morton wrote:
> so... what's the bottom line here, guys? Should we change that patch?
My summary:
(1) The patch is safe-as is, though it should move its hook elsewhere.
(2) Scribbling on the memory still irks me but is safe.
(3) I should redo the i386 pgd updates to suck less.
(4) Christoph might let me change quicklists to use struct page pointers.
For (3) I can post the update any time; it won't conflict with the
quicklist code, apart from textually, and I can handle the mergework.
The case one should hold off on merging the quicklist code is if
Christoph wants to update the core quicklist code or have me update
it according to the cached precomputed value scheme I outlined in a
prior post before its initial merge. I'll prepare all the patches for
comment regardless.
-- wli
next prev parent reply other threads:[~2007-05-11 7:53 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-10 20:03 slub-i386-support.patch Hugh Dickins
2007-05-10 20:17 ` slub-i386-support.patch Andrew Morton
2007-05-10 20:31 ` slub-i386-support.patch Christoph Lameter
2007-05-10 20:50 ` slub-i386-support.patch David Miller
2007-05-10 20:31 ` slub-i386-support.patch William Lee Irwin III
2007-05-10 20:35 ` slub-i386-support.patch Christoph Lameter
2007-05-10 21:09 ` slub-i386-support.patch William Lee Irwin III
2007-05-10 21:28 ` slub-i386-support.patch Jeremy Fitzhardinge
2007-05-10 23:35 ` slub-i386-support.patch William Lee Irwin III
2007-05-10 21:22 ` slub-i386-support.patch Jeremy Fitzhardinge
2007-05-10 23:14 ` slub-i386-support.patch Hugh Dickins
2007-05-11 0:07 ` slub-i386-support.patch William Lee Irwin III
2007-05-11 1:08 ` slub-i386-support.patch William Lee Irwin III
2007-05-11 5:09 ` slub-i386-support.patch Christoph Lameter
2007-05-11 7:43 ` slub-i386-support.patch William Lee Irwin III
2007-05-11 1:42 ` slub-i386-support.patch William Lee Irwin III
2007-05-11 8:29 ` slub-i386-support.patch Andi Kleen
2007-05-11 7:42 ` slub-i386-support.patch Andrew Morton
2007-05-11 7:54 ` William Lee Irwin III [this message]
2007-05-11 16:15 ` slub-i386-support.patch Christoph Lameter
2007-05-11 20:47 ` slub-i386-support.patch William Lee Irwin III
2007-05-11 9:27 ` slub-i386-support.patch Hugh Dickins
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=20070511075410.GT19966@holomorphy.com \
--to=wli@holomorphy.com \
--cc=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=clameter@sgi.com \
--cc=hugh@veritas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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