Skip to content

Commit 89064c1

Browse files
xmarcalxdianpopa
authored andcommitted
doc: provide better clarity of supported features
Signed-off-by: Marco Cali <xmarcalx@amazon.co.uk>
1 parent b71407a commit 89064c1

File tree

2 files changed

+7
-7
lines changed

2 files changed

+7
-7
lines changed

docs/design.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -18,8 +18,8 @@ Firecracker virtual machine manager (VMM).
1818

1919
1. Firecracker can safely run workloads from different customers on the same
2020
machine.
21-
1. Customers can create microVMs with any combination of vCPU and memory to
22-
match their application requirements.
21+
1. Customers can create microVMs with any combination of vCPU (up to 32)
22+
and memory to match their application requirements.
2323
1. Firecracker microVMs can oversubscribe host CPU and memory. The degree of
2424
oversubscription is controlled by customers, who may factor in workload
2525
correlation and load in order to ensure smooth host system operation.

docs/prod-host-setup.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -82,10 +82,10 @@ for Firecracker processes that are unresponsive, and kills them, by SIGKILL.
8282

8383
## Jailer Configuration
8484

85-
For assuring secure isolation in production deployments, Firecracker should
86-
must be started using the `jailer` binary that's part of each Firecracker
87-
release, or executed under process constraints equal or more restrictive than
88-
those in the jailer. For more about Firecracker sandboxing please see
85+
For assuring secure isolation in production deployments, Firecracker should be
86+
started using the `jailer` binary that's part of each Firecracker release, or
87+
executed under process constraints equal or more restrictive than those in the jailer.
88+
For more about Firecracker sandboxing please see
8989
[Firecracker design](design.md)
9090

9191
The Jailer process applies
@@ -127,7 +127,7 @@ Here are some recommendations on how to limit the process's resources:
127127

128128
- Jailer's `resource-limit` provides control on the disk usage through:
129129
- `fsize` - limits the size in bytes for files created by the process
130-
- `no-file` - specifies a value one greater than the maximum file
130+
- `no-file` - specifies a value greater than the maximum file
131131
descriptor number that can be opened by the process. If not specified,
132132
it defaults to 4096.
133133

0 commit comments

Comments
 (0)