From: Dave Hansen <haveblue@us.ibm.com>
To: "Martin J. Bligh" <mbligh@aracnet.com>
Cc: Andi Kleen <ak@muc.de>,
torvalds@osdl.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andy Whitcroft <apw@shadowen.org>, Andrew Morton <akpm@osdl.org>
Subject: Re: [PATCH] Permit inode & dentry hash tables to be allocated > MAX_ORDER size
Date: Tue, 15 Jun 2004 09:40:53 -0700 [thread overview]
Message-ID: <1087226661.18615.1752.camel@nighthawk> (raw)
In-Reply-To: <113620000.1087052452@[10.10.2.4]>
On Sat, 2004-06-12 at 08:00, Martin J. Bligh wrote:
> >> Since vmalloc() maps the pages with small pagetable entries (unlike most
> >> of the rest of the kernel address space), do you think the interleaving
> >> will outweigh any negative TLB effects?
> >
> > I think so, yes (assuming you run the benchmark on all CPUs)
>
> On the other hand, there's no reason we can't hack up a version of vmalloc
> to use large pages, and interleave only based on that.
Think about ppc64 where the large page size is 16MB. That might hurt
interleaving a bit if the structure is only 32MB. It's better than
*everything* on node 0, but not by much.
-- Dave
next prev parent reply other threads:[~2004-06-15 16:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <263jX-5RZ-19@gated-at.bofh.it>
[not found] ` <262nZ-56Z-5@gated-at.bofh.it>
[not found] ` <263jX-5RZ-17@gated-at.bofh.it>
2004-06-12 0:21 ` [PATCH] Permit inode & dentry hash tables to be allocated > MAX_ORDER size Andi Kleen
2004-06-12 6:00 ` Martin J. Bligh
2004-06-12 7:36 ` Dave Hansen
2004-06-12 13:11 ` Andi Kleen
2004-06-12 15:00 ` Martin J. Bligh
2004-06-15 16:40 ` Dave Hansen [this message]
2004-06-11 10:44 David Howells
2004-06-11 10:48 ` Andrew Morton
2004-06-11 11:12 ` David Howells
2004-06-11 22:04 ` Andrew Morton
2004-06-11 23:03 ` Martin J. Bligh
2004-06-11 23:19 ` Andrew Morton
2004-06-11 23:18 ` Martin J. Bligh
2004-06-11 23:30 ` Andrew Morton
2004-06-12 12:45 ` Andy Whitcroft
2004-06-13 16:09 ` Linus Torvalds
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=1087226661.18615.1752.camel@nighthawk \
--to=haveblue@us.ibm.com \
--cc=ak@muc.de \
--cc=akpm@osdl.org \
--cc=apw@shadowen.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@aracnet.com \
--cc=torvalds@osdl.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