Lines Matching refs:kernel

4 The Open vSwitch kernel module allows flexible userspace control over
10 The kernel module implements multiple "datapaths" (analogous to
18 When a packet arrives on a vport, the kernel module processes it by
23 packets of the same type entirely in-kernel).
31 kernel module to remain relevant, it must be possible for newer
39 kernel module passes a packet to userspace, it also passes along the
42 kernel-provided version:
45       kernel's, then nothing special is necessary.
47     - If the kernel's flow key includes more fields than the userspace
48       version of the flow key, for example if the kernel decoded IPv6
52       as long as it uses the kernel-provided flow key to do it.
55       kernel's, for example if userspace decoded an IPv6 header but
56       the kernel stopped at the Ethernet type, then userspace can
58       kernel.  This case is bad for performance because every packet
59       that the kernel considers part of the flow must go to userspace,
107 Support for the mask Netlink attribute is optional for both the kernel and user
108 space program. The kernel can ignore the mask attribute, installing an exact
109 match flow, or reduce the number of don't care bits in the kernel to less than
111 that the kernel does not implement will simply result in additional flow setups.
112 The kernel module will also work with user space programs that neither support
115 Since the kernel may ignore or modify wildcard bits, it can be difficult for
117 two possible approaches: reactively install flows as they miss the kernel
119 or use the kernel's response messages to determine the installed wildcards.
121 When interacting with userspace, the kernel should maintain the match portion
125 by the kernel.
139 for both the kernel and user space program.
143 future operations. The kernel is not required to index flows by the original
163 through a few examples.  Suppose, for example, that the kernel module
186 across kernel versions even though it follows the compatibility rules.
204 Don't drop packets in the kernel for malformed protocol headers, bad
231 VLAN_TAG_PRESENT inside the kernel) is ordinarily set in a vlan
245     - When the kernel sends a given flow key to userspace, it always