From owner-freebsd-hackers Thu Oct 28 19:29:10 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from usc.edu (usc.edu [128.125.253.136]) by hub.freebsd.org (Postfix) with ESMTP id 079A314EFF for ; Thu, 28 Oct 1999 19:29:05 -0700 (PDT) (envelope-from walker@usc.edu) Received: from skat.usc.edu (root@skat.usc.edu [128.125.253.131]) by usc.edu (8.9.3.1/8.9.3/usc) with ESMTP id TAA20855; Thu, 28 Oct 1999 19:29:02 -0700 (PDT) Received: from cohiba.usc.edu (cohiba.usc.edu [128.125.29.205]) by skat.usc.edu (8.9.3.1/8.9.3/usc) with ESMTP id TAA20264; Thu, 28 Oct 1999 19:29:01 -0700 (PDT) Date: Thu, 28 Oct 1999 19:28:58 -0700 (Pacific Daylight Time) From: Michael Walker To: hackers@FreeBSD.ORG Cc: Michael Beckmann Subject: Re: Limitations in FreeBSD In-Reply-To: <19991029011348.B2757@apfel.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Here is the problem: > When you want to have 500 GB of storage, you will need 250 files. In the = current > implementation of nnrpd, this will need 250 file descriptors per nnrpd. T= his will > limit the number of readers that can be supported on a system, because a = nnrpd is > spawned for each reader. I was told that nnrpd can be hacked to only cons= ume file > descriptors when really needed, but it=B4s supposed to have a performance= penalty. > That=B4s why I=B4m looking for a way of having large mmap=B4able files. A= re you saying > that ALL Intel CPUs, including PIII, can only address 4 GB? I probably ne= ed to > look at other architectures or solve this fd problem. >=20 > Michael Is FreeBSD available for Alpha's 64 bit arch (1.8e19)? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message