From: "lk" <linux_kernel@patni.com>
To: Ram S <linux_guy_76@yahoo.com>, linux-c-programming@vger.kernel.org
Subject: Re: Good book
Date: Tue, 24 May 2005 10:36:21 +0530 [thread overview]
Message-ID: <000801c5601e$5612b880$5e91a8c0@patni.com> (raw)
In-Reply-To: 20050524034750.70100.qmail@web51307.mail.yahoo.com
>I am a new to linux. While going through the kernel
>code, I saw couple of routines beginning with __ e.g
> __init free_all_bootmem_core (in mm/bootmem.c). Any
>specific reason why it is so ?
usually the methods starting with __ are the core routines & there would be
some wrapper to it..
say do_page_fault(); is a wrapper which internally calls __do_page_fault();
The __init token in the definition may look a little strange; it is a hint
to the kernel that the given function is
used only at initialization time. The module loader drops the initialization
function after the module is loaded, making its memory available for other
uses.
There is a similar tag (__initdata)for data used only during initialization.
You may also encounter __devinit and __devinitdata in the kernel source;
these translate to __init and __initdata only if the kernel has not been
configured for
hotpluggable devices.
>I know this may be a
>very basic thing that I am asking and I need to to
>read more. Can you point to me some good book which
>I can refer and get some of the basic doubts
>clarified ?
1] "Understanding the linux kernel" by "Bovet & Cesati " is a good book to
get the insight of kernel...
you can also look at some ebooks like..
2] Linux Kernel 2.4 Internals by Tigran Aivazian tigran@veritas.com
http://www.linuxdoc.org/guides.html
3]Linux Kernel Hackers Guide..
regqrds
lk
next prev parent reply other threads:[~2005-05-24 5:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-24 3:47 Good book Ram S
2005-05-24 5:06 ` lk [this message]
2005-05-25 7:08 ` kerel level threads K. Anantha Kiran
2005-05-25 9:06 ` Steven Smith
2005-05-25 11:46 ` Glynn Clements
2005-05-25 11:57 ` Glynn Clements
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='000801c5601e$5612b880$5e91a8c0@patni.com' \
--to=linux_kernel@patni.com \
--cc=linux-c-programming@vger.kernel.org \
--cc=linux_guy_76@yahoo.com \
/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;
as well as URLs for NNTP newsgroup(s).