From: Rob Landley <rob@landley.net>
To: corbet@lwn.net (Jonathan Corbet), "Lars Unin" <lars_unin@linuxmail.org>
Cc: linux-kernel@vger.kernel.org, rgooch@atnf.csiro.au
Subject: LKML FAQ updating (was: Re: kernel spinlocks; when to use; when appropriate?)
Date: Tue, 10 Jun 2003 13:57:30 -0400 [thread overview]
Message-ID: <200306101357.30908.rob@landley.net> (raw)
In-Reply-To: <20030609155051.22121.qmail@eklektix.com>
Okay, that link needs to go in the "basic linux kernel documentation" section
at the start of the "http://www.tux.org/lkml/" faq, along with some other
resources that have fallen through the cracks. I'd happily generate a patch
against the FAQ, but haven't a clue what the source format is. (Is it
hand-hacked HTML?)
Documentation resources:
Linux Device Drivers, second edition (whole book online).
http://www.xml.com/ldd/chapter/book/index.html
Porting device drivers to 2.5 (30-article series):
http://lwn.net/Articles/driver-porting/
Linux Kernel Internals (walkthrough of kernel 2.4 source):
http://www.moses.uklinux.net/patches/lki.html
Mel Gorman's Virtual Memory Guides (read "understanding" first, then
"coding"):
http://www.csn.ul.ie/~mel/projects/vm/guide/
Also, the "asking smart questions" thing isn't on tuxedo.org anymore, it's on
catb.org. (Otherwise same URL.)
And while we're on the subject, could the mention of the Documentation
directory in the linux kernel source A) be moved to the start of the list, B)
be updated to include a mention of "make htmldocs" and friends?
I'm sure there's more, this is just off the top of my head. I'd be happy to
whip up a patch if I had a clue what file it should be against...
Rob
On Monday 09 June 2003 11:50, Jonathan Corbet wrote:
> > When is is appropriate to use spinlocks in the kernel,
> > how are they implemented (e.g. syntax, function names) and
> > can anyone think of a good area of the kernel for me to look
> > at, that uses them?
>
> May I humbly suggest a look at Linux Device Drivers, Second Edition? It
> goes over locking primitives in a fair amount of detail, and includes
> examples of their use. Available freely online at:
>
> http://www.xml.com/ldd/chapter/book/index.html
>
> or in your favorite bookstore.
>
> jon
>
> Jonathan Corbet
> Executive editor, LWN.net
> corbet@lwn.net
> -
> 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/
prev parent reply other threads:[~2003-06-10 17:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-09 15:43 kernel spinlocks; when to use; when appropriate? Lars Unin
2003-06-09 15:50 ` Jonathan Corbet
2003-06-10 17:57 ` Rob Landley [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=200306101357.30908.rob@landley.net \
--to=rob@landley.net \
--cc=corbet@lwn.net \
--cc=lars_unin@linuxmail.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rgooch@atnf.csiro.au \
/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