Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
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
2 changes: 1 addition & 1 deletion g3doc/user_guide/filesystem.md
Original file line number Diff line number Diff line change
Expand Up @@ -113,4 +113,4 @@ Docker configuration (`/etc/docker/daemon.json`) and restart the Docker daemon:
}
```

[Production guide]: ../production/
[Production guide]: production.md
11 changes: 7 additions & 4 deletions g3doc/user_guide/production.md
Original file line number Diff line number Diff line change
Expand Up @@ -115,7 +115,9 @@ If you absolutely must run gVisor in a virtual machine, we recommend using the
`systrap` platform. This platform has the most flexibility, but its performance
will lag behind that of KVM.

<a class="button" href="/docs/user_guide/platforms/">Configure Platform
<!-- disableFinding(LINK_RELATIVE_G3DOC) -->

<a class="button">[Configure Platform](../architecture_guide/platforms.md)
&raquo;</a>

### Optimizing I/O performance {#configure-io}
Expand All @@ -126,8 +128,7 @@ default configuration must support all possible I/O interaction patterns.
However, you can configure gVisor to use more aggressive caching policies where
it makes sense.

<a class="button" href="/docs/user_guide/filesystem/">Configure Filesystem
&raquo;</a>
<a class="button">[Configure Filesystem](filesystem.md) &raquo;</a>

### Optimizing network performance {#configure-network}

Expand All @@ -137,7 +138,9 @@ is optimized for security over performance. If your application is semi-trusted
and network performance is paramount, you can optionally enable Network
Passthrough to use the host's (Linux's) network stack, rather than gVisor's own.

<a class="button" href="/docs/user_guide/networking/">Configure Networking
<!-- disableFinding(LINK_RELATIVE_G3DOC) -->

<a class="button">[Configure Networking](../architecture_guide/networking.md)
&raquo;</a>

### Optimizing MM performance {#configure-mm}
Expand Down
Loading