From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from ar.aichi-u.ac.jp ([202.250.160.40]) by ttr; Mon Apr 28 12:50:12 EDT 2014
Received: from [192.168.1.110] ([125.192.161.78]) by ar; Mon Apr 28 19:52:54 JST 2014
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
Subject: cwfs fsmempercent
From: arisawa <arisawa@ar.aichi-u.ac.jp>
In-Reply-To: <9b527eeb4e8d99739805d55a327db989@x230.inri>
Date: Mon, 28 Apr 2014 19:52:54 +0900
Content-Transfer-Encoding: quoted-printable
Message-Id: <EF1793BB-86E2-4C54-979F-9117C2952EC5@ar.aichi-u.ac.jp>
List-ID: <9front.9front.org>
X-Glyph: ➈
X-Bullshit: base property content-driven controller
References: <9b527eeb4e8d99739805d55a327db989@x230.inri>
To: 9front@9front.org
X-Mailer: Apple Mail (2.1874)

Hello,

recent cwfs restricts memory size to 1GB max to be allocated to cwfs.
is there any reason to restrict the value?
nowadays we have much memory such as 16GB on MB.
I would be happier if I can allocate much memory to cwfs.

Kenji Arisawa

/sys/src/cmd/cwfs/malloc.c
static ulong
memsize(void)
{
	...
		userpgs =3D (userpgs*mpcnt)/100;
		pgmax =3D (1024*1024*1024)/pgsize;	/* 1GB max */
		if(userpgs > pgmax)
			userpgs =3D pgmax;
		return userpgs*pgsize;
	=E2=80=A6
}