On Sat, 29 Apr 2006 00:54:28 +0300, khaled MOHAMMED atteya said: > HELLO > I hope to be kernel developer ,in i386 arch. Do you plan to be actively developing code in the arch/i386 tree, or are you just developing on systems that happen to be x86 boxes? The difference is crucial. > am i needing to read all i386 and pentium manual (the three volume)? There's large portions of the kernel ( fs/* and net/* in particular) that are largely CPU-agnostic. Much more important overall is understanding the basic *concepts* of barriers (why you need them, when, and where), and trusting the provided macros to Do The Right Thing when you use the right macro (conversely, using the *wrong* macro is an error no matter what architecture you're on). That, and locking. Understanding locking is another things more important than the actual CPU registers. And you need to get a grip on both of those concepts before starting to deal with architecture-dependent code (of which there's an amazingly small amount).
Attachment:
pgpVeTYKIS7Ky.pgp
Description: PGP signature
- Follow-Ups:
- Re: I hope to be kernel developer ,in i386 arch
- From: Alan Camus <[email protected]>
- Re: I hope to be kernel developer ,in i386 arch
- References:
- I hope to be kernel developer ,in i386 arch
- From: "khaled MOHAMMED atteya" <[email protected]>
- I hope to be kernel developer ,in i386 arch
- Prev by Date: Re: I hope to be kernel developer ,in i386 arch
- Next by Date: [git pull] Input update for 2.6.17-rc3
- Previous by thread: Re: I hope to be kernel developer ,in i386 arch
- Next by thread: Re: I hope to be kernel developer ,in i386 arch
- Index(es):
 |