On Wed, 17 Oct 2001, Norm Dresner wrote: > Calin. > > No offense intended. I was just trying to point out that ^^ you could have fooled me.
> there are many resources out there which will answer all > kinds of questions (basic and otherwise) about Linux kernel > programming, and that I thought that the Rubini book was > the best investment. Ok, advice noted. I did buy that Linux Kernel Internals book but it's pretty much utter rubbish. -Calin > > Norm > > ----- Original Message ----- > From: Calin A. Culianu <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Wednesday, October 17, 2001 6:29 PM > Subject: RE: [rtl] Locking Memory in Kernel > > > > > > Norm. > > > > Why do you always assume the most basic stupid things > about my questions? > > I wasn't asking how to write a kernel module. I have > written many in my > > lifetime. Re-read my question please. Despite what you > think, you aren't > > infinitely smarter than everyone here. > > > > What I was asking was how do you make sure that the > memory is available > > immediately (or relatively so) so that by the time your > real-time thread > > is created the memory is there, in ram, and cannot be > swapped out. > > > > *Sheesh* > > > > > > -Calin > > > > > > On Tue, 16 Oct 2001, Dresner, > > Norman A. wrote: > > > > > Calin. > > > > > > The init_module() function runs as part of the normal > Linux kernel. > > > Therefore the all of the "usual" kernel mechanisms are > available, in > > > particular kmalloc(). If you can't find a man-page, > there are a few > > > web-sites with moderate kernel "hacking" guides but IMO > the best source for > > > kernel programming information is in Rubini's book > (O'Reilly) and apparently > > > the entire text of the second edition is available > on-line. I have the 1st > > > ed. (I just haven't gotten around to upgrading yet). > It's a fine text that > > > I use "all the time" and I heartily recommend it. > > > > > > Norm > > > > > > > -----Original Message----- > > > > From: Calin A. Culianu [SMTP:[EMAIL PROTECTED]] > > > > Sent: Tuesday, October 16, 2001 8:39 AM > > > > To: [EMAIL PROTECTED] > > > > Subject: [rtl] Locking Memory in Kernel > > > > > > > > > > > > Hey, this may be a basic question, but what steps > should a programmer take > > > > when allocating memory in a real-time module during > init_module() to > > > > ensure that the memory is A) available more-or-less > immediately and needs > > > > not be paged-in-on-use and B) the memory stays locked > in RAM. > > > > > > > > -Calin > > > > > > > > -- [rtl] --- > > > > To unsubscribe: > > > > echo "unsubscribe rtl" | mail [EMAIL PROTECTED] > OR > > > > echo "unsubscribe rtl <Your_email>" | mail > [EMAIL PROTECTED] > > > > -- > > > > For more information on Real-Time Linux see: > > > > http://www.rtlinux.org/ > > > -- [rtl] --- > > > To unsubscribe: > > > echo "unsubscribe rtl" | mail [EMAIL PROTECTED] OR > > > echo "unsubscribe rtl <Your_email>" | mail > [EMAIL PROTECTED] > > > -- > > > For more information on Real-Time Linux see: > > > http://www.rtlinux.org/ > > > > > > > -- [rtl] --- > > To unsubscribe: > > echo "unsubscribe rtl" | mail [EMAIL PROTECTED] OR > > echo "unsubscribe rtl <Your_email>" | mail > [EMAIL PROTECTED] > > -- > > For more information on Real-Time Linux see: > > http://www.rtlinux.org/ > > > > -- [rtl] --- > To unsubscribe: > echo "unsubscribe rtl" | mail [EMAIL PROTECTED] OR > echo "unsubscribe rtl <Your_email>" | mail [EMAIL PROTECTED] > -- > For more information on Real-Time Linux see: > http://www.rtlinux.org/ > -- [rtl] --- To unsubscribe: echo "unsubscribe rtl" | mail [EMAIL PROTECTED] OR echo "unsubscribe rtl <Your_email>" | mail [EMAIL PROTECTED] -- For more information on Real-Time Linux see: http://www.rtlinux.org/
