projects
/
openvswitch
/ blobdiff
commit
grep
author
committer
pickaxe
?
search:
re
summary
|
shortlog
|
log
|
commit
|
commitdiff
|
tree
raw
|
inline
| side by side
meta-flow: Reduce redundant transport set/get code
[openvswitch]
/
INSTALL.Linux
diff --git
a/INSTALL.Linux
b/INSTALL.Linux
index da992b57d4f9eebf14c9cee77c92c3d8c3464aff..78152b6940f7a6a5b04847d014b38a7c6352d121 100644
(file)
--- a/
INSTALL.Linux
+++ b/
INSTALL.Linux
@@
-100,6
+100,14
@@
you have the following:
- Python 2.x, for x >= 4.
- Python 2.x, for x >= 4.
+If you are going to extensively modify Open vSwitch, please consider
+installing the following to obtain better warnings:
+
+ - "sparse" version 0.4.4 or later
+ (http://www.kernel.org/pub/software/devel/sparse/dist/).
+
+ - GNU make.
+
Installation Requirements
-------------------------
Installation Requirements
-------------------------
@@
-187,6
+195,9
@@
Prerequisites section, follow the procedure below to build.
% make
% make
+ For improved warnings if you installed "sparse" (see
+ "Prerequisites"), add C=1 to the "make" command line.
+
4. Become root by running "su" or another program.
5. Run "make install" to install the executables and manpages into the
4. Become root by running "su" or another program.
5. Run "make install" to install the executables and manpages into the
@@
-194,16
+205,16
@@
Prerequisites section, follow the procedure below to build.
6. If you built kernel modules, you may load them with "insmod", e.g.:
6. If you built kernel modules, you may load them with "insmod", e.g.:
- % insmod datapath/linux/openvswitch
_mod
.ko
+ % insmod datapath/linux/openvswitch.ko
You may need to specify a full path to insmod, e.g. /sbin/insmod.
To verify that the modules have been loaded, run "/sbin/lsmod" and
You may need to specify a full path to insmod, e.g. /sbin/insmod.
To verify that the modules have been loaded, run "/sbin/lsmod" and
- check that openvswitch
_mod
is listed.
+ check that openvswitch is listed.
If the "insmod" operation fails, look at the last few kernel log
messages (e.g. with "dmesg | tail"):
If the "insmod" operation fails, look at the last few kernel log
messages (e.g. with "dmesg | tail"):
- - The message "openvswitch
_mod
: exports duplicate symbol
+ - The message "openvswitch: exports duplicate symbol
br_should_route_hook (owned by bridge)" means that the bridge
module is loaded. Run "/sbin/rmmod bridge" to remove it.
br_should_route_hook (owned by bridge)" means that the bridge
module is loaded. Run "/sbin/rmmod bridge" to remove it.
@@
-212,7
+223,7
@@
Prerequisites section, follow the procedure below to build.
the kernel, rather than as a module. Open vSwitch does not
support this configuration (see "Build Requirements", above).
the kernel, rather than as a module. Open vSwitch does not
support this configuration (see "Build Requirements", above).
- - The message "openvswitch
_mod
: exports duplicate symbol
+ - The message "openvswitch: exports duplicate symbol
dp_ioctl_hook (owned by ofdatapath)" means that the ofdatapath
module from the OpenFlow reference implementation is loaded.
Run "/sbin/rmmod ofdatapath" to remove it. (You might have to
dp_ioctl_hook (owned by ofdatapath)" means that the ofdatapath
module from the OpenFlow reference implementation is loaded.
Run "/sbin/rmmod ofdatapath" to remove it. (You might have to
@@
-222,10
+233,10
@@
Prerequisites section, follow the procedure below to build.
- Otherwise, the most likely problem is that Open vSwitch was
built for a kernel different from the one into which you are
- Otherwise, the most likely problem is that Open vSwitch was
built for a kernel different from the one into which you are
- trying to load it. Run "modinfo" on openvswitch
_mod
.ko and on
+ trying to load it. Run "modinfo" on openvswitch.ko and on
a module built for the running kernel, e.g.:
a module built for the running kernel, e.g.:
- % /sbin/modinfo openvswitch
_mod
.ko
+ % /sbin/modinfo openvswitch.ko
% /sbin/modinfo /lib/modules/`uname -r`/kernel/net/bridge/bridge.ko
Compare the "vermagic" lines output by the two commands. If
% /sbin/modinfo /lib/modules/`uname -r`/kernel/net/bridge/bridge.ko
Compare the "vermagic" lines output by the two commands. If
@@
-235,7
+246,7
@@
Prerequisites section, follow the procedure below to build.
module loading, please include the output from the "dmesg" and
"modinfo" commands mentioned above.
module loading, please include the output from the "dmesg" and
"modinfo" commands mentioned above.
- There is an optional module parameter to openvswitch
_mod
.ko called
+ There is an optional module parameter to openvswitch.ko called
vlan_tso that enables TCP segmentation offload over VLANs on NICs
that support it. Many drivers do not expose support for TSO on VLANs
in a way that Open vSwitch can use but there is no way to detect
vlan_tso that enables TCP segmentation offload over VLANs on NICs
that support it. Many drivers do not expose support for TSO on VLANs
in a way that Open vSwitch can use but there is no way to detect
@@
-302,7
+313,7
@@
also upgrade the database schema:
1. Stop the Open vSwitch daemons, e.g.:
1. Stop the Open vSwitch daemons, e.g.:
- % kill `cd /usr/local/var/run && cat ovsdb-server.pid ovs-vswitchd.pid`
+ % kill `cd /usr/local/var/run
/openvswitch
&& cat ovsdb-server.pid ovs-vswitchd.pid`
2. Install the new Open vSwitch release.
2. Install the new Open vSwitch release.