From: Eric Blake Date: Wed, 30 Oct 2019 16:17:55 +0000 (+0100) Subject: 8400: Replace
 graph with .
X-Git-Url: http://git.annexia.org/?a=commitdiff_plain;h=56e3f6075fb0c4bc9ce19abfe9e4b16c6ab64535;p=libguestfs-talks.git

8400: Replace 
 graph with 
. --- diff --git a/2019-kvm-forum/8400-tradeoff-complexity-issues.html b/2019-kvm-forum/8400-tradeoff-complexity-issues.html index 8208350..f3c0ba3 100644 --- a/2019-kvm-forum/8400-tradeoff-complexity-issues.html +++ b/2019-kvm-forum/8400-tradeoff-complexity-issues.html @@ -5,26 +5,47 @@

Tradeoff: how much complexity

- Filler - summarize various options. Maybe a 2-d graph with: - -

-    c |
-    l |
- ^  i |
-    e |
- i  n |
- n  t |  multiple knobs,
- c    |  requires multiple
- r  c |  fallbacks, but a
- e  o |  non-SR solution works
- a  m |
- s  p |
- i  l |
- n  e |
- g  x |                           require more uniformity,
-    i |                           interop testing is easier,
-    t |                           but writing correct server
-    y |                           requires more effort
-      +------------------------------------------------------
-         > increasing server complexity
+  Tradeoffs in implementation complexity
+  
+ + + + + + + + + + + + + + + +
Lots of knobs in the NBD specMandate all-or-none server implementation
Pro +
    +
  • Implement as much or as little as convenient for the + server +
  • Matches reality that no one resize solution fits all +
+
+
    +
  • Easier interoperability testing +
  • Client can rely on all servers giving same response +
+
Con +
    +
  • More combinations requires more testing +
  • Odd or untested combinations could produce weird + behaviors or even CVEs +
  • Clients must be prepared for more fallbacks +
  • NBD protocol tries to be as simple as possible +
+
+
    +
  • Not all tradeoffs map easily to existing implementation +
  • Open-ended structured replies requires more efforts for + writing a compliant server +
+