From: William Lee Irwin III <wli@holomorphy.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Rik van Riel <riel@conectiva.com.br>,
Ingo Oeser <ingo.oeser@informatik.tu-chemnitz.de>,
Andrew Morton <akpm@zip.com.au>,
Anton Blanchard <anton@samba.org>,
linux-kernel@vger.kernel.org, riel@imladris.surriel.com
Subject: Re: fix CONFIG_HIGHPTE
Date: Thu, 8 Aug 2002 12:22:01 -0700 [thread overview]
Message-ID: <20020808192201.GF15685@holomorphy.com> (raw)
In-Reply-To: <1028836757.28883.73.camel@irongate.swansea.linux.org.uk>
On Thu, 2002-08-08 at 15:51, Rik van Riel wrote:
>> Linux isn't yet up to having 500 simultaneous interactive
>> users, in fact I don't think it has ever been up to this
>> situation.
On Thu, Aug 08, 2002 at 08:59:17PM +0100, Alan Cox wrote:
> It works suprisingly well. I know people who are doing it. It does not
> work when those users are all running arbitarly large jobs. In most
> conventional (non student compile) type setups 500 is fine. The O(1)
> scheduler and highio are pretty essential as is a real I/O subsystem.
Could you put me and/or Rik in contact with them so we can get a better
grip on their issues and characteristics of their workload?
Thanks,
Bill
next prev parent reply other threads:[~2002-08-08 19:19 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-06 23:15 fix CONFIG_HIGHPTE William Lee Irwin III
2002-08-07 0:43 ` Andrew Morton
2002-08-07 0:50 ` Rik van Riel
2002-08-07 1:31 ` William Lee Irwin III
2002-08-07 4:00 ` Rik van Riel
2002-08-07 4:12 ` William Lee Irwin III
2002-08-07 1:07 ` Anton Blanchard
2002-08-07 1:55 ` William Lee Irwin III
2002-08-07 2:57 ` Andrew Morton
2002-08-07 18:43 ` Ingo Oeser
2002-08-08 14:51 ` Rik van Riel
2002-08-08 19:59 ` Alan Cox
2002-08-08 18:44 ` Rik van Riel
2002-08-08 19:22 ` William Lee Irwin III [this message]
2002-08-08 14:51 ` Martin J. Bligh
2002-08-09 14:10 ` Daniel Phillips
2002-08-09 14:07 ` Daniel Phillips
2002-08-07 4:05 ` Rik van Riel
2002-08-07 4:18 ` Anton Blanchard
2002-08-07 5:16 ` Martin J. Bligh
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=20020808192201.GF15685@holomorphy.com \
--to=wli@holomorphy.com \
--cc=akpm@zip.com.au \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=anton@samba.org \
--cc=ingo.oeser@informatik.tu-chemnitz.de \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@conectiva.com.br \
--cc=riel@imladris.surriel.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.