Date: Tue, 27 Jan 1998 17:18:56 +1030 From: Mike Smith <mike@smith.net.au> To: "Daniel O'Connor" <doconnor@cain.gsoft.com.au> Cc: joelh@gnu.org, mike@smith.net.au, dag-erli@ifi.uio.no, hackers@FreeBSD.ORG Subject: Re: File I/O in kernel land (was: Re: 2nd warning: 2.2.6 BETA begins in 10 days!) Message-ID: <199801270648.RAA01893@word.smith.net.au> In-Reply-To: Your message of "Tue, 27 Jan 1998 17:21:32 %2B1030." <199801270651.RAA29592@cain.gsoft.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
> > > My real concern is holding on to lots of dynamically allocated kernel > > memory, which is something I can't see getting around without the > > screen saver doing file I/O. In Linux, dynamic kernel memory was a > > precious resource. Is it not so in FreeBSD? > Umm, well wouldn't it be allocated in either case? > You either load it in the kernel, or you load it in user land, and then copy > it to the kernel.. You still take kernel memory to do it. Actually, if you're a real stud, you hold an open vnode reference on it, and read it off the disk every time you want to display it. As Julian said, see how the code in the kernel handles reading executable images. It's moderately painful, but definitely the Right Way to do it. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199801270648.RAA01893>