Re: [ovs-dev] [PATCH V14] Function tracer to trace all function calls

2016-08-08 Thread Ryan Moats
"dev" wrote on 08/05/2016 10:51:38 PM: > From: Nirapada Ghosh/San Jose/IBM@IBMUS > To: dev@openvswitch.org > Date: 08/05/2016 10:52 PM > Subject: [ovs-dev] [PATCH V14] Function tracer to trace all function calls > Sent by: "dev" > > From: Nirapada Ghosh

Re: [ovs-dev] [PATCH V14] Function tracer to trace all function calls

2016-08-06 Thread Ryan Moats
"dev" wrote on 08/05/2016 10:51:38 PM: > From: Nirapada Ghosh/San Jose/IBM@IBMUS > To: dev@openvswitch.org > Date: 08/05/2016 10:52 PM > Subject: [ovs-dev] [PATCH V14] Function tracer to trace all function calls > Sent by: "dev" > > From: Nirapada Ghosh

[ovs-dev] [PATCH V14] Function tracer to trace all function calls

2016-08-05 Thread nghosh
From: Nirapada Ghosh In some circumstances, we might need to figure out where in code, the CPU time is being spent most, so as to pinpoint the bottleneck and thereby resolve it with proper changes. Using '-finstrument-functions' flag, that can be achieved, and this patch exactly does that. There