public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: "Seth, Rohit" <rohit.seth@intel.com>
To: linux-ia64@vger.kernel.org
Subject: RE: [Linux-ia64] page size > 16KB
Date: Sat, 15 Mar 2003 03:08:48 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590709806130@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590709806057@msgid-missing>

The HugeTLB page documentation with 2.5.64 is most uptodate.  The
default setting on SLES8 uses 16MB hugepage size.

> -----Original Message-----
> From: Jesse Barnes [mailto:jbarnes@sgi.com] 
> Sent: Friday, March 14, 2003 9:34 AM
> To: Jan Schreckenbach
> Cc: linux-ia64@linuxia64.org
> Subject: Re: [Linux-ia64] page size > 16KB
> 
> 
> On Fri, Mar 14, 2003 at 01:33:12PM +0100, Jan Schreckenbach wrote:
> > yep, I'm doing some benchmark stuff with SAP/SAPDB and the 
> performance 
> > is not as good as I expected. CONFIG_HUGETLB_PAGE=y is 
> standard on a 
> > SLES8 kernel (2.4.19-SMP). I changed the page size from 16K 
> to 64K and 
> > the performance increase was 2-3 percent. Changing  Huge TLB Page 
> > Size" seems not to have any effect.
> 
> Are you using the huge TLB support (it's not transparent to 
> the app). If you're  seeing a few percent going from 16k to 
> 64k, I'd expect that you'd see a bigger gain going from 16k 
> to using the huge tlb api.  See 
> Documentation/vm/hugetlbpage.txt in the kernel source for an 
> idea of how to make use it (not sure if the doc is up to 
> date, haven't used it myself).
> 
> Jesse
> 
> _______________________________________________
> Linux-IA64 mailing list
> Linux-IA64@linuxia64.org 
> http://lists.linuxia64.org/lists/listinfo/linu> x-ia64
> 


      parent reply	other threads:[~2003-03-15  3:08 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-12 16:38 [Linux-ia64] page size > 16KB Jan Schreckenbach
2003-03-12 16:55 ` Grant Grundler
2003-03-12 17:07 ` n0ano
2003-03-12 17:40 ` David Mosberger
2003-03-12 17:46 ` David Mosberger
2003-03-12 17:49 ` Jesse Barnes
2003-03-12 18:07 ` David Mosberger
2003-03-12 18:08 ` Grant Grundler
2003-03-12 18:24 ` Jesse Barnes
2003-03-12 19:51 ` Mario Smarduch
2003-03-13 18:05 ` David Mosberger
2003-03-13 20:44 ` Mario Smarduch
2003-03-14 12:33 ` Jan Schreckenbach
2003-03-14 15:51 ` Chen, Kenneth W
2003-03-14 17:33 ` Jesse Barnes
2003-03-14 18:00 ` Mario Smarduch
2003-03-14 18:17 ` Grant Grundler
2003-03-14 19:00 ` Jesse Barnes
2003-03-14 19:43 ` David Mosberger
2003-03-15  3:08 ` Seth, Rohit [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=marc-linux-ia64-105590709806130@msgid-missing \
    --to=rohit.seth@intel.com \
    --cc=linux-ia64@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