aboutsummaryrefslogtreecommitdiff
path: root/community/gsoc/project_ideas/dtrace.mdwn
diff options
context:
space:
mode:
authorCarl Fredrik Hammar <hammy.lite@gmail.com>2010-03-11 13:23:12 +0100
committerCarl Fredrik Hammar <hammy.lite@gmail.com>2010-03-11 13:23:12 +0100
commit1b076ae5402eae01a4630b4a617b806806f899ce (patch)
treea9b6ac5c112cd16631548c2df457c6d987921198 /community/gsoc/project_ideas/dtrace.mdwn
parent7f786419b9c8026a8ab9e36b04fd4cadaf1fb527 (diff)
downloadweb-1b076ae5402eae01a4630b4a617b806806f899ce.tar.gz
web-1b076ae5402eae01a4630b4a617b806806f899ce.tar.bz2
web-1b076ae5402eae01a4630b4a617b806806f899ce.zip
Spell it `microkernel'
Diffstat (limited to 'community/gsoc/project_ideas/dtrace.mdwn')
-rw-r--r--community/gsoc/project_ideas/dtrace.mdwn2
1 files changed, 1 insertions, 1 deletions
diff --git a/community/gsoc/project_ideas/dtrace.mdwn b/community/gsoc/project_ideas/dtrace.mdwn
index 25e6db29..4a46cf38 100644
--- a/community/gsoc/project_ideas/dtrace.mdwn
+++ b/community/gsoc/project_ideas/dtrace.mdwn
@@ -18,7 +18,7 @@ causes bad performance is necessary to improve the situation.
For that, we need tools for performance measurements. While all kinds of more
or less specific profiling tools could be conceived, the most promising and
generic approach seems to be a framework for logging certain events in the
-running system (both in the micro kernel and in the Hurd servers). This would
+running system (both in the microkernel and in the Hurd servers). This would
allow checking how much time is spent in certain modules, how often certain
situations occur, how things interact, etc. It could also prove helpful in
debugging some issues that are otherwise hard to find because of complex