#undef TRACE_SYSTEM #define TRACE_SYSTEM gpio #ifndef CONFIG_TRACING_EVENTS_GPIO #define NOTRACE #endif #if !defined(_TRACE_GPIO_H) || defined(TRACE_HEADER_MULTI_READ) #define _TRACE_GPIO_H #include TRACE_EVENT(gpio_direction, TP_PROTO(unsigned gpio, int in, int err), TP_ARGS(gpio, in, err), TP_STRUCT__entry( __field(unsigned, gpio) __field(int, in) __field(int, err) ), TP_fast_assign( __entry->gpio = gpio; __entry->in = in; __entry->err = err; ), TP_printk("%u %3s (%d)", __entry->gpio, __entry->in ? "in" : "out", __entry->err) ); TRACE_EVENT(gpio_value, TP_PROTO(unsigned gpio, int get, int value), TP_ARGS(gpio, get, value), TP_STRUCT__entry( __field(unsigned, gpio) __field(int, get) __field(int, value) ), TP_fast_assign( __entry->gpio = gpio; __entry->get = get; __entry->value = value; ), TP_printk("%u %3s %d", __entry->gpio, __entry->get ? "get" : "set", __entry->value) ); #endif /* if !defined(_TRACE_GPIO_H) || defined(TRACE_HEADER_MULTI_READ) */ /* This part must be outside protection */ #include ed'>master net-next plumbingsTobias Klauser
summaryrefslogtreecommitdiff
AgeCommit message (Collapse)AuthorFilesLines
2017-02-03bridge: per vlan dst_metadata netlink supportRoopa Prabhu1-2/+3
This patch adds support to attach per vlan tunnel info dst metadata. This enables bridge driver to map vlan to tunnel_info at ingress and egress. It uses the kernel dst_metadata infrastructure. The initial use case is vlan to vni bridging, but the api is generic to extend to any tunnel_info in the future: - Uapi to configure/unconfigure/dump per vlan tunnel data - netlink functions to configure vlan and tunnel_info mapping - Introduces bridge port flag BR_LWT_VLAN to enable attach/detach dst_metadata to bridged packets on ports. off by default. - changes to existing code is mainly refactor some existing vlan handling netlink code + hooks for new vlan tunnel code - I have kept the vlan tunnel code isolated in separate files. - most of the netlink vlan tunnel code is handling of vlan-tunid ranges (follows the vlan range handling code). To conserve space vlan-tunid by default are always dumped in ranges if applicable. Use case: example use for this is a vxlan bridging gateway or vtep which maps vlans to vn-segments (or vnis). iproute2 example (patched and pruned iproute2 output to just show relevant fdb entries): example shows same host mac learnt on two vni's and vlan 100 maps to vni 1000, vlan 101 maps to vni 1001 before (netdev per vni): $bridge fdb show | grep "00:02:00:00:00:03" 00:02:00:00:00:03 dev vxlan1001 vlan 101 master bridge 00:02:00:00:00:03 dev vxlan1001 dst 12.0.0.8 self 00:02:00:00:00:03 dev vxlan1000 vlan 100 master bridge 00:02:00:00:00:03 dev vxlan1000 dst 12.0.0.8 self after this patch with collect metdata in bridged mode (single netdev): $bridge fdb show | grep "00:02:00:00:00:03" 00:02:00:00:00:03 dev vxlan0 vlan 101 master bridge 00:02:00:00:00:03 dev vxlan0 src_vni 1001 dst 12.0.0.8 self 00:02:00:00:00:03 dev vxlan0 vlan 100 master bridge 00:02:00:00:00:03 dev vxlan0 src_vni 1000 dst 12.0.0.8 self CC: Nikolay Aleksandrov <nikolay@cumulusnetworks.com> Signed-off-by: Roopa Prabhu <roopa@cumulusnetworks.com> Signed-off-by: David S. Miller <davem@davemloft.net>