tools to convert debian sarge to 16K page size

tools to convert debian sarge to 16K page size

[Fuxin Zhang]

[-- Attachment #1: Type: text/plain, Size: 218 bytes --]

hi,
  Some time ago I promised this:

  Attached is some program/scripts to convert sarge debs to 16k page
compatible,that is, a kernel with PAGE_SIZE == 16K can use it.

  There is a simple README in the tar file.




[-- Attachment #2: convert-debian-16k.tgz --]
[-- Type: application/octet-stream, Size: 7890 bytes --]

Re: tools to convert debian sarge to 16K page size

[Thiemo Seufer]

On Fri, Mar 10, 2006 at 04:50:14PM +0800, Fuxin Zhang wrote:
> hi,
>   Some time ago I promised this:
> 
>   Attached is some program/scripts to convert sarge debs to 16k page
> compatible,that is, a kernel with PAGE_SIZE == 16K can use it.
> 
>   There is a simple README in the tar file.

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?


Thiemo

Re: tools to convert debian sarge to 16K page size

[Fuxin Zhang]

[-- Attachment #1: Type: text/plain, Size: 890 bytes --]



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)
> 
> 
> Thiemo
> 
> 
> 

[-- Attachment #2: perf-pgsizes.jpg --]
[-- Type: image/jpeg, Size: 52220 bytes --]

Re: tools to convert debian sarge to 16K page size

[Ralf Baechle]

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