From: Gerald Pfeifer <gp@suse.de>
To: linux-ia64@vger.kernel.org
Subject: Re: [RFC] 4-level page table directories.
Date: Tue, 08 Nov 2005 23:58:51 +0000 [thread overview]
Message-ID: <Pine.LNX.4.63.0511082003120.11938@lifschitz.suse.de> (raw)
In-Reply-To: <20051027041709.GA13193@attica.americas.sgi.com>
On Tue, 8 Nov 2005, Rohit Seth wrote:
> I agree with you completely about OSV certification part. And SuSE is
> again a good example here, they have a released kernel with 64K page
> size. There is no reason why end customer should not be using this
> bigger page kernel when desired.
Unfortuantely, I'm pretty sure that if you run such a kernel and call
$BIGISV for support you'll find yourself in troubles. :-(
For example, at least one important ISV even requires a specific
version of the distro kernel RPMs (excluding security updates), so
I pretty much doubt they'll support an alternative kernel such as
one with 64K page size.
> I just think that we should validate the 64K page size more rigorously.
> So as to have the OSVs gain more confidence. There is such a wide range
> of system configurations...having a single kernel configuration may not
> be the optimal solution.
As an OSV, we are facing combinatorial explosion. For example when
we also consider CPU counts we get 32p vs 512p maximum on one dimension,
and 16K vs 64K on another, and there may be further ones lurking in the
dark right now (like Xen Dom0 versus Xen Dom1).
OSVs and ISVs, on the other hand, usually prefer to only test and harden
and qualify/certify a single kernel (which is why Dan's approach to Xen/ia64
looks quite appealing).
Gerald
next prev parent reply other threads:[~2005-11-08 23:58 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
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 [this message]
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=Pine.LNX.4.63.0511082003120.11938@lifschitz.suse.de \
--to=gp@suse.de \
--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