Very often, the majority of GPU IO traffic is textures. No form of text file is the most effective representation for them.
However, in my comment I didn’t meant text files. I meant that in *nix, a GPU itself is a single file, /dev/dri/cardN. All that GPU’s complexity is squeezed into a single ioctl system call for that special file. The approach is IMO one of the reason why Linux still doesn’t have reliable 3D acceleration support.
Here’s a long article why Linux ain’t ready for desktops, note the author listed 3D acceleration on the top:
However, in my comment I didn’t meant text files. I meant that in *nix, a GPU itself is a single file, /dev/dri/cardN. All that GPU’s complexity is squeezed into a single ioctl system call for that special file. The approach is IMO one of the reason why Linux still doesn’t have reliable 3D acceleration support.
Here’s a long article why Linux ain’t ready for desktops, note the author listed 3D acceleration on the top:
https://itvision.altervista.org/why.linux.is.not.ready.for.t...