From 5685448c0f43a282c53245a3c40ed2fc070e6907 Mon Sep 17 00:00:00 2001 From: Vladislav Bolkhovitin Date: Fri, 7 Oct 2016 23:34:34 +0000 Subject: [PATCH] SCST README: clarification git-svn-id: http://svn.code.sf.net/p/scst/svn/trunk@6997 d57e44dd-8a1f-0410-8b47-8ef2f437770f --- scst/README | 20 +++++++++++++------- 1 file changed, 13 insertions(+), 7 deletions(-) diff --git a/scst/README b/scst/README index 4b380b61a..6355425c9 100644 --- a/scst/README +++ b/scst/README @@ -2264,14 +2264,20 @@ help in many troubleshooting cases. So, if you may consider to keep CONFIG_SCST_TRACING, its performance impact is very limited. IMPORTANT: The development version of SCST in the SVN is optimized for -========= development and bug hunting, not for performance. To reconfigure - - it for performance you should run "make 2perf" or "make - 2release" (to keep CONFIG_SCST_TRACING) in the root of your - source code (e.g. trunk/). It will set the above options as - needed. The only option it doesn't set is +========= development and bug hunting, not for performance. This means + it is MUCH slower (multiple times). To reconfigure SCST for + release you should run "make 2release" command in the root of + your source code (e.g. trunk/). It will set the above options + as needed. The only option it doesn't set is CONFIG_SCST_TEST_IO_IN_SIRQ, so, if needed, you should change - it manually. + it manually. There is also so called "performance" build + mode, which you can activate by "make 2perf" command. The + only difference it has comparing to release build mode is + disabled CONFIG_SCST_TRACING option. Because of that, you + won't be able to see many important SCST run time logging + messages. This mode is intended to evaluate impact of + CONFIG_SCST_TRACING on performance and not recommended for + production. IMPORTANT: You can't use debug SCST drivers with non-debug SCST core. ========= So, after disabling both CONFIG_SCST_TRACING and CONFIG_SCST_DEBUG