From: Valdis.Kletnieks@vt.edu
To: Constantine Shulyupin <const@linuxdriver.co.il>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Need advice on updating the Linux kernel map
Date: Tue, 27 Apr 2010 09:41:11 -0400 [thread overview]
Message-ID: <5312.1272375671@localhost> (raw)
In-Reply-To: Your message of "Sun, 25 Apr 2010 02:02:29 +0300." <t2w8aa6b0651004241602i50449643lc05dcf834a80b344@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1209 bytes --]
On Sun, 25 Apr 2010 02:02:29 +0300, Constantine Shulyupin said:
> I was wondering if you could help me. I've recently resumed work on
> the map of the Linux kernel - http://www.makelinux.net/kernel_map in
> order to make it more up-to-date and to improve it. Please let me know
> how I can update the map, as it would help me a lot.
A few quick comments:
1) Can we do better than an OSI 7-layer burrito? ;) As it stands, doing it
that way creates a lot of things that look like layering violations. For
instance, "Device Model" is up on "virtual", when it actually gets *used*
several levels further down. And you have a *lot* of vertical lines that
cross a whole bunch of levels. You would probably be served much better
by letting each column be a lot wider, and maybe only 4 levels high (you
can probably squish virtual/bridges/logical into one wider level).
1b) Much of the I/O column should be one wide section across the bottom of
disk/network/user peripherals, and the 'system run' box should be in some
other column(s).
2) Security and debugging seem to be forced in the "user peripherals" column
for no real rational reason.
3) I see no mention of tracing/oprofile/perf.
Hope that helps...
[-- Attachment #2: Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2010-04-27 13:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-24 23:02 Need advice on updating the Linux kernel map Constantine Shulyupin
2010-04-27 13:41 ` Valdis.Kletnieks [this message]
2010-04-29 20:19 ` Constantine Shulyupin
2010-12-14 15:38 ` Constantine Shulyupin
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=5312.1272375671@localhost \
--to=valdis.kletnieks@vt.edu \
--cc=const@linuxdriver.co.il \
--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