To test some config I created such app_config.xml file on SETI beta:

<app_config>
   <app>
      <name>astropulse_v7</name>
      <max_concurrent>10</max_concurrent>
      <gpu_versions>
          <gpu_usage>0.5</gpu_usage>
	<cpu_usage>0.01</cpu_usage>
      </gpu_versions>
    </app>
  <app_version>
 	  <app_name>astropulse_v7</app_name>
 	<plan_class>opencl_ati_100</plan_class>
	<cmdline>-cpu_lock</cmdline>
   </app_version>
</app_config>

Now 2 GPU instances running as desired, but app seems doesn't get param passed via <smdline> tag. Before using app's own abilities to pass params I would like to know what is wrong in this case.

---

To test some config I created such app_config.xml file on SETI beta:

<app_config>
   <app>
      <name>astropulse_v7</name>
      <max_concurrent>10</max_concurrent>
      <gpu_versions>
          <gpu_usage>0.5</gpu_usage>
	<cpu_usage>0.01</cpu_usage>
      </gpu_versions>
    </app>
  <app_version>
 	  <app_name>astropulse_v7</app_name>
 	<plan_class>opencl_ati_100</plan_class>
	[color=red]<cmdline>-cpu_lock</cmdline>[/color]
   </app_version>
</app_config>

Now 2 GPU instances running as desired, but app seems doesn't get param passed via <smdline> tag. Before using app's own abilities to pass params I would like to know what is wrong in this case.

I thought the <cmdline> tag required double hyphens, i.e.
<cmdline>--cpu_lock</cmdline>

I thought the <cmdline> tag required double hyphens, i.e.
<cmdline>--cpu_lock</cmdline>

How this could be infered from app_config documentation? -cpu_lock is app-specific option, I could make it let say @cpu_lock or #cpu_lock in app code.
Should one list it -@cpu_lock or -#cpu_lock then ?

---

I thought the <cmdline> tag required double hyphens, i.e.
<cmdline>--cpu_lock</cmdline>

How this could be infered from app_config documentation? -cpu_lock is app-specific option, I could make it let say @cpu_lock or #cpu_lock in app code.
Should one list it -@cpu_lock or -#cpu_lock then ?

I put it into my app_config.xml for Seti Beta, seems to work O.K (althrough I took it out, did a read, and restarted Boinc, and it's still enabled):

Running on device number: 0
Priority of worker thread raised successfully
Priority of process adjusted successfully, below normal priority class used
OpenCL platform detected: Intel(R) Corporation
OpenCL platform detected: NVIDIA Corporation
BOINC assigns device 0
Info: BOINC provided OpenCL device ID used
Used GPU device parameters are:
Number of compute units: 2
Single buffer allocation size: 256MB
Total device global memory: 2048MB
max WG size: 1024
local mem type: Real
FERMI path used: yes
-unroll default value used: 2
-ffa_block default value used: 512
-ffa_block_fetch default value used: 256

Build features: Non-graphics BLANKIT OpenCL USE_OPENCL_NV TWIN_FFA OCL_ZERO_COPY COMBINED_DECHIRP_KERNEL FFTW USE_INCREASED_PRECISION USE_SSE2 x86
CPUID: Intel(R) Core(TM) i5-3210M CPU @ 2.50GHz

Cache: L1=64K L2=256K

CPU features: FPU TSC PAE CMPXCHG8B APIC SYSENTER MTRR CMOV/CCMP MMX FXSAVE/FXRSTOR SSE SSE2 HT SSE3 SSSE3 SSE4.1 SSE4.2 AVX
AstroPulse v7 Windows x86 rev 2690, V7 match, by Raistmer with support of Lunatics.kwsn.net team. SSE2

OpenCL version by Raistmer

ffa threshold mods by Joe Segur
SSE3 dechirping by JDWhale
Combined dechirp kernel by Frizz
Number of OpenCL platforms: 2


OpenCL Platform Name: Intel(R) OpenCL
Number of devices: 1
Max compute units: 16
Max work group size: 512
Max clock frequency: 1100Mhz
Max memory allocation: 340158054
Cache type: Read/Write
Cache line size: 64
Cache size: 2097152
Global memory size: 1360632218
Constant buffer size: 65536
Max number of constant args: 8
Local memory type: Scratchpad
Local memory size: 65536
Queue properties:
Out-of-Order: No
Name: Intel(R) HD Graphics 4000
Vendor: Intel(R) Corporation
Driver version: 10.18.10.3621
Version: OpenCL 1.2
Extensions: cl_intel_d3d11_nv12_media_sharing cl_intel_dx9_media_sharing cl_khr_3d_image_writes cl_khr_byte_addressable_store cl_khr_d3d10_sharing cl_khr_d3d11_sharing cl_khr_depth_images cl_khr_dx9_media_sharing cl_khr_gl_depth_images cl_khr_gl_event cl_khr_gl_msaa_sharing cl_khr_gl_sharing cl_khr_global_int32_base_atomics cl_khr_global_int32_extended_atomics cl_khr_icd cl_khr_image2d_from_buffer cl_khr_local_int32_base_atomics cl_khr_local_int32_extended_atomics cl_intel_accelerator cl_intel_motion_estimation


OpenCL Platform Name: NVIDIA CUDA
Number of devices: 1
Max compute units: 2
Max work group size: 1024
Max clock frequency: 950Mhz
Max memory allocation: 536870912
Cache type: Read/Write
Cache line size: 128
Cache size: 32768
Global memory size: 2147483648
Constant buffer size: 65536
Max number of constant args: 9
Local memory type: Scratchpad
Local memory size: 49151
Queue properties:
Out-of-Order: Yes
Name: GeForce GT 650M
Vendor: NVIDIA Corporation
Driver version: 340.43
Version: OpenCL 1.1 CUDA
Extensions: cl_khr_byte_addressable_store cl_khr_icd cl_khr_gl_sharing cl_nv_d3d9_sharing cl_nv_d3d10_sharing cl_khr_d3d10_sharing cl_nv_d3d11_sharing cl_nv_compiler_options cl_nv_device_attribute_query cl_nv_pragma_unroll cl_khr_global_int32_base_atomics cl_khr_global_int32_extended_atomics cl_khr_local_int32_base_atomics cl_khr_local_int32_extended_atomics cl_khr_fp64


state.fold_buf_size_short=65536; state.fold_buf_size_long=262144
INFO: can't open binary kernel file: C:\ProgramData\BOINC/projects/setiweb.ssl.berkeley.edu_beta\AstroPulse_Kernels_r2690.cl_GeForceGT650M.bin_V7_TWIN_FFA_34043, continue with recompile...
INFO: binary kernel file created
WARNING: can't open binary kernel file for oclFFT plan: C:\ProgramData\BOINC/projects/setiweb.ssl.berkeley.edu_beta\AP_clFFTplan_GeForceGT650M_32768_gr64_lr8_wg256_tw0_r2690.bin_34043, continue with recompile...
GPU device sync requested... ...GPU device synched
Termination request detected or computations are finished. GPU device synched, exiting...
Running on device number: 0
Priority of worker thread raised successfully
Priority of process adjusted successfully, below normal priority class used
OpenCL platform detected: Intel(R) Corporation
OpenCL platform detected: NVIDIA Corporation
BOINC assigns device 0
Info: BOINC provided OpenCL device ID used
Used GPU device parameters are:
Number of compute units: 2
Single buffer allocation size: 256MB
Total device global memory: 2048MB
max WG size: 1024
local mem type: Real
FERMI path used: yes
-unroll default value used: 2
-ffa_block default value used: 512
-ffa_block_fetch default value used: 256

Build features: Non-graphics BLANKIT OpenCL USE_OPENCL_NV TWIN_FFA OCL_ZERO_COPY COMBINED_DECHIRP_KERNEL FFTW USE_INCREASED_PRECISION USE_SSE2 x86
CPUID: Intel(R) Core(TM) i5-3210M CPU @ 2.50GHz

Cache: L1=64K L2=256K

CPU features: FPU TSC PAE CMPXCHG8B APIC SYSENTER MTRR CMOV/CCMP MMX FXSAVE/FXRSTOR SSE SSE2 HT SSE3 SSSE3 SSE4.1 SSE4.2 AVX
### Restart at 39.64 percent.
state.fold_buf_size_short=65536; state.fold_buf_size_long=262144
GPU device sync requested... ...GPU device synched
Termination request detected or computations are finished. GPU device synched, exiting...
CPU affinity adjustment enabled
GPUlock enabled. Use -instances_per_device N switch to provide number of instances to run if BOINC is configured to launch few tasks per device.
Running on device number: 0
Priority of worker thread raised successfully
Priority of process adjusted successfully, below normal priority class used
OpenCL platform detected: Intel(R) Corporation
OpenCL platform detected: NVIDIA Corporation
BOINC assigns device 0, slots 0 to 0 (including) will be checked
Used slot is 0; Info: BOINC provided OpenCL device ID used
Info: CPU affinity mask used: 1
Used GPU device parameters are:
Number of compute units: 2
Single buffer allocation size: 256MB
Total device global memory: 2048MB
max WG size: 1024
local mem type: Real
FERMI path used: yes
-unroll default value used: 2
-ffa_block default value used: 512
-ffa_block_fetch default value used: 256

Build features: Non-graphics BLANKIT OpenCL USE_OPENCL_NV TWIN_FFA OCL_ZERO_COPY COMBINED_DECHIRP_KERNEL FFTW USE_INCREASED_PRECISION USE_SSE2 x86
CPUID: Intel(R) Core(TM) i5-3210M CPU @ 2.50GHz

Cache: L1=64K L2=256K

CPU features: FPU TSC PAE CMPXCHG8B APIC SYSENTER MTRR CMOV/CCMP MMX FXSAVE/FXRSTOR SSE SSE2 HT SSE3 SSSE3 SSE4.1 SSE4.2 AVX
### Restart at 54.05 percent.
state.fold_buf_size_short=65536; state.fold_buf_size_long=262144
GPU device sync requested... ...GPU device synched
Termination request detected or computations are finished. GPU device synched, exiting...
CPU affinity adjustment enabled
GPUlock enabled. Use -instances_per_device N switch to provide number of instances to run if BOINC is configured to launch few tasks per device.
Running on device number: 0
Priority of worker thread raised successfully
Priority of process adjusted successfully, below normal priority class used
OpenCL platform detected: Intel(R) Corporation
OpenCL platform detected: NVIDIA Corporation
BOINC assigns device 0, slots 0 to 0 (including) will be checked
Used slot is 0; Info: BOINC provided OpenCL device ID used
Info: CPU affinity mask used: 1
Used GPU device parameters are:
Number of compute units: 2
Single buffer allocation size: 256MB
Total device global memory: 2048MB
max WG size: 1024
local mem type: Real
FERMI path used: yes
-unroll default value used: 2
-ffa_block default value used: 512
-ffa_block_fetch default value used: 256

Build features: Non-graphics BLANKIT OpenCL USE_OPENCL_NV TWIN_FFA OCL_ZERO_COPY COMBINED_DECHIRP_KERNEL FFTW USE_INCREASED_PRECISION USE_SSE2 x86
CPUID: Intel(R) Core(TM) i5-3210M CPU @ 2.50GHz

Cache: L1=64K L2=256K

CPU features: FPU TSC PAE CMPXCHG8B APIC SYSENTER MTRR CMOV/CCMP MMX FXSAVE/FXRSTOR SSE SSE2 HT SSE3 SSSE3 SSE4.1 SSE4.2 AVX
### Restart at 55.86 percent.
state.fold_buf_size_short=65536; state.fold_buf_size_long=262144
GPU device sync requested... ...GPU device synched
Termination request detected or computations are finished. GPU device synched, exiting...
CPU affinity adjustment enabled
GPUlock enabled. Use -instances_per_device N switch to provide number of instances to run if BOINC is configured to launch few tasks per device.
Running on device number: 0
Priority of worker thread raised successfully
Priority of process adjusted successfully, below normal priority class used
OpenCL platform detected: Intel(R) Corporation
OpenCL platform detected: NVIDIA Corporation
BOINC assigns device 0, slots 0 to 0 (including) will be checked
Used slot is 0; Info: BOINC provided OpenCL device ID used
Info: CPU affinity mask used: 1
Used GPU device parameters are:
Number of compute units: 2
Single buffer allocation size: 256MB
Total device global memory: 2048MB
max WG size: 1024
local mem type: Real
FERMI path used: yes
-unroll default value used: 2
-ffa_block default value used: 512
-ffa_block_fetch default value used: 256

Build features: Non-graphics BLANKIT OpenCL USE_OPENCL_NV TWIN_FFA OCL_ZERO_COPY COMBINED_DECHIRP_KERNEL FFTW USE_INCREASED_PRECISION USE_SSE2 x86
CPUID: Intel(R) Core(TM) i5-3210M CPU @ 2.50GHz

Cache: L1=64K L2=256K

CPU features: FPU TSC PAE CMPXCHG8B APIC SYSENTER MTRR CMOV/CCMP MMX FXSAVE/FXRSTOR SSE SSE2 HT SSE3 SSSE3 SSE4.1 SSE4.2 AVX
### Restart at 58.56 percent.
state.fold_buf_size_short=65536; state.fold_buf_size_long=262144

Claggy

Now 2 GPU instances running as desired, but app seems doesn't get param passed via <smdline> tag. Before using app's own abilities to pass params I would like to know what is wrong in this case.

What Boinc version is this on? knowing you it's on an old Alpha/Beta version where the Bugs hadn't been eliminated yet, upgrade to Boinc 7.4.21 and try again.

and I only needed to use -cpu_lock

Claggy

Now 2 GPU instances running as desired, but app seems doesn't get param passed via <smdline> tag. Before using app's own abilities to pass params I would like to know what is wrong in this case.

What Boinc version is this on? knowing you it's on an old Alpha/Beta version where the Bugs hadn't been eliminated yet, upgrade to Boinc 7.4.21 and try again.

and I only needed to use -cpu_lock

Claggy

BOINC version 7.0.64
<core_client_version>7.0.64</core_client_version>

EDIT: from Wiki page:

cmdline
command-line parameters to pass to the program.

No mentions from what version it was introduced. So accordingly this doc 7.0.64 is fine.

---

EDIT: from Wiki page:

cmdline
command-line parameters to pass to the program.

No mentions from what version it was introduced. So accordingly this doc 7.0.64 is fine.

Cmdline is a sub-component of app_version. The app_version construct is labelled as 'new in 7.2.39'.