Skip to content

Commit 20e2ca8

Browse files
committed
fix(doc): do not claim guest memory is always fd based
At the time of writing the docs, that was temporarily the case in v1.6.0, but was reverted in scenarios where no vhost-user devices are attached due to performance regressions. Signed-off-by: Patrick Roy <roypat@amazon.co.uk>
1 parent 66cf8cb commit 20e2ca8

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

docs/hugepages.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -49,8 +49,8 @@ tracking is enabled, even if the host users huge mappings.
4949

5050
### Why does Firecracker not offer a transparent huge pages (THP) setting?
5151

52-
Firecracker's guest memory is memfd based. Linux (as of 6.1) does not offer a
53-
way to dynamically enable THP for such memory regions. Additionally, UFFD does
52+
Firecracker's guest memory can be memfd based. Linux (as of 6.1) does not offer
53+
a way to dynamically enable THP for such memory regions. Additionally, UFFD does
5454
not integrate with THP (no transparent huge pages will be allocated during
5555
userfaulting). Please refer to the [Linux Documentation][thp_docs] for more
5656
information.

0 commit comments

Comments
 (0)