From owner-freebsd-hackers Fri Feb 19 21:22: 8 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from obie.softweyr.com (unknown [204.68.178.33]) by hub.freebsd.org (Postfix) with ESMTP id B3F8B1161A for ; Fri, 19 Feb 1999 21:22:05 -0800 (PST) (envelope-from wes@softweyr.com) Received: from softweyr.com (zaphod.softweyr.com [204.68.178.35]) by obie.softweyr.com (8.8.8/8.8.8) with ESMTP id WAA18122; Fri, 19 Feb 1999 22:21:51 -0700 (MST) (envelope-from wes@softweyr.com) Message-ID: <36CE466E.E29A845A@softweyr.com> Date: Fri, 19 Feb 1999 22:21:50 -0700 From: Wes Peters Organization: Softweyr llc X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 3.0-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Terry Lambert Cc: Dag-Erling Smorgrav , hackers@FreeBSD.ORG Subject: Re: [Alfred Perlstein ] Re: vm_page_zero_fill References: <199902200050.RAA15634@usr02.primenet.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Terry Lambert wrote: > > I think that we would do well to provide C code, wherever possible, > for all assmebly language code, no matter how suboptimal this ends > up being. > > The reason for this is portability to new platforms becomes more > immediate, though less optimal. The assembly code can later be > "back filled", as necessary, as an optimization. > > The ugliest place for this type of thinking is locore.s and the bios > crap, but it would speed inclusion of new platforms, and is probably > worth the effort. Depending on the architecture in question, this might not even be that much of a loss. Architectures that have ONLY memory-mapped I/O, for instance, suffer less from low-level C code. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC http://www.softweyr.com/~softweyr wes@softweyr.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message