Thanks Ilya,
Sorry your emails were going into social media folder on gmail :(, just saw
it.
One more thing I notice, that the idle and busy cycles %ages will drift if
I leave the traffic running over night....I was expecting them to stay same
for the same traffic pattern.
Thanks, Shahaji

On Tue, Sep 25, 2018 at 6:36 AM Ilya Maximets <[email protected]>
wrote:

> Hi.
>
> "Cycles" are the total number of cycles measured for
> the period. The number of GHz is just that number divided
> by the time, i.e it should be equal to your TSC frequency.
>
> I think we need to clarify it more, because it's unclear.
> On x86 systems this number will usually be equal to the
> CPU frequency, but on ARM you have completely different
> TSC source with its own frequency.
>
> For example, on my ARM board I have only 0.10 GHz for TSC,
> but 2.0 GHz for CPU.
>
> I'll send a patch to clarify that misunderstanding.
>
> Best regards, Ilya Maximets.
>
> On 24.09.2018 22:28, Shahaji Bhosle wrote:
> > Hi Ilya,
> >
> > I was trying the above command and was wondering what "Cycles:"
> represents? Should this match my CPU frequency? It is not matching to my
> ARM cores, so wondering. Thanks, Shahaji
> >
> >
> >> pmd thread numa_id 0 core_id 1:
> >>
> >>   Cycles:            2419034712  (2.40 GHz)
> >>   Iterations:            572817  (1.76 us/it)
> >>   - idle:                486808  (15.9 % cycles)
> >>   - busy:                 86009  (84.1 % cycles)
> >>   Rx packets:           2399607  (2381 Kpps, 848 cycles/pkt)
> >>   Datapath passes:      3599415  (1.50 passes/pkt)
> >>   - EMC hits:            336472  ( 9.3 %)
> >>   - Megaflow hits:      3262943  (90.7 %, 1.00 subtbl lookups/hit)
> >>   - Upcalls:                  0  ( 0.0 %, 0.0 us/upcall)
> >>   - Lost upcalls:             0  ( 0.0 %)
> >>   Tx packets:           2399607  (2381 Kpps)
> >>   Tx batches:            171400  (14.00 pkts/batch)
>
>
>
_______________________________________________
dev mailing list
[email protected]
https://mail.openvswitch.org/mailman/listinfo/ovs-dev

Reply via email to