diff options
| author | Ben Pfaff <blp@nicira.com> | 2009-08-19 15:59:18 -0700 |
|---|---|---|
| committer | Ben Pfaff <blp@nicira.com> | 2009-08-19 15:59:18 -0700 |
| commit | 641a0a4ed0a79d53a52d4e78ce1d90140a768798 (patch) | |
| tree | b011ec3e120b0716d1bd0e7165d67fec1f13075f /xenserver/etc_sysconfig_vswitch.example | |
| parent | 612f6d49c5137ecaf407a5f8cc0a1e5ba4b4bca7 (diff) | |
xenserver: Renice netback process to priority 0 by default.
Under heavy VM network load, we have observed that ovs-vswitchd can be
starved for CPU time, which prevents flows from being set up. This can
in turn cause connections to XAPI in Dom0 to time out (among other issues).
It is probably not necessary to renice netback all the way to priority 0
as done in this commit. That is simply the value that we have tested. QA
has not reported any ill side-effects of this choice of value (yet). One
reasonable alternative, should any problems be noticed, would be to leave
netback at its default -5 priority and simply boost ovs-vswitchd's priority
to say -6 or -7.
Bug #1656.
Diffstat (limited to 'xenserver/etc_sysconfig_vswitch.example')
| -rw-r--r-- | xenserver/etc_sysconfig_vswitch.example | 7 |
1 files changed, 7 insertions, 0 deletions
diff --git a/xenserver/etc_sysconfig_vswitch.example b/xenserver/etc_sysconfig_vswitch.example index 789d61ab..ea8efe16 100644 --- a/xenserver/etc_sysconfig_vswitch.example +++ b/xenserver/etc_sysconfig_vswitch.example @@ -43,6 +43,13 @@ # processes. # VSWITCHD_PRIORITY=-5 +# VSWITCHD_NETBACK_PRIORITY: "nice" priority at which to run netback. +# It is a good idea to run ovs-vswitchd at a higher priority than +# netback to ensure that it gets enough CPU time to set up flows +# (bug #1656). Set this to 'default' to avoid changing netback's +# priority. +# VSWITCHD_NETBACK_PRIORITY=0 + # VSWITCHD_LOGFILE: File to send the FILE_LOGLEVEL log messages to. # VSWITCHD_LOGFILE=/var/log/ovs-vswitchd.log |