From 6dffd85cd6157c9e6dc0089ab0a9a5adcebf6977 Mon Sep 17 00:00:00 2001 From: Yang Hu Date: Fri, 9 Aug 2024 10:35:58 -0400 Subject: [PATCH] Update content/blog/2024-08-01-unikraft-gsoc-debugging-mimalloc.mdx Co-authored-by: Radu Nichita <45298861+RaduNichita@users.noreply.github.com> Signed-off-by: Yang Hu --- content/blog/2024-08-01-unikraft-gsoc-debugging-mimalloc.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/blog/2024-08-01-unikraft-gsoc-debugging-mimalloc.mdx b/content/blog/2024-08-01-unikraft-gsoc-debugging-mimalloc.mdx index 33e7d334..4d01a6e3 100644 --- a/content/blog/2024-08-01-unikraft-gsoc-debugging-mimalloc.mdx +++ b/content/blog/2024-08-01-unikraft-gsoc-debugging-mimalloc.mdx @@ -29,7 +29,7 @@ This is the first step in a series of efforts to provide Unikraft users with mor ### Objectives [Hugo Lefeuvre](https://github.com/hlef) made an initial work to port mimalloc to Unikraft back in 2020 (see [this repo](https://github.com/unikraft/lib-mimalloc)). -However, as Unikraft has evolved significantly over the years, more work is needed to adapt the `lib-mimalloc` port to the latest Unikraft core. +However, as Unikraft has evolved significantly over the years, more work has to be done in order to adapt the `lib-mimalloc` port to the latest Unikraft core. So far, I have successfully ported the mimalloc memory allocator to Unikraft, marked by a successful compilation of mimalloc `v1.6.3` against the latest Unikraft core (v0.17.0) with `lib-musl`. Now, I am focused on validating the port and testing its performace.