2016-06-15 6:37 GMT-07:00 Ryan Moats :
> "dev" wrote on 06/14/2016 08:58:33 PM:
>
> > From: Daniele Di Proietto
> > To: Nirapada Ghosh/San Jose/IBM@IBMUS
> > Cc: "dev@openvswitch.org"
> > Date: 06/14/2016 08:59 PM
> > Subject: Re: [o
not aligh with the ovn-northd implementation. Did I
> miss anything
> when compiling openvswitch source code (I used default ./configure; make
> to generate
> the ovn-northd execuable)? Thanks.
>
> - Hui
>
> > From: Daniele Di Proietto
> > To: Nirapada Ghosh/San J
"dev" wrote on 06/14/2016 08:58:33 PM:
> From: Daniele Di Proietto
> To: Nirapada Ghosh/San Jose/IBM@IBMUS
> Cc: "dev@openvswitch.org"
> Date: 06/14/2016 08:59 PM
> Subject: Re: [ovs-dev] [PATCH V5] Function tracer to trace all function
calls
> Sen
./configure; make to
generate
the ovn-northd execuable)? Thanks.
- Hui
> From: Daniele Di Proietto
> To: Nirapada Ghosh/San Jose/IBM@IBMUS
> Cc: "dev@openvswitch.org"
> Date: 06/14/2016 09:58 PM
> Subject: Re: [ovs-dev] [PATCH V5] Function tracer to trace all function
calls
Hi Nirapada,
When optimizing for the DPDK datapath we have a very similar problem and,
usually, running a simple profiler like perf (
https://perf.wiki.kernel.org/index.php/Main_Page) is enough to highlight
the bottlenecks in terms of CPU usage.
Have you tried perf? Does this infrastructure provi
