Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

gsoc-2024: Fix typos #22

Open
wants to merge 1 commit into
base: staging
Choose a base branch
from
Open

gsoc-2024: Fix typos #22

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions ...-in-Internal-Libraries/Yang-Hu-Synchronization-Support-in-Internal-Libraries.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,8 +5,8 @@
## Summary

Memory allocators have a significant impact on application performance.
There have been serveral [research papers](https://dl.acm.org/doi/10.1145/378795.378821) which compared different memory allocators.
According to their work, switching to the appropiate memory allocator may improve the application performance by 60%.
There have been several [research papers](https://dl.acm.org/doi/10.1145/378795.378821) which compared different memory allocators.
According to their work, switching to the appropriate memory allocator may improve the application performance by 60%.
Unikraft currently supports only one non-synchronized memory allocator, the [*binary buddy* allocator](https://github.com/unikraft/unikraft/tree/staging/lib/ukallocbbuddy).
Therefore, this project aims to enhance synchronization support in Unikraft's internal libraries and port [*mimalloc*](https://github.com/microsoft/mimalloc) (pronounced "me-malloc"), a high-performance general-purpose memory allocator developed by Microsoft, to it.

Expand Down