mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Borzenkov, Andrey" <andrey.borzenkov@ts.fujitsu.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: Extermeley large PageTables over 500G on kernel 2.6.32.49 (SLES11 SP1)
Date: Wed, 11 Jan 2012 12:23:37 +0100	[thread overview]
Message-ID: <CB1B361E45A85849902B25342E88900501CFDC31120E@ABGEX70E.FSC.NET> (raw)
In-Reply-To: <1326280780.2767.11.camel@edumazet-HP-Compaq-6005-Pro-SFF-PC>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="utf-8", Size: 1408 bytes --]

> -----Original Message-----
> From: Eric Dumazet [mailto:eric.dumazet@gmail.com]
> Sent: Wednesday, January 11, 2012 3:20 PM
> To: Borzenkov, Andrey
> Cc: linux-kernel@vger.kernel.org
> Subject: RE: Extermeley large PageTables over 500G on kernel 2.6.32.49
> (SLES11 SP1)
> 
> Le mercredi 11 janvier 2012 à 11:52 +0100, Borzenkov, Andrey a écrit :
> 
> > Colleagues responsible for Oracle are reconfiguring it now.
> >
> 
> OK. Since your hardware supports 1GB hugepages, you might try to use
> them as well. Not sure if your kernel is recent enough...
> 
> cat /proc/cmdline
> ro root=LABEL=/ hugepagesz=1GB hugepages=512
> 

It says 2M so it probably is the limit.

> > > If not, its normal to eat so much memory for page tables
> > >
> > > grep VmPTE /proc/*/status
> > >
> > >
> >
> > Forgive my ignorance. I thought that
> >
> > 1. PTE is 8 bytes per page, which is 4K which gives 2K per 1M of memory
> > 2. All processes sharing the same shared memory share the same page
> table
> 
> It depends how oracle maps its SGA.
> 
> It probably uses a method disallowing page table sharing.

Do you have any reference to description of these methods so we can check?

Thank you!

> 
> Anyway, hugetables for this kind of workload is a must.
> 


ÿôèº{.nÇ+‰·Ÿ®‰­†+%ŠËÿ±éݶ\x17¥Šwÿº{.nÇ+‰·¥Š{±þG«éÿŠ{ayº\x1dʇڙë,j\a­¢f£¢·hšïêÿ‘êçz_è®\x03(­éšŽŠÝ¢j"ú\x1a¶^[m§ÿÿ¾\a«þG«éÿ¢¸?™¨è­Ú&£ø§~á¶iO•æ¬z·švØ^\x14\x04\x1a¶^[m§ÿÿÃ\fÿ¶ìÿ¢¸?–I¥

  reply	other threads:[~2012-01-11 11:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-11 10:18 Borzenkov, Andrey
2012-01-11 10:36 ` Eric Dumazet
2012-01-11 10:52   ` Borzenkov, Andrey
2012-01-11 11:19     ` Eric Dumazet
2012-01-11 11:23       ` Borzenkov, Andrey [this message]
2012-01-11 11:26     ` Avi Kivity
2012-01-13  5:20       ` Borzenkov, Andrey
2012-01-16 15:43         ` Avi Kivity

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=CB1B361E45A85849902B25342E88900501CFDC31120E@ABGEX70E.FSC.NET \
    --to=andrey.borzenkov@ts.fujitsu.com \
    --cc=eric.dumazet@gmail.com \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®