summaryrefslogtreecommitdiff
path: root/community
diff options
context:
space:
mode:
authorSamuel Thibault <samuel.thibault@ens-lyon.org>2015-02-18 00:58:22 +0100
committerSamuel Thibault <samuel.thibault@ens-lyon.org>2015-02-18 00:58:22 +0100
commit87eedcfa99aade3d85beab8e082eb1fb7d404179 (patch)
treea8f863969fa251dac2e025dd5a95ea5568016a91 /community
parent6986ab631f26d2b72f032d6fb6b7d66e7e3b36b8 (diff)
Revert "update for rename of open_issues/profiling.mdwn to service_solahart_jakarta_selatan__082122541663/profiling.mdwn"
This reverts commit 0447d6f115c94f5815189d1be4211991ef665d9e.
Diffstat (limited to 'community')
-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 1bc343f5..6261c03e 100644
--- a/community/gsoc/project_ideas/dtrace.mdwn
+++ b/community/gsoc/project_ideas/dtrace.mdwn
@@ -19,7 +19,7 @@ problems, these are mostly just guesses. Better understanding what really
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 [[service_solahart_jakarta_selatan__082122541663/profiling]] tools could be conceived, the most promising and
+or less specific [[open_issues/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 microkernel and in the Hurd servers). This would
allow checking how much time is spent in certain modules, how often certain