From owner-freebsd-mips@FreeBSD.ORG Sun Jul 25 11:30:51 2010 Return-Path: Delivered-To: mips@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 177BE1065677 for ; Sun, 25 Jul 2010 11:30:51 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (bsdimp.com [199.45.160.85]) by mx1.freebsd.org (Postfix) with ESMTP id EFEFF8FC22 for ; Sun, 25 Jul 2010 11:30:50 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by harmony.bsdimp.com (8.14.3/8.14.1) with ESMTP id o6PBPqcZ040239; Sun, 25 Jul 2010 05:25:53 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Sun, 25 Jul 2010 05:26:29 -0600 (MDT) Message-Id: <20100725.052629.160100930644600654.imp@bsdimp.com> To: c.jayachandran@gmail.com From: "M. Warner Losh" In-Reply-To: References: <201007250419.o6P4J50q033283@svn.freebsd.org> <4C4BC213.5060001@cs.rice.edu> X-Mailer: Mew version 6.3 on Emacs 22.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Cc: mips@freebsd.org, alc@cs.rice.edu Subject: Re: svn commit: r210460 - head/sys/mips/include X-BeenThere: freebsd-mips@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to MIPS List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Jul 2010 11:30:51 -0000 In message: "Jayachandran C." writes: : On Sun, Jul 25, 2010 at 10:18 AM, Alan Cox wrote: : > Warner Losh wrote: : >> : >> Author: imp : >> Date: Sun Jul 25 04:19:05 2010 : >> New Revision: 210460 : >> URL: http://svn.freebsd.org/changeset/base/210460 : >> : >> Log: : >> =A0Get N64 building by defining VM_FREELIST_DIRECT to be : >> =A0VM_FREELIST_DEFAULT. =A0I believe this is correct, since KX is = set in : >> =A0n64, and thus all RAM can be direct mapped. : = : Thanks, this is something I missed in my MIPS page table changes. : = : > : > Yes, it is. : = : In MIPS 64bit, whole physical memory is direct mapped thru a XKPHYS : region. We can use vm_page_alloc() for pmap_alloc_pte_page() and : VM_WAIT for pmap_grow_pte_page_cache(), is this something we should : consider? Likely. Any idea what kind of performance difference this would buy us? Warner