Skip to content

Commit

Permalink
FAQ: Refine discussion of how to get a kernel module.
Browse files Browse the repository at this point in the history
This has come up a couple of times lately.

Signed-off-by: Ben Pfaff <[email protected]>
Acked-by: Russell Bryant <[email protected]>
  • Loading branch information
blp committed Apr 21, 2015
1 parent f4fa820 commit fcc369b
Showing 1 changed file with 17 additions and 8 deletions.
25 changes: 17 additions & 8 deletions FAQ.md
Original file line number Diff line number Diff line change
Expand Up @@ -173,14 +173,23 @@ A: The following table lists the Linux kernel versions against which the

What should I do?

A: If there is a newer version of Open vSwitch, consider building that
one, because it may support the kernel that you are building
against. (To find out, consult the table in the previous answer.)

Otherwise, use the Linux kernel module supplied with the kernel
that you are using. All versions of Open vSwitch userspace are
compatible with all versions of the Open vSwitch kernel module, so
this will also work. See also the following question.
A: You have the following options:

- Use the Linux kernel module supplied with the kernel that you are
using. (See also the following FAQ.)

- If there is a newer released version of Open vSwitch, consider
building that one, because it may support the kernel that you are
building against. (To find out, consult the table in the
previous FAQ.)

- The Open vSwitch "master" branch may support the kernel that you
are using, so consider building the kernel module from "master".

All versions of Open vSwitch userspace are compatible with all
versions of the Open vSwitch kernel module, so you do not have to
use the kernel module from one source along with the userspace
programs from the same source.

### Q: What features are not available in the Open vSwitch kernel datapath that ships as part of the upstream Linux kernel?

Expand Down

0 comments on commit fcc369b

Please sign in to comment.