From: Lee Revell <rlrevell@joe-job.com>
To: lya755@ece.northwestern.edu
Cc: "H. Peter Anvin" <hpa@zytor.com>, linux-kernel@vger.kernel.org
Subject: Re: question about ramdisk
Date: Tue, 13 Jul 2004 17:27:08 -0400 [thread overview]
Message-ID: <1089754028.22175.10.camel@mindpipe> (raw)
In-Reply-To: <1089749203.22026.17.camel@mindpipe>
Sorry, Robert Love's book is 'Linux Kernel Development'.
http://www.amazon.com/exec/obidos/tg/detail/-/0672325128/ref=pd_sim_books_2/002-8634838-0327232?v=glance&s=books
Lee
On Tue, 2004-07-13 at 16:06, Lee Revell wrote:
> "Unix Internals", by Uresh Vahalia (sp?). This book went everywhere I
> did for a year. I cannot praise it highly enough. Read that, then get
> Robert Love's 'Linux Kernel Programming'.
>
> Lee
>
> On Tue, 2004-07-13 at 10:01, lya755@ece.northwestern.edu wrote:
> > Thank you! Can you pls tell me where I can find related references? I've been
> > looking into several books about kernel and part of the kernel code, but no
> > luck so far..
> >
> > Thanks for any comments!
> >
> > Quoting "H. Peter Anvin" <hpa@zytor.com>:
> >
> > > Followup to: <1089651469.40f2c30d44364@core.ece.northwestern.edu>
> > > By author: lya755@ece.northwestern.edu
> > > In newsgroup: linux.dev.kernel
> > > >
> > > > Hi all,
> > > >
> > > > I am learning linux kernel and have a question about ramdisk. When loading
> > > an
> > > > executable in ramdisk, is the kernel loading the code all at a time to
> > > memory
> > > > and then execute, or is it loading only a page at one time and generating a
> > >
> > > > page fault to fetch another page?
> > > >
> > > > Thanks for any comments! Waiting desprately for your help.
> > > >
> > >
> > > Neither. The code is already in RAM. It's mapped into the process
> > > address space and run in place.
> > >
> > > -hpa
> > > -
> > > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> > > the body of a message to majordomo@vger.kernel.org
> > > More majordomo info at http://vger.kernel.org/majordomo-info.html
> > > Please read the FAQ at http://www.tux.org/lkml/
> > >
> >
> >
> >
> > _________________________________________________________
> > This message was sent through the NU ECE webmail gateway.
> > -
> > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at http://vger.kernel.org/majordomo-info.html
> > Please read the FAQ at http://www.tux.org/lkml/
> >
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
next prev parent reply other threads:[~2004-07-13 21:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-12 16:57 question about ramdisk lya755
2004-07-12 17:13 ` H. Peter Anvin
2004-07-13 14:01 ` lya755
2004-07-13 20:06 ` Lee Revell
2004-07-13 21:27 ` Lee Revell [this message]
[not found] ` <1089753034.40f44fca074c2@core.ece.northwestern.edu>
[not found] ` <1089753955.22175.8.camel@mindpipe>
2004-07-14 14:59 ` lya755
2004-07-14 16:07 ` Richard B. Johnson
2004-07-14 16:30 ` lya755
2004-07-14 16:57 ` Richard B. Johnson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1089754028.22175.10.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lya755@ece.northwestern.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox