Hi Ole,
Many Thanks for your quick response. it explains why I see different
numbers when the works threads number is changed in startup.conf. I will
have a look at vpptop as well.
Best Regards,

On Fri, Jan 3, 2020 at 11:45 AM <otr...@employees.org> wrote:

> Hi Sunny,
>
> > I am new to VPP and am using vpp_get_stats to check some counters on the
> interfaces.
> > if I run the command, I get the following output:
> > vpp version used: vpp v19.04.1-release
> >
> > [root@idn_upf_ntsn /]# vpp_get_stats dump  if/names  if/drops$
> > [0]: local0 /if/names
> > [1]: host-eth /if/names
> > [2]: tunnel0 /if/names
> > [0 @ 0]: 0 packets /if/drops
> > [1 @ 0]: 0 packets /if/drops
> > [2 @ 0]: 0 packets /if/drops
> > [0 @ 1]: 0 packets /if/drops
> > [1 @ 1]: 19614 packets /if/drops
> > [2 @ 1]: 0 packets /if/drops
> > [0 @ 2]: 0 packets /if/drops
> > [1 @ 2]: 0 packets /if/drops
> > [2 @ 2]: 0 packets /if/drops
> > [0 @ 3]: 0 packets /if/drops
> > [1 @ 3]: 0 packets /if/drops
> > [2 @ 3]: 0 packets /if/drops
> >
> > As you can see that there are 3 software interface Ids. but the second
> number after character "@"
> > what does it denote? Many thanks for your help in advance.
>
> The second number is the worker index.
> The interface counters are arranged as a two dimensional array in shared
> memory. First dimension is thread_index second is sw_if_index.
>
> vpp_get_stats was something I wrote as an example application for the C
> stats library.
> There are various integrations using the stats API that might be of
> interest.
> vpptop was pretty cool as a standalone application. Not sure if it's well
> maintained.
> https://github.com/PantheonTechnologies/vpptop
>
> Best regards,
> Ole
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#15042): https://lists.fd.io/g/vpp-dev/message/15042
Mute This Topic: https://lists.fd.io/mt/69405067/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to