From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S934123Ab0D3Sf7 (ORCPT ); Fri, 30 Apr 2010 14:35:59 -0400 Received: from mail-bw0-f219.google.com ([209.85.218.219]:61846 "EHLO mail-bw0-f219.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S934110Ab0D3Sfm convert rfc822-to-8bit (ORCPT ); Fri, 30 Apr 2010 14:35:42 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; b=w1aPXpszLVY2fX0CVikZRJLfLhIy5ODaafvVNL56OA6zAafU92s09PL4/RZJSQI2aE eUFdK76qQEi58fbDl3KdmxDeNkXlNCV5yOxcU2Kac4knMvlxFU65UtU5Y85FqOvdts9M nZgi9X0py6fcDdvG3DLl4RugC9GYQBF5vxdGY= MIME-Version: 1.0 In-Reply-To: <5312.1272375671@localhost> References: <5312.1272375671@localhost> Date: Thu, 29 Apr 2010 23:19:38 +0300 X-Google-Sender-Auth: ce390e20b1fa4a1e Message-ID: Subject: Re: Need advice on updating the Linux kernel map From: Constantine Shulyupin To: Valdis.Kletnieks@vt.edu Cc: linux-kernel@vger.kernel.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Valdis, Thank you for your comments! Is very helpful! On Tue, Apr 27, 2010 at 4:41 PM, wrote: > 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... > -- Constantine Shulyupin Embedded Linux Expert TI DaVinci Expert Tel-Aviv Israel http://www.LinuxDriver.co.il/