about summary refs log tree commit diff
diff options
context:
space:
mode:
authorLaurent Bercot <ska-skaware@skarnet.org>2021-04-15 14:13:13 +0000
committerLaurent Bercot <ska-skaware@skarnet.org>2021-04-15 14:13:13 +0000
commit1e0fbba7c270701b4f27f808be988b63118d9533 (patch)
tree84a2a9de169051ad895110e86c5c4bf67403665d
parentc90d001c7b9c828a57ccd59690f4caa8628c1ac9 (diff)
downloadmdevd-1e0fbba7c270701b4f27f808be988b63118d9533.tar.gz
mdevd-1e0fbba7c270701b4f27f808be988b63118d9533.tar.xz
mdevd-1e0fbba7c270701b4f27f808be988b63118d9533.zip
version: 0.1.4.0 v0.1.4.0
-rw-r--r--doc/index.html7
1 files changed, 4 insertions, 3 deletions
diff --git a/doc/index.html b/doc/index.html
index 1af280c..be7c5df 100644
--- a/doc/index.html
+++ b/doc/index.html
@@ -63,9 +63,10 @@ by a supervision suite. </li>
 and <a href="https://pubs.opengroup.org/onlinepubs/9699919799/functions/unsetenv.html">unsetenv()</a>)
 to store uevent data for each event. This implies repeated allocations of
 heap memory. By contrast, mdevd does not use its own environment - it
-actually does not use heap memory at all. All the memory it uses is
-committed (in the stack) at start time, and it will never grow during
-its lifetime. </li>
+only uses heap memory to compile its regular expressions, which only happens
+at start and when you reload its configuration file. All the rest of the
+memory it uses is committed in the stack, and it will never require more.
+mdevd cannot fail due to lack of memory while it is processing events. </li>
  <li> Better speed: <tt>mdev -d</tt> parses its config file for every
 event it receives, and has to perform expensive operations such as
 <a href="https://pubs.opengroup.org/onlinepubs/9699919799/functions/getpwnam.html">getpwnam()</a>