It’s a little more complex than that….
Yes, the Kernel is a compiled program – but it runs in a privileged mode that is not available to user-space (normal) stuff. It acts as the interface between the low-level hardware and applications running in user-space.

The kernel then exposes the hardware to applications through the device drivers. When you call `open()`, `close()`, `read()` and `write()` on that device driver, they get mapped through to the device driver in kernel space which fulfils that request. The user-space application uses the `libc` as the interface between user-space and kernel-sapce

Very simplistically:

+---------------+
| Application   |
|  open()       |       
+---------------+
  |        ^        
  V        |
 libc     libc 
  |        |
  V        |
+---------------+
|   Kernel      |
|   |       ^   |  
|   V       |   |  
| Device Driver | 
+---------------+
  |        ^
  V        |
+---------------+
| Hardware      |  
+---------------+

but I want to know about more deeply like syscall table and more

That is getting into Linux kernel device drivers.
Have you looked at the Bootlin course material?
https://bootlin.com/doc/training/linux-kernel/

I haven’t yet.

😵

Let’s see where it goes

I can’t share my materials, as they are proprietary – but can answer any questions you have