From owner-freebsd-hackers@FreeBSD.ORG Fri Dec 7 11:02:24 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6B2EB16A41A for ; Fri, 7 Dec 2007 11:02:24 +0000 (UTC) (envelope-from gheinig@marvell.com) Received: from maili.marvell.com (host2.marvell.com [65.219.4.2]) by mx1.freebsd.org (Postfix) with ESMTP id 54E0813C46A for ; Fri, 7 Dec 2007 11:02:24 +0000 (UTC) (envelope-from gheinig@marvell.com) Received: from MSI-MTA.marvell.com (msi-mta.marvell.com [10.68.76.91]) by maili.marvell.com (Postfix) with ESMTP id 350EF1A2FA; Fri, 7 Dec 2007 03:02:24 -0800 (PST) Received: from SKGExch01.marvell.com ([10.9.116.16]) by MSI-MTA.marvell.com with Microsoft SMTPSVC(6.0.3790.3959); Fri, 7 Dec 2007 03:02:24 -0800 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Fri, 7 Dec 2007 12:02:21 +0100 Message-ID: <4D634BCFD1A2144ABECC75FF512D7A9001DF60BF@SKGExch01.marvell.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Large array in KVM Thread-Index: Acg4vjo5plfu5W/lTee0JFw3oAp4CQAAPhWw From: "Gerald Heinig" To: "Ivan Voras" , X-OriginalArrivalTime: 07 Dec 2007 11:02:24.0008 (UTC) FILETIME=[A5695880:01C838C0] Cc: Subject: RE: Large array in KVM X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Dec 2007 11:02:24 -0000 > Gerald Heinig wrote: >=20 > > How about implementing your code as a system call, which is called from > > a process that maps a large file into memory, as you suggested above. >=20 > What if the code is a device driver? I'm just assuming it isn't a device driver. Sonja (the original poster) just mentioned 'a kernel module'. It might be worth asking what exactly this module does and why it would need to be implemented as a kernel module if it needs so much memory. If it's a device driver, what is it driving? The only hardware that springs to mind which might need large amounts of memory is a camera driver or some high-speed sampling device.