From: martinez.javier@gmail.com (Javier Martinez Canillas)
To: kernelnewbies@lists.kernelnewbies.org
Subject:
Date: Thu, 16 Jun 2011 20:55:40 +0900 [thread overview]
Message-ID: <BANLkTi=pT99A1H6z2TVxPdk-s-cK-=NhxQ@mail.gmail.com> (raw)
In-Reply-To: <BANLkTikfuEcP1UJvse-wCJVXmCL-ehNFog@mail.gmail.com>
On Thu, Jun 16, 2011 at 8:41 PM, Venkateswarlu P
<p.venkatesh551@gmail.com> wrote:
> how to understand the kernerl source? files in a simple way
>
>
> what header? files i have to understand first
>
>
> for example? to understand????? do_fork()???? function? for process
> creation? which is defined in? kernel/fork.c
>
In the end the Linux kernel is just a big project written in C.
Instead of asking what files do you need to understand. You should ask
yourself what subsystem do you want to learn?
Focus on functionality and browse the code to understand. As others
pointed before there are lots of good books that will give you a high
overview of the kernel.
The first book that I recommend reading is Linux kernel development by
Robert Love, but only if you have already read a book on operating
system concepts. The best book for me is Andrew Tanenbaum's Modern
Operating Systems.
Hope it helps,
--
Javier Mart?nez Canillas
(+34) 682 39 81 69
PhD Student in High Performance Computing
Computer Architecture and Operating System Department (CAOS)
Universitat Aut?noma de Barcelona
Barcelona, Spain
next prev parent reply other threads:[~2011-06-16 11:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-16 11:41 No subject Venkateswarlu P
2011-06-16 11:47 ` Anuz Pratap Singh Tomar
2011-06-16 11:55 ` Javier Martinez Canillas [this message]
2011-06-16 13:19 ` Anand Arumugam
2011-06-16 15:37 ` Anand Moon
2011-06-19 21:25 ` abhijeet tripathi
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='BANLkTi=pT99A1H6z2TVxPdk-s-cK-=NhxQ@mail.gmail.com' \
--to=martinez.javier@gmail.com \
--cc=kernelnewbies@lists.kernelnewbies.org \
/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).