mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Buddy Lumpkin" <b.lumpkin@comcast.net>
To: <linux-kernel@VGER.KERNEL.ORG>
Subject: Large page support in the Linux Kernel?
Date: Sat, 1 May 2004 02:28:07 -0700	[thread overview]
Message-ID: <S262103AbUEAJXe/20040501092334Z+498@vger.kernel.org> (raw)

I was wondering if there is going to be large page support for the linux
kernel in the near future. I am sure most people know the benefit this has
for large databases like Oracle, ultimately larger pages means the TLB slots
refer to a much larger area of memory increasing the chance of a TLB hit and
avoiding the need to walk the page tables in the MMU.

I have spotted a few previous threads where fragmentation and the complexity
in making these pages such that they can be evicted were offered as reasons
to defer this feature. I think this is a mistake. 

In Solaris, the first large page support was added to the shared memory
segment driver and called Intimate Shared Memory. ISM uses 4MB pages, and is
a segment that is locked in memory (non-pagable). Solaris hasn't done
anything to address fragmentation as far as I know until recently in Solaris
9 (ISM has been available since 2.6, maybe prior). 

I have seen many cases where a DBA shuts down an Oracle instance, but cannot
restart it because significant memory use has taken place since the instance
was shut down (filesystem backed pages read into the page cache, malloc,
free, etc..), and in these cases, there was plenty of available memory on
the system to handle the request for the ISM segment. In most Oracle
installations, the SGA is allocated with an ISM segment that stays resident
for entire duration that the Oracle instance is running. This is hardly a
case where fragmentation is going to cause an issue since normal 4k or 8k
pages are allocated easily in the presence of this segment.

To a kernel programmer, the fragmentation and paging issues may seem like a
big issue, but any DBA I know would happily make this tradeoff on their
production databases for the additional performance that large pages offers.

If fragmentation isn't a big deal, and pages can be locked in memory, are
large pages still a difficult feature to add to the linux kernel?

Lastly, I know I have mentioned Oracle and Solaris a lot. Please don't flame
me for this, I think the points I am trying to make are reasonable.

Regards,

--Buddy




             reply	other threads:[~2004-05-01  9:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-01  9:28 Buddy Lumpkin [this message]
2004-05-01 10:36 ` Paul Jackson
2004-05-02  4:45   ` Buddy Lumpkin
2004-05-01 16:15 ` Tom Sightler
2004-05-01 23:22 ` Rik van Riel

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=S262103AbUEAJXe/20040501092334Z+498@vger.kernel.org \
    --to=b.lumpkin@comcast.net \
    --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®