JavaScript isn't enabled in your browser, so this file can't be opened. Enable and reload.
Session 09: Advanced App Porting
Sign in to Google
to save your progress.
Learn more
* Indicates required question
Why does using the Unikraft API directly provides better performance than using the POSIX API exposed by the standard C library?
*
The standard C library is not optimized
Less indirections
The Unikraft API is better optimized
Required
What is the role of the VFS core?
*
Reads/writes from actual files stored either on disk or memory
Is used by the standard C library to interact with files
Provide an abstraction layer over the file systems
Required
What does every Unikraft ported library have?
*
Makefile.uk
Makefile.rules
Config.uk
main.c
Required
Which of the following functionalities make use of the ELF sections?
*
Unikraft testing library (
https://github.com/unikraft/unikraft/tree/staging/lib/uktest
)
Internal RAMFS library (
https://github.com/unikraft/unikraft/tree/staging/lib/ramfs
)
Networking device (
https://github.com/unikraft/unikraft/tree/staging/lib/uknetdev
)
Unikraft constructors (
https://github.com/unikraft/unikraft/blob/staging/include/uk/ctors.h
)
Required
Submit
Clear form
This content is neither created nor endorsed by Google.
Report Abuse
-
Terms of Service
-
Privacy Policy
Forms
