From: Blake Caldwell <blake@pluginbox.com>
To: unlisted-recipients:; (no To-header on input)
Cc: "(linux-kernel@vger.kernel.org)" <linux-kernel@vger.kernel.org>
Subject: Re: linux kernel scheduler
Date: Wed, 24 Dec 2003 14:38:18 -0500 [thread overview]
Message-ID: <3FE9EB2A.6060403@pluginbox.com> (raw)
In-Reply-To: <3BEEE23D31CAD2118D920008C75D8946059FF5A1@NPRI54EXC21.NPT.NUWC.NAVY.MIL>
is it this one? I'm looking for such a book that covers the 2.6 kernel
http://www.amazon.com/exec/obidos/tg/detail/-/0672325128/qid=1072294583//ref=sr_8_xs_ap_i0_xgl14/002-2050823-6096828?v=glance&s=books&n=507846
thx
- blake
Pacheco Jason NPRI wrote:
>>Is there any document or book where I can
>>find this kind of information ?
>
>
> I recently purchased "Linux Kernel Development" by Robert Love. I
> haven't finished it yet, but so far I would give it great reviews.
> It has a very simple style and is easy to understand. The book solely
> covers the 2.6 kernel and explains where it differentiates from the
> earlier kernels. Chapter 3 is dedicated to Scheduling and will
> give you all the information you need as far as how the 2.6 kernel
> does scheduling. For the 2.4 kernel there is plenty of documentation
> available on that already.
> -
> 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/
>
>
next prev parent reply other threads:[~2003-12-24 19:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-24 17:11 linux kernel scheduler Pacheco Jason NPRI
2003-12-24 19:38 ` Blake Caldwell [this message]
2003-12-24 19:38 ` Blake Caldwell
-- strict thread matches above, loose matches on Subject: below --
2003-12-25 1:18 Felipe Alfaro Solana
2003-12-24 20:40 Pacheco Jason NPRI
2003-12-24 16:00 Yoann
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=3FE9EB2A.6060403@pluginbox.com \
--to=blake@pluginbox.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