From: Pete Zaitcev <zaitcev@redhat.com>
To: linux-kernel@vger.kernel.org
Subject: pmd_large vs. pmd_huge
Date: Mon, 28 Jul 2003 15:08:37 -0400 [thread overview]
Message-ID: <20030728150837.A29122@devserv.devel.redhat.com> (raw)
I looked at the 2.6.0-test2 to find out the difference between
large and huge pages, but it seems they are one and the same.
The ia64 only implements pmd_huge, so how about just going
with that everywhere? For starters, we can do this to strike
down an evil #ifdef:
diff -urN -X dontdiff linux-2.6.0-test1-bk2/mm/slab.c linux-2.6.0-test1-bk2-nip/mm/slab.c
--- linux-2.6.0-test1-bk2/mm/slab.c 2003-07-23 18:20:17.000000000 -0700
+++ linux-2.6.0-test1-bk2-nip/mm/slab.c 2003-07-28 11:58:46.000000000 -0700
@@ -91,6 +91,7 @@
#include <linux/cpu.h>
#include <linux/sysctl.h>
#include <linux/module.h>
+#include <linux/hugetlb.h>
#include <asm/uaccess.h>
#include <asm/cacheflush.h>
@@ -2728,12 +2729,10 @@
printk("No pmd.\n");
break;
}
-#ifdef CONFIG_X86
- if (pmd_large(*pmd)) {
- printk("Large page.\n");
+ if (pmd_huge(*pmd)) {
+ printk("Huge page.\n");
break;
}
-#endif
printk("normal page, pte_val 0x%llx\n",
(unsigned long long)pte_val(*pte_offset_kernel(pmd, addr)));
} while(0);
reply other threads:[~2003-07-28 18:53 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20030728150837.A29122@devserv.devel.redhat.com \
--to=zaitcev@redhat.com \
--cc=linux-kernel@vger.kernel.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