separate namespaces for kernel internals versus user-space interface versus user-space proxies+runtime #205
Comments
|
depending on the api definitions is fine. it is used to expose relevant kernel internals. a dedicated namespace |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The subfolder
kernel/mythoscontains shared definitions that are used by the kernel and the user space. Within the kernel implementation it is not always clear which definitions are internal or belong to the public api. And sometimes the dependency is in a weird directions. Core kernel concepts should not directly depend on the API's definitions in the code.One example is the KEvent data structure. In the API it is used to return a 64bit result value together with a user-configured 64bit context value to the user-space. Having two identical definitions in the kernel's core and the api sounds weird but would have the advantage that it is much more clearer, where the transition from kernel internals to the public interface happens. The kernel internal KEvent might have to transmit additional kernel-internal data.
The text was updated successfully, but these errors were encountered: