From: "M. Edward Borasky" <znmeb@aracnet.com>
To: linux-mm@kvack.org
Subject: RE: meminfo or Rephrased helping the Programmer's help themselves...
Date: Fri, 6 Sep 2002 06:44:16 -0700 [thread overview]
Message-ID: <HBEHIIBBKKNOBLMPKCBBOEIKFFAA.znmeb@aracnet.com> (raw)
In-Reply-To: <Pine.LNX.4.44L.0209061010190.1857-100000@imladris.surriel.com>
Yes, it is a high-level proposal - I adhere to the top-down philosophy of
software design, as well as the SEI standards for software engineering
process. One does not communicate about large software objects like the
Linux kernel in small manageable chunks of C code in that process. Perhaps
the fact that I insist on a design specification, requirements documents,
code reviews, etc., is the reason nobody has volunteered to join the
project.
I think a team of three could pull it off in six months; there isn't that
much kernel code that has to be done. All the hooks are there in the /proc
filesystem, they just need to be organized in a rational manner. The scheme
Windows has for PerfMon is much better than the haphazard results in the
/proc filesystem, which have been submitted over the years in "manageable
chunks". The rest of Cougar is R code - R is extremely well documented - and
database work, for which any ODBC-compliant RDB will work.
The first task that needs to be done is to develop a high-level model of the
Linux kernel. There are numerous modeling/simulation/analysis techniques
that can be used for such models. Generalized Stochastic Petri Nets (GSPNs)
are probably the best known, and I believe a related package, DSPNExpress,
is available for Linux in an academic settings. See Christoph Lindemann's
home page at
http://ls4-www.cs.uni-dortmund.de/~Lindemann/
for the details.
M. Edward (Ed) Borasky
mailto: znmeb@borasky-research.net
http://www.pdxneurosemantics.com
http://www.meta-trading-coach.com
http://www.borasky-research.net
Coaching: It's Not Just for Athletes and Executives Any More!
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/
next prev parent reply other threads:[~2002-09-06 13:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-06 6:19 John Carter
2002-09-06 12:51 ` M. Edward (Ed) Borasky
2002-09-06 13:12 ` Rik van Riel
2002-09-06 13:44 ` M. Edward Borasky [this message]
2002-09-08 22:21 ` John Carter
2002-09-09 3:02 ` M. Edward Borasky
2002-09-09 14:07 ` Eric W. Biederman
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=HBEHIIBBKKNOBLMPKCBBOEIKFFAA.znmeb@aracnet.com \
--to=znmeb@aracnet.com \
--cc=linux-mm@kvack.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