From: Pavel Machek <pavel@suse.cz>
To: adefacc@tin.it, linux-kernel@vger.kernel.org
Subject: Re: Confirmation request about new 2.4.x. kernel limits
Date: Fri, 5 Jan 2001 23:46:04 +0100 [thread overview]
Message-ID: <20010105234604.C301@bug.ucw.cz> (raw)
In-Reply-To: <3A546385.C50B1092@tin.it>
In-Reply-To: <3A546385.C50B1092@tin.it>; from A.D.F. on Thu, Jan 04, 2001 at 11:50:29AM +0000
Hi!
> Hi, I would like to know whether following limits are right for kernel
> 2.4.x:
>
> Max. N. of CPU: 32 (SMP)
> Max. CPU speed: > 2 Ghz (up to ?)
> Max. RAM size: 64 GB (any slowness accessing RAM over 4 GB
> with 32 bit machines ?)
64GB on i386. I believe you can get few terabytes with ultrasparc.
> Max. file size: 1 TB (?)
> Max. file system size: 2 TB (?)
Again, maybe on i386 with ext2.
Pavel
--
I'm pavel@ucw.cz. "In my country we have almost anarchy and I don't care."
Panos Katsaloulis describing me w.r.t. patents at discuss@linmodems.org
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-08 19:41 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-04 11:50 Confirmation request about new 2.4.x. kernel limits A.D.F.
2001-01-04 11:23 ` Tigran Aivazian
2001-01-04 11:50 ` Anton Blanchard
2001-01-05 22:46 ` Pavel Machek [this message]
2001-01-09 14:03 ` Stephen C. Tweedie
-- strict thread matches above, loose matches on Subject: below --
2001-01-09 4:11 Venkatesh Ramamurthy
2001-01-09 12:21 ` Matti Aarnio
2001-01-09 16:27 ` Tim Wright
2001-01-09 16:44 ` Andi Kleen
2001-01-09 16:50 ` Tim Wright
2001-01-10 13:16 ` Kurt Garloff
2001-01-09 14:05 ` Stephen C. Tweedie
2001-01-09 15:15 Venkatesh Ramamurthy
2001-01-09 15:51 ` Andi Kleen
2001-01-09 17:35 Venkatesh Ramamurthy
2001-01-09 17:47 ` Andi Kleen
2001-01-09 18:00 Venkatesh Ramamurthy
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=20010105234604.C301@bug.ucw.cz \
--to=pavel@suse.cz \
--cc=adefacc@tin.it \
--cc=linux-kernel@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