linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dave Hansen <haveblue@us.ibm.com>
To: William Lee Irwin III <wli@holomorphy.com>
Cc: Andrew Morton <akpm@digeo.com>,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: 2.5.68-mm4
Date: Fri, 02 May 2003 09:47:33 -0700	[thread overview]
Message-ID: <3EB2A125.4000407@us.ibm.com> (raw)
In-Reply-To: 20030502131857.GH8978@holomorphy.com

William Lee Irwin III wrote:
>> On Fri, May 02, 2003 at 02:01:49AM -0700, Andrew Morton wrote:
>>+dont-set-kernel-pgd-on-PAE.patch
>> little ia32 optimisation/cleanup
> 
> It looks like no one listened to my commentary on the set_pgd() patch.
> 
> Remove pointless #ifdef, pointless set_pgd(), and a mysterious line
> full of nothing but whitespace after the #endif, and update commentary.
> -#ifndef CONFIG_X86_PAE
> -		set_pgd(pgd, *pgd_k);
> -#endif

I wask thinking that the PMD set in 4G mode was a noop.  But, it isn't,
so it makes up for the completely removed pgd set.

This comment needs to get updated in include/asm-i386/pgtable-2level.h:
/*
 * (pmds are folded into pgds so this doesn't get actually called,
 * but the define is needed for a generic inline function.)
 */
#define set_pmd(pmdptr, pmdval) (*(pmdptr) = pmdval)
#define set_pgd(pgdptr, pgdval) (*(pgdptr) = pgdval)

-- 
Dave Hansen
haveblue@us.ibm.com


  reply	other threads:[~2003-05-02 16:36 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-02  9:01 2.5.68-mm4 Andrew Morton
2003-05-02 13:18 ` 2.5.68-mm4 William Lee Irwin III
2003-05-02 16:47   ` Dave Hansen [this message]
2003-05-02 14:45 ` 2.5.68-mm4 Steven Cole
2003-05-02 15:00   ` 2.5.68-mm4 Steven Cole
2003-05-02 15:35 ` 2.5.68-mm4 Anton Blanchard
2003-05-03 14:12   ` 2.5.68-mm4 Eric W. Biederman
2003-05-02 16:54 ` 2.5.68-mm4 Martin J. Bligh
2003-05-02 20:04 ` 2.5.68-mm4 Steven Cole
2003-05-02 20:34   ` 2.5.68-mm4 Andrew Morton
2003-05-02 20:49     ` 2.5.68-mm4 Steven Cole
2003-05-02 21:01       ` 2.5.68-mm4 Steven Cole
2003-05-02 21:05       ` 2.5.68-mm4 Andrew Morton
2003-05-02 21:20         ` 2.5.68-mm4 Steven Cole
2003-05-02 21:49           ` 2.5.68-mm4 Andy Pfiffer
2003-05-02 22:00             ` 2.5.68-mm4 Steven Cole
2003-05-02 23:22           ` 2.5.68-mm4 Matt Bernstein
2003-05-02 23:41             ` 2.5.68-mm4 Andrew Morton
2003-05-03  2:53               ` 2.5.68-mm4 Andi Kleen
2003-05-03  7:08                 ` 2.5.68-mm4 Matt Bernstein
     [not found]                   ` <Pine.LNX.4.55.0305061511020.3237@r2-pc.dcs.qmul.ac.uk>
2003-05-06 14:35                     ` 2.5.68-mm4 Andi Kleen
2003-05-06 15:50                       ` 2.5.68-mm4 Matt Bernstein
2003-05-07 10:27                       ` 2.5.68-mm4 Matt Bernstein
2003-05-07 12:35                         ` 2.5.68-mm4 Andi Kleen
2003-05-07 15:45                           ` 2.5.68-mm4 Matt Bernstein
2003-05-03  3:14               ` 2.5.68-mm4 Andi Kleen
2003-05-03 13:51               ` 2.5.68-mm4 Diego Calleja García
2003-05-03  1:14     ` 2.5.68-mm4 Herbert Xu
2003-05-05  3:46 ` 2.5.68-mm4 && kexec Eric W. Biederman
2003-05-02 19:58 2.5.68-mm4 J. Hidding
2003-05-03 11:52 2.5.68-mm4 cb-lkml

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=3EB2A125.4000407@us.ibm.com \
    --to=haveblue@us.ibm.com \
    --cc=akpm@digeo.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.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;
as well as URLs for NNTP newsgroup(s).