Comment change only: remove discussion of --client-perms flag and clarify

performance consequences of client requests.

MERGE TO STABLE

git-svn-id: svn://svn.valgrind.org/valgrind/trunk@1460

diff --git a/include/valgrind.h b/include/valgrind.h
index c5cf5ab329b512fc94448fd8981317ac96780177..b81961b864addef1d344460ae46be12aec7530c4 100644 (file)
--- a/include/valgrind.h
+++ b/include/valgrind.h
@@ -78,12 +78,12 @@
 
    The resulting executables will still run without Valgrind, just a
    little bit more slowly than they otherwise would, but otherwise
-   unchanged.  
-
-   When run on Valgrind with --client-perms=yes, Valgrind observes
-   these macro calls and takes appropriate action.  When run on
-   Valgrind with --client-perms=no (the default), Valgrind observes
-   these macro calls but does not take any action as a result.  */
+   unchanged.  When not running on valgrind, each client request
+   consumes about 9 x86 instructions, so the resulting performance
+   loss is negligible unless you plan to execute client requests
+   millions of times per second.  Nevertheless, if that is still a
+   problem, you can compile with the NVALGRIND symbol defined (gcc
+   -DNVALGRIND) so that client requests are not even compiled in.  */