Also clock_gettime is not even doing any syscalls. Im curious how it works, but it works great.

@@rogo7330 “While it may seem like it would require a system call to access the system clock, on some systems, including Linux, it is implemented using a virtual dynamic shared object (VDSO) mechanism. The VDSO is a kernel-provided shared library that allows user-space programs to access certain kernel-level functionalities without the need for a system call. One of the functionalities that can be accessed through the VDSO is the system clock. When a program calls clock_gettime(), the C library first checks if the VDSO is available and can be used to retrieve the clock time. If the VDSO is present, clock_gettime() accesses it through a function pointer and retrieves the time directly from the VDSO, without making a system call. This mechanism is more efficient than using a system call, as it avoids the overhead of switching between user space and kernel space. However, if the VDSO is not available or cannot be used, the C library will fallback to using a system call to retrieve the clock time. This ensures that clock_gettime() will always work correctly, regardless of whether the VDSO is available or not.”

@@addisonmigash8227 basically there is a function that can be directly executed by userspace program, but this function is doing something that requires kernel priveleges. Thats how I understand it from this description.

That's exactly what I'm doing in my C program, but my cursor still jumps around. I print it using printf. I guess it could be due to the fact that my computer screen refreshes when its in the middle of printing I guess. But I am not sure yet

Good. I'm never fixing that then.

You just had to be annoyed, 😂