From owner-freebsd-questions  Mon Jul 13 17:18:41 1998
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id RAA14520
          for freebsd-questions-outgoing; Mon, 13 Jul 1998 17:18:41 -0700 (PDT)
          (envelope-from owner-freebsd-questions@FreeBSD.ORG)
Received: from eagle.ns.net (root@eagle.ns.net [204.75.146.20])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA14490
          for <questions@FreeBSD.ORG>; Mon, 13 Jul 1998 17:18:33 -0700 (PDT)
          (envelope-from rfg@monkeys.com)
Received: from monkeys.com (rfg.ns.net [207.159.10.82])
	by eagle.ns.net (8.8.5/8.8.5) with ESMTP id RAA22474;
	Mon, 13 Jul 1998 17:18:25 -0700 (PDT)
Received: from monkeys.com (localhost [127.0.0.1])
	by monkeys.com (8.8.8/8.8.5) with ESMTP id RAA11764;
	Mon, 13 Jul 1998 17:20:29 -0700
To: Doug White <dwhite@resnet.uoregon.edu>
cc: questions@FreeBSD.ORG
Subject: Re: What to do about limited caching on 430FX chipset (?) 
In-reply-to: Your message of Mon, 13 Jul 1998 14:27:31 -0700.
             <Pine.BSF.3.96.980713142626.25570z-100000@resnet.uoregon.edu> 
X-Copyright: (c) 1998 Ronald F. Guilmette; All rights reserved.
Date: Mon, 13 Jul 1998 17:20:29 -0700
Message-ID: <11762.900375629@monkeys.com>
From: "Ronald F. Guilmette" <rfg@monkeys.com>
Sender: owner-freebsd-questions@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


In message <Pine.BSF.3.96.980713142626.25570z-100000@resnet.uoregon.edu>, you w
rote:

>On Mon, 13 Jul 1998, Ronald F. Guilmette wrote:
>
>> Is there any way, short of removing 64MB of memory from this system, that
>> I can convince the FreeBSD kernel to avoid allocating space for programs
>> and data in the upper 64MB on this system if it can be avoided?  I mean
>> ideally, that upper 64MB would be used only for stuff like the disk buffer
>> cache and perhaps other not-too-time-sensitive stuff... unless of course
>> the kernel really has no other choice but to use that for programs and
>> associated data (because it has run out of run for such stuff in the lower
>> 64MB).
>
>You can try using the MAXMEM option to your kernel to define the maximum
>amount of memory the system is to use as 64MB, but then your other 64MB of
>RAM sits rotting.

Thanks for the tip.  I may perhaps just try setting MAXMEM and then rerunning
the application just to see if my suspicions about the non-caching of the
upper 64MB are in fact what is making the performance of this program suck.


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message