From: Jiri Slaby <jirislaby@gmail.com>
To: Someone Something <fordhaivat@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: How the heck do I get started?
Date: Sat, 21 Aug 2010 22:47:52 +0200 [thread overview]
Message-ID: <4C703B78.6080005@gmail.com> (raw)
In-Reply-To: <AANLkTi=9y=_NnC349523E_qgJ2nSk1++3Z_Phx+GMJW4@mail.gmail.com>
On 08/21/2010 07:56 PM, Someone Something wrote:
> How should
> I get started hacking on it? Writing modules, or just browsing through
> the code and trying to understand it? Any books you guys recommend?
Go through
Documentation/kernel-docs.txt
and
http://kernelnewbies.org/KernelJanitors
> 1) Does the linux kernel use pages AND segments? Or just one of them?
Speaking of x86 32-bit, both. Segments are a whole space 0-4G though, so
fairly unused except some small kind of protection. x86 64-bit removed
segmenting support.
> If its pages, how does it deal with the wasted memory at the end of
> each page? Very small pages?
Which wasted memory? No memory is wasted. If code needs memory <
PAGE_SIZE, one of slab allocator is used.
> 2) I looked at the 0.01 kernel and it has this weird mix of nasm and
> gas syntax for its assembly. Why's that?
0.01 is the ancient history, who cares?
> 3) Is there some kind of tracker for the kernel where it lists bugs and stuff?
bugzilla.kernel.org
And some reports are reported solely to this (or other) ML.
> 4) If I do have a patch I'd like to submit, how would I do this?
See
Documentation/SubmittingPatches
And Documentation/00-INDEX is of interest usually.
hth,
--
js
prev parent reply other threads:[~2010-08-21 20:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-21 17:56 How the heck do I get started? Someone Something
[not found] ` <20100822042525.7168ac37.lisa@ltmnet.com>
[not found] ` <AANLkTin22E7zF0aomc+t23X7bETzNv-WgLivV_j98+dq@mail.gmail.com>
2010-08-21 19:26 ` Someone Something
2010-08-21 19:32 ` Someone Something
2010-08-21 20:47 ` Jiri Slaby [this message]
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=4C703B78.6080005@gmail.com \
--to=jirislaby@gmail.com \
--cc=fordhaivat@gmail.com \
--cc=linux-kernel@vger.kernel.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