From: Jack Steiner <steiner@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [RFC] 4-level page table directories.
Date: Thu, 03 Nov 2005 03:55:07 +0000 [thread overview]
Message-ID: <20051103035506.GA8611@sgi.com> (raw)
In-Reply-To: <20051027041709.GA13193@attica.americas.sgi.com>
On Thu, Nov 03, 2005 at 02:36:18AM +0100, Gerald Pfeifer wrote:
> On Thu, 3 Nov 2005, Ian Wienand wrote:
> > On Wed, Nov 02, 2005 at 11:16:11AM -0600, Robin Holt wrote:
> > I must admit to be a bit perplexed however. I would have thought that
> > a customer who just spent (what I assume is a lot of) money on a
> > machine to map huge areas of contiguous memory would really want to
> > evaluate the probable benefits of larger pages, despite what Redhat
> > ships.
>
> I'll note that SUSE has been shipping a 64k-pagesize kernel for more
> than a year now as part of SUSE LINUX Enterprise Server 9, and I have
> not seen a single L3 support call for this kernel.
>
> Which means that it's either completely bug free, or nobody uses it
> in production. ;-)
You are probably correct that very few sites use it. Part of the reason is
that the 64k-pagesize kernel is built with NR_CPUS\x128 - not 512. I suspect
that many of the big-memory sites have more than 128p. That makes the 64K page
kernel unusable for those sites.
In addition, the 64k-pagesize kernel does not have KDB configured. That
makes support more difficult. Many sites use the "arch-kdb" commands
to take quick dumps after system failures.
(and of course it really is bug free :-)
>
> > I'm probably just extremley naive as to what customers really
> > want, however.
>
> The reason customers generally prefer to go with default kernels,
> as far as I can tell, is software certification. If you're only
> running your special applications, you may not care, but for such
> huge memory configs a DBMS like Oracle or DB2 is often part of the
> picture, for example.
True...
>
> Gerald
> -
> To unsubscribe from this list: send the line "unsubscribe linux-ia64" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Thanks
.Jack Steiner (steiner@sgi.com) 651-683-5302
Principal Engineer SGI - Silicon Graphics, Inc.
next prev parent reply other threads:[~2005-11-03 3:55 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-27 4:17 [RFC] 4-level page table directories Robin Holt
2005-10-28 5:19 ` Ian Wienand
2005-10-28 11:19 ` Robin Holt
2005-10-28 23:23 ` Luck, Tony
2005-10-28 23:55 ` Chen, Kenneth W
2005-10-29 0:49 ` Grant Grundler
2005-10-29 2:18 ` David Mosberger-Tang
2005-11-01 12:13 ` Robin Holt
2005-11-01 15:41 ` David Mosberger-Tang
2005-11-02 10:35 ` Robin Holt
2005-11-02 13:26 ` Robin Holt
2005-11-02 16:11 ` Luck, Tony
2005-11-02 16:23 ` Robin Holt
2005-11-02 16:30 ` Luck, Tony
2005-11-02 17:16 ` Robin Holt
2005-11-02 18:59 ` David Mosberger-Tang
2005-11-02 22:26 ` Ian Wienand
2005-11-03 1:36 ` Gerald Pfeifer
2005-11-03 1:53 ` Chen, Kenneth W
2005-11-03 3:55 ` Jack Steiner [this message]
2005-11-03 16:36 ` Robin Holt
2005-11-03 19:59 ` Chen, Kenneth W
2005-11-04 17:58 ` Luck, Tony
2005-11-04 21:37 ` Robin Holt
2005-11-04 21:42 ` Chen, Kenneth W
2005-11-04 22:50 ` Chen, Kenneth W
2005-11-07 21:18 ` Luck, Tony
2005-11-08 0:22 ` Rohit Seth
2005-11-08 12:43 ` Robin Holt
2005-11-08 18:23 ` Boehm, Hans
2005-11-08 18:52 ` Magenheimer, Dan (HP Labs Fort Collins)
2005-11-08 18:56 ` Rohit Seth
2005-11-08 19:36 ` Robin Holt
2005-11-08 20:07 ` Chen, Kenneth W
2005-11-08 20:27 ` Chen, Kenneth W
2005-11-08 22:09 ` Ian Wienand
2005-11-08 23:58 ` Gerald Pfeifer
2005-11-09 0:08 ` David Mosberger-Tang
2005-11-09 0:22 ` Rohit Seth
2005-11-09 0:46 ` Magenheimer, Dan (HP Labs Fort Collins)
2005-11-09 1:18 ` Chen, Kenneth W
2005-11-09 12:11 ` Robin Holt
2005-11-09 14:29 ` Robin Holt
2005-11-09 18:22 ` Chen, Kenneth W
2005-11-09 18:39 ` Luck, Tony
2005-11-10 0:03 ` Gerald Pfeifer
2005-11-10 0:23 ` Jack Steiner
2005-11-10 0:27 ` Luck, Tony
2005-11-10 2:54 ` Jack Steiner
2005-11-10 9:13 ` Robin Holt
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=20051103035506.GA8611@sgi.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox