Searched hist:e3cfddd577e763496c25ddb855cfff48b1174b63 (Results 1 – 3 of 3) sorted by relevance
| /openbmc/linux/include/trace/events/ |
| H A D | bridge.h | diff e3cfddd577e763496c25ddb855cfff48b1174b63 Thu Aug 31 00:18:13 CDT 2017 Roopa Prabhu <roopa@cumulusnetworks.com> bridge: add tracepoint in br_fdb_update
This extends bridge fdb table tracepoints to also cover
learned fdb entries in the br_fdb_update path. Note that
unlike other tracepoints I have moved this to when the fdb
is modified because this is in the datapath and can generate
a lot of noise in the trace output. br_fdb_update is also called
from added_by_user context in the NTF_USE case which is already
traced ..hence the !added_by_user check.
Signed-off-by: Roopa Prabhu <roopa@cumulusnetworks.com>
Acked-by: Nikolay Aleksandrov <nikolay@cumulusnetworks.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
|
| /openbmc/linux/net/core/ |
| H A D | net-traces.c | diff e3cfddd577e763496c25ddb855cfff48b1174b63 Thu Aug 31 00:18:13 CDT 2017 Roopa Prabhu <roopa@cumulusnetworks.com> bridge: add tracepoint in br_fdb_update
This extends bridge fdb table tracepoints to also cover
learned fdb entries in the br_fdb_update path. Note that
unlike other tracepoints I have moved this to when the fdb
is modified because this is in the datapath and can generate
a lot of noise in the trace output. br_fdb_update is also called
from added_by_user context in the NTF_USE case which is already
traced ..hence the !added_by_user check.
Signed-off-by: Roopa Prabhu <roopa@cumulusnetworks.com>
Acked-by: Nikolay Aleksandrov <nikolay@cumulusnetworks.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
|
| /openbmc/linux/net/bridge/ |
| H A D | br_fdb.c | diff e3cfddd577e763496c25ddb855cfff48b1174b63 Thu Aug 31 00:18:13 CDT 2017 Roopa Prabhu <roopa@cumulusnetworks.com> bridge: add tracepoint in br_fdb_update
This extends bridge fdb table tracepoints to also cover
learned fdb entries in the br_fdb_update path. Note that
unlike other tracepoints I have moved this to when the fdb
is modified because this is in the datapath and can generate
a lot of noise in the trace output. br_fdb_update is also called
from added_by_user context in the NTF_USE case which is already
traced ..hence the !added_by_user check.
Signed-off-by: Roopa Prabhu <roopa@cumulusnetworks.com>
Acked-by: Nikolay Aleksandrov <nikolay@cumulusnetworks.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
|