RE: Hugepages - benefits / drawbacks
Date: Thu, 9 Oct 2008 13:25:52 -0500
Does anyone have any doc (for the Unix SA) for hugepages on Solaris 9/10?
so I can get their help to implement this?
Guillermo Alan Bort
DBA / DBA Main Team
EDS, an HP company
[mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Yong Huang Sent: Thursday, October 09, 2008 1:31 PM To: oracle-l_at_freelists.org
Cc: David.J.Miller_at_Sun.COM; roman.podshivalov_at_gmail.com Subject: Re: Hugepages - benefits / drawbacks
Thanks, David. That finally anwers my (and maybe Roman's) question: How can ISM be used for PGA? Just because there's a shared (or rather, sharable) memory segment created doesn't mean it must be shared. Solaris ISM or Linux HugePages is just a name for this technology. It has all these features: (a) sharing page tables between processes, (b) large memory page size, (c) locking pages in memory (related to (a)). The name ISM emphasizes (a), while HugePages emphasizes (b). The Oracle parameter _use_ism_for_pga confused me simply because they used the term ism in it. If it was called _use_largepage_for_pga without any change in its implementation, I wouldn't ask the question.
> From: David Miller <David.J.Miller_at_Sun.COM>
> Hi Roman,
> ISM is indeed shared memory, but it is possible to allocate it and
> use it in one place, i.e. a single process's PGA. Once it's mapped
> the address space, it's just memory (at least mostly). Clearly when
> this was implemented, the PGA for each process would use a different
> shared memory segment so there wouldn't be collisions.
> As I mentioned before, I'm sure it was done to use large pages. Since
> are other mechanisms now, it's no longer necessary, which is why it
> obsoleted in 10.2.
> Roman Podshivalov wrote, On 10/07/08 18:30:
> > David,
> > In my mind ISM is related to shared memory, could it be used for
> > memory allocation ?
> > thanks
> > --romas