From: "Martin J. Bligh" <mbligh@aracnet.com>
To: GrandMasterLee <masterlee@digitalroadkill.net>
Cc: Austin Gonyou <austin@coremetrics.com>, linux-kernel@vger.kernel.org
Subject: Re: Using O(1) scheduler with 600 processes.
Date: Thu, 23 Jan 2003 22:48:19 -0800 [thread overview]
Message-ID: <438270000.1043390898@titus> (raw)
In-Reply-To: <1043389673.14486.7.camel@localhost>
> Heh..Well, I am currently using 2.4.19rc5aa1. We're having some major
> stack problems, so I first when through trying to update the XFS
> codebase in 2.4.19rc5aa1. That didn't prove very fruitful. I couldn't
> even fully reverse the patch for some reason.
>
> 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.
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.
M.
next prev parent reply other threads:[~2003-01-24 6:39 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 [this message]
2003-01-24 8:50 ` William Lee Irwin III
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=438270000.1043390898@titus \
--to=mbligh@aracnet.com \
--cc=austin@coremetrics.com \
--cc=linux-kernel@vger.kernel.org \
--cc=masterlee@digitalroadkill.net \
/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