diff options
| author | gVisor bot <gvisor-bot@google.com> | 2020-10-06 13:01:23 -0700 |
|---|---|---|
| committer | gVisor bot <gvisor-bot@google.com> | 2020-10-06 13:01:23 -0700 |
| commit | 68e1dfa308a36530b6fd3d3d872290e900abbfaa (patch) | |
| tree | 8d8e38d849529687febb958b5de94153bf058c39 | |
| parent | a57dc67b6386c4c75ba6b9b4cee11277a8a98898 (diff) | |
| parent | c29f5cf193cb2082a0efe526a905a4211d75808c (diff) | |
Merge pull request #3150 from wietsevenema:patch-2
PiperOrigin-RevId: 335702168
| -rw-r--r-- | g3doc/user_guide/networking.md | 7 |
1 files changed, 3 insertions, 4 deletions
diff --git a/g3doc/user_guide/networking.md b/g3doc/user_guide/networking.md index 4aa394c91..95f675633 100644 --- a/g3doc/user_guide/networking.md +++ b/g3doc/user_guide/networking.md @@ -2,9 +2,9 @@ [TOC] -gVisor implements its own network stack called [netstack][netstack]. All aspects -of the network stack are handled inside the Sentry — including TCP connection -state, control messages, and packet assembly — keeping it isolated from the host +gVisor implements its own network stack called netstack. All aspects of the +network stack are handled inside the Sentry — including TCP connection state, +control messages, and packet assembly — keeping it isolated from the host network stack. Data link layer packets are written directly to the virtual device inside the network namespace setup by Docker or Kubernetes. @@ -82,4 +82,3 @@ Offload (GSO) to run with a kernel that is newer than 3.17. Add the } ``` -[netstack]: https://github.com/google/netstack |