From owner-freebsd-hackers  Sun Aug 19 13:50:19 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from netbank.com.br (garrincha.netbank.com.br [200.203.199.88])
	by hub.freebsd.org (Postfix) with ESMTP
	id CAE3D37B411; Sun, 19 Aug 2001 13:50:14 -0700 (PDT)
	(envelope-from riel@conectiva.com.br)
Received: from 1-083.ctame701-1.telepar.net.br (1-083.ctame701-1.telepar.net.br [200.181.137.83])
	by netbank.com.br (Postfix) with ESMTP
	id 95C5A46804; Sun, 19 Aug 2001 17:49:07 -0300 (BRST)
Received: from localhost ([IPv6:::ffff:127.0.0.1]:36790 "EHLO localhost")
	by imladris.surriel.com with ESMTP id <S160116AbRHSUuJ>;
	Sun, 19 Aug 2001 17:50:09 -0300
Date:	Sun, 19 Aug 2001 17:50:08 -0300 (BRST)
From: Rik van Riel <riel@conectiva.com.br>
X-X-Sender:  <riel@imladris.rielhome.conectiva>
To: Matt Dillon <dillon@earth.backplane.com>
Cc: David Greenman <dg@root.com>,
	Sergey Babkin <babkin@bellatlantic.net>, <hackers@FreeBSD.ORG>,
	<murray@FreeBSD.ORG>, <jkh@FreeBSD.ORG>
Subject: Re: Recommendation for minor KVM adjustments for the release
In-Reply-To: <200108191853.f7JIrAP45731@earth.backplane.com>
Message-ID: <Pine.LNX.4.33L.0108191749140.5646-100000@imladris.rielhome.conectiva>
X-spambait: aardvark@kernelnewbies.org
X-spammeplease:	aardvark@nl.linux.org
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hackers.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG

On Sun, 19 Aug 2001, Matt Dillon wrote:

> :   Uh, I don't think you understand what this limit is about. It's
> :essentially the limit on the amount of filesystem directory data that
> :can be cached. It does not limit the amount of file data that can
> :be cached - that is only limited by the amount of RAM in the machine.

>     Yes, and the buffer cache determines how much dirty file-backed data
>     (via write() or mmap()) the system is allowed to accumulate before
>     it forces it out, which should probably be the greater concern here.

How hard would it be to allow dirty data in the file
cache, without buffer mappings ?

regards,

Rik
--
IA64: a worthy successor to i860.

http://www.surriel.com/		http://distro.conectiva.com/

Send all your spam to aardvark@nl.linux.org (spam digging piggy)


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