no "nvidia" available for opengl and opencl

[mrl5]

I dont see nvidia in eselect opengl list and eselect opencl list

# eselect opengl list
Available OpenGL implementations:
  [1]   xorg-x11 *
# eselect opencl list
Available OpenCL implementations:
  [1]   ocl-icd *

# epro show

=== Enabled Profiles: ===

        arch: x86-64bit
       build: current
     subarch: core2_64
      flavor: desktop
     mix-ins: lxde
     mix-ins: gfxcard-nvidia

(...)

# emerge -pv nvidia-kernel-modules nvidia-drivers

These are the packages that would be merged, in order:

Calculating dependencies... done!
[ebuild   R    ] x11-drivers/nvidia-drivers-430.26-r2:0/430::core-gl-kit  USE="X compat32 cuda egl encodeapi glvnd gpgpu nvcuvid nvfbc nvifr nvml nvpd opencl opengl opticalflow optix raytracing static-libs tools uvm vdpau wayland xdriver xutils -abi_riscv_lp64 -abi_riscv_lp64d -acpi -driver" 0 KiB
[ebuild   R    ] x11-drivers/nvidia-kernel-modules-430.26:0/430::core-gl-kit  USE="kms uvm -abi_riscv_lp64 -abi_riscv_lp64d" 0 KiB

Total: 2 packages (2 reinstalls), Size of downloads: 0 KiB

# lsmod | grep nvidia
nvidia_drm             45056  2
nvidia_modeset       1081344  3 nvidia_drm
nvidia              18395136  83 nvidia_modeset
drm_kms_helper        204800  1 nvidia_drm
drm                   491520  5 drm_kms_helper,nvidia_drm
ipmi_msghandler        65536  2 ipmi_devintf,nvidia

But looking at the performance when I watch 1080p movie or glxgears I think that nvidia is used - but I'm not 100% sure:

# glxgears 
Running synchronized to the vertical refresh.  The framerate should be
approximately the same as the monitor refresh rate.
302 frames in 5.0 seconds = 60.241 FPS
300 frames in 5.0 seconds = 59.883 FPS
300 frames in 5.0 seconds = 59.883 FPS

 

[mrl5]

hm.. looks like it's described here: https://www.funtoo.org/Package:NVIDIA_Linux_Display_Drivers

Quote

Once the new drivers are installed, you will notice that eselect opengl will display xorg-x11. This is OK! With the new drivers, the libglvnd package now provides libGL and brokers the GL calls to the appropriate underlying hardware-specific library, making eselect opengl redundant. We may fix this is the production release so that eselect opengl shows glvnd instead, to avoid confusion.

@temptorsent could you pls comment is it still expected behavior?