Update docs for guides and concepts #400
Conversation
| compatibility but they result in a monolithic kernel. | ||
|
|
||
| Existing monolithic OSs do have APIs for each component but these APIs have | ||
| become quite rich as they have evolved organically. These OSs often blur |
There was a problem hiding this comment.
Does this sentence have any value?
"Existing monolithic OSs do have APIs for each component but these APIs have
become quite rich as they have evolved organically."
Sounds very vague to me.
| all kernels), functions provided by the host (scheduling, memory allocation, | ||
| etc.), and independently executable "factions" (e.g., network or filesystem | ||
| support). rumpkernel goes some way towards achieving our goals. Still, many | ||
| dependencies remain that require the kernel to have the base and hypercall |
There was a problem hiding this comment.
"Still, many
dependencies remain that require the kernel to have the base and hypercall
layers. In the context of a VM, which is our deployment target, this limits the
extent of modularity that we can achieve."
Please check if this still carries the meaning the author initially intended.
|
@UtkarshVerma , thanks, we will take a look. Please solve the conflict. |
|
@razvand I have fixed the merge conflicts. |
|
@UtkarshVerma , there are some new merge conflicts. Could you please fix them again? |
As someone new to the Unikraft project, I was reading the docs to understand more about the ecosystem. In the process, I noticed a few articles where I thought having a bit more detail would help.
Please have a look and let me know if any changes are required.