summaryrefslogtreecommitdiff
path: root/README.devel
diff options
context:
space:
mode:
authorVadim Kochan <vadim4j@gmail.com>2017-05-27 18:30:08 +0300
committerTobias Klauser <tklauser@distanz.ch>2017-05-30 09:26:30 +0200
commit83f11c231626f79433a021c526ffa1ac7521ae36 (patch)
tree72a3e0cfb3efd9e34455c8ad5d670a2e08900112 /README.devel
parent90b9483c806f0571988581c1712c7ca236c4a38c (diff)
flowtop: Improve and unify up/down scrolling
Move scrolling logic to the ui.c module, it requires to have some data iteration provided in flowtop.c and delegated to ui.c part. So approach is that now flowtop provides 2 additional callbacks for: 1) Iterate over flows/procs list 2) Draw flow/proc on each iteration which is controlled from ui.c it allows to unify scrolling logic and delegate it to the ui.c, in the future it should allow to easy handle press event on selected row and drow some additional information, or draw a cursor line per selected row. Also fixed case when down scrolling was bigger that printed rows, not it is handled by ui part. Signed-off-by: Vadim Kochan <vadim4j@gmail.com> Signed-off-by: Tobias Klauser <tklauser@distanz.ch>
Diffstat (limited to 'README.devel')
0 files changed, 0 insertions, 0 deletions
ht have been transformed by NAT, as the original direction 5-tuple represents the packet headers before any such transformation. When using the original direction 5-tuple the admissibility of return and/or related packets need not be based on the mere existence of a conntrack entry, allowing separation of admission policy from the established conntrack state. While existence of a conntrack entry is required for admission of the return or related packets, policy changes can render connections that were initially admitted to be rejected or dropped afterwards. If the admission of the return and related packets was based on mere conntrack state (e.g., connection being in an established state), a policy change that would make the connection rejected or dropped would need to find and delete all conntrack entries affected by such a change. When using the original direction 5-tuple matching the affected conntrack entries can be allowed to time out instead, as the established state of the connection would not need to be the basis for packet admission any more. It should be noted that the directionality of related connections may be the same or different than that of the master connection, and neither the original direction 5-tuple nor the conntrack state bits carry this information. If needed, the directionality of the master connection can be stored in master's conntrack mark or labels, which are automatically inherited by the expected related connections. The fact that neither ARP nor ND packets are trackable by conntrack allows mutual exclusion between ARP/ND and the new conntrack original tuple fields. Hence, the IP addresses are overlaid in union with ARP and ND fields. This allows the sw_flow_key to not grow much due to this patch, but it also means that we must be careful to never use the new key fields with ARP or ND packets. ARP is easy to distinguish and keep mutually exclusive based on the ethernet type, but ND being an ICMPv6 protocol requires a bit more attention. Signed-off-by: Jarno Rajahalme <jarno@ovn.org> Acked-by: Joe Stringer <joe@ovn.org> Acked-by: Pravin B Shelar <pshelar@ovn.org> Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'net')
-rw-r--r--net/openvswitch/actions.c2
-rw-r--r--net/openvswitch/conntrack.c86
-rw-r--r--net/openvswitch/conntrack.h10
-rw-r--r--net/openvswitch/flow.c34
-rw-r--r--net/openvswitch/flow.h49
-rw-r--r--net/openvswitch/flow_netlink.c85
-rw-r--r--net/openvswitch/flow_netlink.h7
7 files changed, 227 insertions, 46 deletions
diff --git a/net/openvswitch/actions.c b/net/openvswitch/actions.c