public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: alad@hss.hns.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: fcgp understanding
Date: Sun, 05 Aug 2001 14:19:18 +1000	[thread overview]
Message-ID: <E15TFNq-0008V2-00@localhost> (raw)
In-Reply-To: Your message of "Tue, 31 Jul 2001 13:49:16 +0530." <65256A9A.002DAB65.00@sandesh.hss.hns.com>

In message <65256A9A.002DAB65.00@sandesh.hss.hns.com> you write:
> Hi,
>      Can somone please explain in brief -- How to read fcgp ( Free coding
> graphical project) for a
> particular file. One such map (for mmap.c) is at --
> http://fcgp.sourceforge.net/images/mm_mmap.c.png

This is off-topic, but maybe one canonical answer will stop others.

	The solid line (around the top and right edges) is a C file,
labelled on the bottom left.  The dashed lines means a function,
labelled on the bottom left.  Light green functions are file-local
(static).  Red functions are exported to modules.  Dark green
functions are called through a pointer.  Other functions are blue.

	Within each function, the circles are loops, the branches are
conditional statements (if, switch, ?:).  The loops approximately
circle the code they loop around.

	So, we can see that do_munmap looks like a loop around a whole
heap of little branchy code.  Indeed, looking at the code in mm/mmap.c,
half the function is a loop.

Hope that helps,
Rusty.
--
Premature optmztion is rt of all evl. --DK

      reply	other threads:[~2001-08-05  4:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-31  8:19 fcgp understanding alad
2001-08-05  4:19 ` Rusty Russell [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=E15TFNq-0008V2-00@localhost \
    --to=rusty@rustcorp.com.au \
    --cc=alad@hss.hns.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