From: Andrew Morton <akpm@linux-foundation.org>
To: Nick Piggin <nickpiggin@yahoo.com.au>
Cc: Mel Gorman <mel@csn.ul.ie>, Eric Munson <ebmunson@us.ibm.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
linuxppc-dev@ozlabs.org,
libhugetlbfs-devel@lists.sourceforge.net
Subject: Re: [RFC] [PATCH 0/5 V2] Huge page backed user-space stacks
Date: Wed, 30 Jul 2008 23:14:28 -0700 [thread overview]
Message-ID: <20080730231428.a7bdcfa7.akpm@linux-foundation.org> (raw)
In-Reply-To: <200807311604.14349.nickpiggin@yahoo.com.au>
On Thu, 31 Jul 2008 16:04:14 +1000 Nick Piggin <nickpiggin@yahoo.com.au> wrote:
> > Do we expect that this change will be replicated in other
> > memory-intensive apps? (I do).
>
> Such as what? It would be nice to see some numbers with some HPC or java
> or DBMS workload using this. Not that I dispute it will help some cases,
> but 10% (or 20% for ppc) I guess is getting toward the best case, short
> of a specifically written TLB thrasher.
I didn't realise the STREAM is using vast amounts of automatic memory.
I'd assumed that it was using sane amounts of stack, but the stack TLB
slots were getting zapped by all the heap-memory activity. Oh well.
I guess that effect is still there, but smaller.
I agree that few real-world apps are likely to see gains of this
order. More benchmarks, please :)
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2008-07-31 6:14 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-28 19:17 Eric Munson
2008-07-28 19:17 ` [PATCH 1/5 V2] Align stack boundaries based on personality Eric Munson
2008-07-28 20:09 ` Dave Hansen
2008-07-28 19:17 ` [PATCH 2/5 V2] Add shared and reservation control to hugetlb_file_setup Eric Munson
2008-07-28 19:17 ` [PATCH 3/5] Split boundary checking from body of do_munmap Eric Munson
2008-07-28 19:17 ` [PATCH 4/5 V2] Build hugetlb backed process stacks Eric Munson
2008-07-28 20:37 ` Dave Hansen
2008-07-28 19:17 ` [PATCH 5/5 V2] [PPC] Setup stack memory segment for hugetlb pages Eric Munson
2008-07-28 20:33 ` [RFC] [PATCH 0/5 V2] Huge page backed user-space stacks Dave Hansen
2008-07-28 21:23 ` Eric B Munson
2008-07-30 8:41 ` Andrew Morton
2008-07-30 15:04 ` Eric B Munson
2008-07-30 15:08 ` Eric B Munson
2008-07-30 8:43 ` Andrew Morton
2008-07-30 17:23 ` Mel Gorman
2008-07-30 17:34 ` Andrew Morton
2008-07-30 19:30 ` Mel Gorman
2008-07-30 19:40 ` Christoph Lameter
2008-07-30 20:07 ` Andrew Morton
2008-07-31 10:31 ` Mel Gorman
2008-08-04 21:10 ` Dave Hansen
2008-08-05 11:11 ` Mel Gorman
2008-08-05 16:12 ` Dave Hansen
2008-08-05 16:28 ` Mel Gorman
2008-08-05 17:53 ` Dave Hansen
2008-08-06 9:02 ` Mel Gorman
2008-08-06 19:50 ` Dave Hansen
2008-08-07 16:06 ` Mel Gorman
2008-08-07 17:29 ` Dave Hansen
2008-08-11 8:04 ` Mel Gorman
2008-07-31 6:04 ` Nick Piggin
2008-07-31 6:14 ` Andrew Morton [this message]
2008-07-31 6:26 ` Nick Piggin
2008-07-31 11:27 ` Mel Gorman
2008-07-31 11:51 ` Nick Piggin
2008-07-31 13:50 ` Mel Gorman
2008-07-31 14:32 ` Michael Ellerman
2008-08-06 18:49 ` Andi Kleen
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=20080730231428.a7bdcfa7.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=ebmunson@us.ibm.com \
--cc=libhugetlbfs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=mel@csn.ul.ie \
--cc=nickpiggin@yahoo.com.au \
/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