From: Ralf Baechle <ralf@linux-mips.org>
To: Fuxin Zhang <fxzhang@ict.ac.cn>
Cc: Thiemo Seufer <ths@networkno.de>,
Linux/MIPS Development <linux-mips@linux-mips.org>
Subject: Re: tools to convert debian sarge to 16K page size
Date: Fri, 10 Mar 2006 16:38:36 +0000 [thread overview]
Message-ID: <20060310163836.GA13976@linux-mips.org> (raw)
In-Reply-To: <44118268.5030109@ict.ac.cn>
On Fri, Mar 10, 2006 at 09:43:04PM +0800, Fuxin Zhang wrote:
> Thiemo Seufer 写道:
> > Can you provide information about the performance impact? That is,
> > what system(s) you use, and some basic benchmark numbers. Did you also
> > try 64k pages?
> The system is running debian sarge,with a mips like Chinese 4-way
> superscalar CPU and marvell 64240 system bridge, 256M sdram.Maybe
> related information: this CPU has 64K 4-way dcache/icache，so cache
> alias exists with 4K configuration.
>
> Big page size helps a bit with at least computational programs, such as
> SPEC CPU2000 benchmarks. The attached jpg is a graph showing the results
> of some SPEC programs under different page sizes. But we have not
> benchmarked other workloads. 16K page size is used mainly to avoid cache
> alias, which caused us too much time.
>
> Yes, with 64k more patches needed(some "short" field overflow?I don't
> remember the exact modifications,other guys did it)
There is more to large pages than just improved performance. They'll
also save 75% memory for mem_map, will eleminate cache aliases in a
bulletproof way. And will make allocation of memory larger than 4kB
reliable - this especially is a big bonus with ethernet jumboframes with
some NICs.
Ralf
prev parent reply other threads:[~2006-03-10 16:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-10 8:50 tools to convert debian sarge to 16K page size Fuxin Zhang
2006-03-10 13:16 ` Thiemo Seufer
2006-03-10 13:43 ` Fuxin Zhang
2006-03-10 16:38 ` Ralf Baechle [this message]
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=20060310163836.GA13976@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=fxzhang@ict.ac.cn \
--cc=linux-mips@linux-mips.org \
--cc=ths@networkno.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.