Does modprobe.d/nvidia.conf NVreg_EnableStreamMemOPs need to be set for GPUDirect to work?

In a “GPUDirect async” note, reference “libgdsync/README.md at master · gpudirect/libgdsync · GitHub”, it says that “NVreg_EnableStreamMemOPs” needs to be set.
Is that still the case?

“If the display driver is r387 or newer, the CUDA Memory Operations API must be explicitly enabled by means of NVreg_EnableStreamMemOPs=1;”

Somehow I had an nvidia.conf file created with those options.
Something along the way must have created it for me, but it prevents loading the nvidia driver on my system.
Can those parms not be set and still have gpudirect function?
Can I just do away with that nvidia.conf file? (Those are the only entries)

[url]CUDA Driver API :: CUDA Toolkit Documentation

Thanks much.

It helps if one gets the case correct on “Enable”… The nvidia.conf file also had two lines, one for:
options nvidia NVreg_EnableStreamMemOPs=1 NVreg_RegistryDwords=“PeerMappingOverride=1;”
and another for:
options nvidia NVreg_RegistryDwords=“PeerMappingOverride=1;”
Only one of the two was needed (used the first due to my driver version).

Got it working again and using the function cuDeviceGetAttribute with CU_DEVICE_ATTRIBUTE_CAN_USE_STREAM_MEM_OPS makes a nice sanity check too.