From: William Lee Irwin III <wli@holomorphy.com>
To: "Martin J. Bligh" <mbligh@aracnet.com>
Cc: GrandMasterLee <masterlee@digitalroadkill.net>,
Austin Gonyou <austin@coremetrics.com>,
linux-kernel@vger.kernel.org
Subject: Re: Using O(1) scheduler with 600 processes.
Date: Fri, 24 Jan 2003 00:50:26 -0800 [thread overview]
Message-ID: <20030124085026.GW780@holomorphy.com> (raw)
In-Reply-To: <438270000.1043390898@titus>
At some point in the past, someone else wrote:
>> So I decided to try 2.4.20aa1 instead, reversing the xfs patches, and
>> then updating with a newer code base, worse problems reversing those xfs
>> patches.
>> SO I decided to just roll my own with the known features we use in
>> production.
>> 2.4.20 + xfs + lvm106 + rmap or aavm + O(1) sched + pte-highmem.
On Thu, Jan 23, 2003 at 10:48:19PM -0800, Martin J. Bligh wrote:
> If you have enough ptes to want pte-highmem, I doubt you want rmap.
> pte-chain space consumption will kill you. The calculations are pretty
> easy to work out as to what the right solution is for your setup.
Basically vma-based ptov resolution needs to be implemented for private
anonymous pages, which will require much less ZONE_NORMAL space overhead
as pte_chains may then be chucked.
Dropping physical scanning altogether would be a mistake esp. for boxen
of any appreciable amount of physical locality (NUMA, big highmem
penalties, etc.) or wishing to support any significant number of tasks.
-- wli
next prev parent reply other threads:[~2003-01-24 8:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-24 0:10 Using O(1) scheduler with 600 processes Austin Gonyou
2003-01-24 0:24 ` Martin J. Bligh
2003-01-24 6:09 ` GrandMasterLee
2003-01-24 6:18 ` Martin J. Bligh
2003-01-24 6:27 ` GrandMasterLee
2003-01-24 6:48 ` Martin J. Bligh
2003-01-24 8:50 ` William Lee Irwin III [this message]
2003-01-24 2:05 ` mgross
2003-01-24 6:08 ` GrandMasterLee
2003-01-24 18:22 ` mgross
2003-01-24 21:44 ` GrandMasterLee
-- strict thread matches above, loose matches on Subject: below --
2003-01-24 0:24 Perez-Gonzalez, Inaky
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=20030124085026.GW780@holomorphy.com \
--to=wli@holomorphy.com \
--cc=austin@coremetrics.com \
--cc=linux-kernel@vger.kernel.org \
--cc=masterlee@digitalroadkill.net \
--cc=mbligh@aracnet.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.