Add some parameters for the NVIDIA driver module

[ventureoo]

Adding a some of important parameters for driver modules.

I'll make a few remarks:

NVreg_UsePageAttributeTable=1 (Default 0) - Improves CPU performance on laptops (See https://bbs.archlinux.org/viewtopic.php?id=242007). NVreg_EnablePCIeGen3=1 (Default 0) - Enables full PCIe 3.0 support for graphics cards. The following is written in nv-reg.h about this parameter:

Due to interoperability problems seen with Kepler PCIe Gen3 capable GPUs when configured on SandyBridge E desktop platforms, NVIDIA feels that delivering a reliable, high-quality experience is not currently possible in PCIe Gen3 mode on all PCIe Gen3 platforms. Therefore, Quadro, Tesla and NVS Kepler products operate in PCIe Gen2 mode by default. You may use this option to enable PCIe Gen3 support.

However, in home configurations for which CachyOS is intended, most people probably do not use either Tesla or Quadro. Support for Kepler, which as indicated had problems with PCIe 3.0, is also discontinued with the 510 driver version.

NVreg_InitializeSystemMemoryAllocations=0 (Default 1) - Disables clearing system memory allocation before using it for the GPU. Has potential security risks, but it also potentially increases performance.

A full description can be found in my nvidia-tweaks package: https://aur.archlinux.org/cgit/aur.git/tree/nvidia.conf?h=nvidia-tweaks

Also my deprecated patch: https://aur.archlinux.org/cgit/aur.git/tree/0004-NVreg-Improvements.patch?h=nvidia-dkms-performance

As I said these changes may partly break some things (although I personally have not had any problems with these parameters on my 1050 Ti), but I suggest at least adding NVreg_UsePageAttributeTable=1 by default and other parameters at your discretion.

@ptr1337

[ptr1337]

Hey!

Yeah, we already talked together about this. I would also add maybe some other tweaks regarding modprobed, the question is how much it affects other devices without a nvidia card?

If you want you can extend this and then i will merge it!

[ventureoo]

@ptr1337 Hi.

Yeah, we already talked together about this. I would also add maybe some other tweaks regarding modprobed, the question is how much it affects other devices without a nvidia card?

No, I don't think it should have any effect on hardware configurations without NVIDIA. modprobe only applies these parameters at module load time:

   options modulename option...
       This command allows you to add options to the module modulename (which might be an alias) every time it is inserted into the kernel: whether directly (using
       modprobe modulename) or because the module being inserted depends on this module.

(From the modprobe.d man page)

But just to be sure, I also tested these parameters on my laptop with Intel graphics. No problems were found and the system did not give any warnings about it.

If you want you can extend this and then i will merge it!

Yeah, I guess I should probably add RTD3 Power Management on. Apparently, the NVreg_DynamicPowerManagement=0x02 parameter has no effect on configurations that don't support it, so perhaps we could add it. For configurations that support this technology this will be a performance benefit, for those who don't have it, there will be no effect.

Some Fedora repositories already have this option enabled by default, so I think it's really safe. https://github.com/negativo17/nvidia-kmod-common/blob/master/nvidia.conf#L16

[ventureoo]

I understand the subject a bit more, so I think we also need some udev rules to make NVreg_DynamicPowerManagement=0x02 work correctly, like here: https://github.com/negativo17/nvidia-kmod-common/blob/master/60-nvidia.rules