diff options
Diffstat (limited to 'g3doc/roadmap.md')
| -rw-r--r-- | g3doc/roadmap.md | 43 |
1 files changed, 22 insertions, 21 deletions
diff --git a/g3doc/roadmap.md b/g3doc/roadmap.md index 86bb11c3b..06ea25a8b 100644 --- a/g3doc/roadmap.md +++ b/g3doc/roadmap.md @@ -10,27 +10,28 @@ feature work. Most gVisor work is focused on four areas. -* [Performance][performance]: overall sandbox performance, including platform - performance, is a critical area for investment. This includes: network - performance (throughput and latency), file system performance (metadata and - data I/O), application switch and fault costs, etc. The goal of gVisor is to - provide sandboxing without a material performance or efficiency impact on all - but the most performance-sensitive applications. - -* [Compatibility][compatibility]: supporting a wide range of applications - requires supporting a large system API, including special system files (e.g. - proc, sys, dev, etc.). The goal of gVisor is to support the broad set of - applications that depend on a generic Linux API, rather than a specific kernel - version. - -* [Infrastructure & tooling][infrastructure]: the above goals require aggressive - testing and coverage, and well-established processes. This includes adding - appropriate system call coverage, end-to-end suites and runtime tests. - -* [Integration][integration]: Container infrastructure is evolving rapidly and - becoming more complex, and gVisor must continuously implement relevant and - popular features to ensure that integration points remain robust and - feature-complete while preserving security guarantees. +* [Performance][performance]: overall sandbox performance, including platform + performance, is a critical area for investment. This includes: network + performance (throughput and latency), file system performance (metadata and + data I/O), application switch and fault costs, etc. The goal of gVisor is to + provide sandboxing without a material performance or efficiency impact on + all but the most performance-sensitive applications. + +* [Compatibility][compatibility]: supporting a wide range of applications + requires supporting a large system API, including special system files (e.g. + proc, sys, dev, etc.). The goal of gVisor is to support the broad set of + applications that depend on a generic Linux API, rather than a specific + kernel version. + +* [Infrastructure & tooling][infrastructure]: the above goals require + aggressive testing and coverage, and well-established processes. This + includes adding appropriate system call coverage, end-to-end suites and + runtime tests. + +* [Integration][integration]: Container infrastructure is evolving rapidly and + becoming more complex, and gVisor must continuously implement relevant and + popular features to ensure that integration points remain robust and + feature-complete while preserving security guarantees. ## Releases |