All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jack Steiner <steiner@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] [RFD] physical memory granularity
Date: Wed, 28 Aug 2002 19:55:05 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590701905998@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590701905996@msgid-missing>

> 
> Linux on IA64 currently supports "granules" of 16MB and 64MB.  
> This is the page size used for the kernel identity-mapped
> regions.  Everything mapped by a page must actually exist (to
> avoid MCAs when prefetching into a hole) and must have the same
> attributes (to avoid attribute aliasing), so we assume that
> physical memory comes in granule-sized chunks.
> 
> DIG64 2.1 says nothing about the granularity of physical memory, 
> but it seems that for all existing IA64 machines, memory comes in
> chunks of at least 64MB.  But there's an HP machine in the pipe
> that may support only 4MB granularity.
> 
> I'm not keen on reducing the granule size to 4MB, because I'm 
> afraid the extra TLB misses will be a noticeable performance
> problem.  Does anybody have any quantitative data on the effect
> of granule size on performance?  

Certainly nothing conclusive, but ....

About 6 months ago, I ran the AIM7 benchmark with 16MB & 64MB 
granules. No measurable difference. The runs were indistinguishable.


However, with other benchmarks (or 4MB granules), YMMV.




> Or any strong opinions on what
> granule sizes we should support?
> 
> Bjorn
> 
> _______________________________________________
> Linux-IA64 mailing list
> Linux-IA64@linuxia64.org
> http://lists.linuxia64.org/lists/listinfo/linux-ia64
> 


-- 
Thanks

Jack Steiner    (651-683-5302)   (vnet 233-5302)      steiner@sgi.com



      reply	other threads:[~2002-08-28 19:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-28 16:42 [Linux-ia64] [RFD] physical memory granularity Bjorn Helgaas
2002-08-28 19:55 ` Jack Steiner [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-105590701905998@msgid-missing \
    --to=steiner@sgi.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 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.