Date: Fri, 7 Dec 2007 12:02:21 +0100 From: "Gerald Heinig" <gheinig@marvell.com> To: "Ivan Voras" <ivoras@freebsd.org>, <freebsd-hackers@freebsd.org> Subject: RE: Large array in KVM Message-ID: <4D634BCFD1A2144ABECC75FF512D7A9001DF60BF@SKGExch01.marvell.com>
next in thread | raw e-mail | index | archive | help
> 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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4D634BCFD1A2144ABECC75FF512D7A9001DF60BF>