Re: [vpp-dev] sh hardware-interfaces extended stats are not showing up

[David Cornejo]

did you make sure that you have detailed stats collection enabled for
the interface?

(see vl_api_collect_detailed_interface_stats_t)

On Mon, Aug 26, 2019 at 2:24 PM carlito nueno  wrote:
>
> Hi all,
>
> I am using: vpp v19.08-release built by root on 365637461ad3 at Wed Aug 21 
> 18:20:49 UTC 2019
>
> When I do sh hardware-interfaces or sh hardware-interfaces detail or verbose, 
> extended stats are not showing.
>
> On 19.08 I only see stats like below:
>
> rss active:none
> tx burst function: eth_igb_xmit_pkts
> rx burst function: eth_igb_recv_scattered_pkts
>
> tx frames ok   26115
> tx bytes ok 34203511
> rx frames ok   12853
> rx bytes ok  1337944
>
> On 19.04 I am able to see:
>
> rss active:none
> tx burst function: eth_igb_xmit_pkts
> rx burst function: eth_igb_recv_scattered_pkts
>
> tx frames ok21535933
> tx bytes ok  21806938127
> rx frames ok13773533
> rx bytes ok   3642009224
> extended stats:
>   rx good packets   13773533
>   tx good packets   21535933
>   rx good bytes   3642009224
>   tx good bytes  21806938127
>   rx size 64 packets 1171276
>   rx size 65 to 127 packets  8462547
>   rx size 128 to 255 packets 1506266
>   rx size 256 to 511 packets  606052
>   rx size 512 to 1023 packets 560122
>   rx size 1024 to max packets1467270
>   rx broadcast packets383890
>   rx multicast packets291769
>   rx total packets  13773533
>   tx total packets  21535933
>   rx total bytes  3642009224
>   tx total bytes 21806938127
>   tx size 64 packets  397270
>   tx size 65 to 127 packets  3649953
>   tx size 128 to 255 packets 1817099
>   tx size 256 to 511 packets  976902
>   tx size 512 to 1023 packets 773963
>   tx size 1023 to max packets   13920746
>   tx multicast packets   893
>   tx broadcast packets356966
>   rx sent to host packets 59
>   tx sent by host packets 81
>
> Any advice on how to show extended stats on 19.08?
>
> Thanks!
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
>
> View/Reply Online (#13846): https://lists.fd.io/g/vpp-dev/message/13846
> Mute This Topic: https://lists.fd.io/mt/33041221/675628
> Group Owner: vpp-dev+ow...@lists.fd.io
> Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [d...@dogwood.com]
> -=-=-=-=-=-=-=-=-=-=-=-



-- 
Kailua, Hawaiʻi
US +1 (808) 728-3050
UK +44 (020) 3286 2808
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

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

Re: [vpp-dev] 19.04.2 and sub-numa cluster support

[Damjan Marion via Lists.Fd.Io]

> On 26 Aug 2019, at 20:00, sheckman  wrote:
> 
> We have been using vpp-18.07 and socket-mem to assign memory to the sub-numa 
> node where our vpp instances have been running in containers.
> 
> socket-mem 0,1024,0,0. e.g.
> 
> In 19.04, that has been deprecated.
> 
> Now, we get memory on ALL numa nodes, whether it's needed or not.
>  
> vpp# show dpdk physmem 
> Segment 0-0: IOVA:0xb8000, len:1073741824, virt:0x14000, socket_id:0, 
> hugepage_sz:1073741824, nchannel:0, nrank:0 fd:36
> Segment 2-0: IOVA:0x238000, len:1073741824, virt:0x1c8000, 
> socket_id:1, hugepage_sz:1073741824, nchannel:0, nrank:0 fd:37
> Segment 4-0: IOVA:0x178000, len:1073741824, virt:0x2d, 
> socket_id:2, hugepage_sz:1073741824, nchannel:0, nrank:0 fd:38
> Segment 6-0: IOVA:0x2f8000, len:1073741824, virt:0x3d8000, 
> socket_id:3, hugepage_sz:1073741824, nchannel:0, nrank:0 fd:39
> Segment 8-0: IOVA:0xc0920, len:2097152, virt:0x4dc020, socket_id:0, 
> hugepage_sz:2097152, nchannel:0, nrank:0 fd:25
>  
> Is there a new way to restrict memory allocation to specific nodes in 19.04?

Not at the moment. It shouldn't be too hard to add. If somebody volunteers to 
work on it iI will be happy to help...



-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

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

[vpp-dev] 19.04.2 and sub-numa cluster support

[sheckman]

We have been using vpp-18.07 and socket-mem to assign memory to the sub-numa 
node where our vpp instances have been running in containers.

socket-mem 0,1024,0,0. e.g.

In 19.04, that has been deprecated.

Now, we get memory on ALL numa nodes, whether it's needed or not.

vpp# show dpdk physmem
Segment 0-0: IOVA:0xb8000, len:1073741824, virt:0x14000, *socket_id:0* 
, hugepage_sz:1073741824, nchannel:0, nrank:0 fd:36
Segment 2-0: IOVA:0x238000, len:1073741824, virt:0x1c8000, 
*socket_id:1* , hugepage_sz:1073741824, nchannel:0, nrank:0 fd:37
Segment 4-0: IOVA:0x178000, len:1073741824, virt:0x2d, 
*socket_id:2,* hugepage_sz:1073741824, nchannel:0, nrank:0 fd:38
Segment 6-0: IOVA:0x2f8000, len:1073741824, virt:0x3d8000, 
*socket_id:3* , hugepage_sz:1073741824, nchannel:0, nrank:0 fd:39
Segment 8-0: IOVA:0xc0920, len:2097152, virt:0x4dc020, socket_id:0, 
hugepage_sz:2097152, nchannel:0, nrank:0 fd:25

Is there a new way to restrict memory allocation to specific nodes in 19.04?

Thanks,
Steve Heckman
Distinguished Software Engineer
Commscope/Arris
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

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

Re: [vpp-dev] [tsc] Project Proposal for uDPI

[Ni, Hongjun]

Welcome Alibaba join UDPI as a founder, and Pengjie Li, Zhao Zhang, Zhangpeng 
Xie as initial committers.

Thanks,
Hongjun

From: vpp-dev@lists.fd.io [mailto:vpp-dev@lists.fd.io] On Behalf Of Ni, Hongjun
Sent: Monday, August 19, 2019 8:10 AM
To: Ni, Hongjun ; Edward Warnicke 
Cc: t...@lists.fd.io; vpp-dev@lists.fd.io; Wang, Xiang W 
; Hong, Yang A ; Chang, Harry 
; gu.ji...@zte.com.cn; Shan Jianghua 
; Zhang Yang ; Li 
Xingfu ; Wu Shuai ; Xia Yuying 
; Fan Chenggang ; Gao Feng 
; Liu Zhong ; Zhao Yong 
; Chen Haiquan 
Subject: Re: [vpp-dev] [tsc] Project Proposal for uDPI


Welcome Netgate join UDPI as a founder and Jim Thompson as initial committer.

Thanks,
Hongjun

From: t...@lists.fd.io [mailto:t...@lists.fd.io] On 
Behalf Of Ni, Hongjun
Sent: Saturday, August 17, 2019 4:28 AM
To: Edward Warnicke mailto:hagb...@gmail.com>>
Cc: t...@lists.fd.io; 
vpp-dev@lists.fd.io; Wang, Xiang W 
mailto:xiang.w.w...@intel.com>>; Hong, Yang A 
mailto:yang.a.h...@intel.com>>; Chang, Harry 
mailto:harry.ch...@intel.com>>; 
gu.ji...@zte.com.cn; Shan Jianghua 
mailto:shanjia...@chinatelecom.cn>>; Zhang Yang 
mailto:zhangy@chinatelecom.cn>>; Li Xingfu 
mailto:lixin...@huachentel.com>>; Wu Shuai 
mailto:wush...@inspur.com>>; Xia Yuying 
mailto:yuying...@yxlink.com>>; Fan Chenggang 
mailto:fanchengg...@sunyainfo.com>>; Gao Feng 
mailto:davidf...@tencent.com>>; Liu Zhong 
mailto:liuzho...@chinaunicom.cn>>; Zhao Yong 
mailto:zhaoyon...@huawei.com>>; Chen Haiquan 
mailto:o...@yunify.com>>
Subject: Re: [vpp-dev] [tsc] Project Proposal for uDPI

Hi Ed,

The next TSC meeting on August 29 is preferable.

Thanks,
Hongjun

From: vpp-dev@lists.fd.io 
[mailto:vpp-dev@lists.fd.io] On Behalf Of Edward Warnicke
Sent: Thursday, August 15, 2019 3:13 AM
To: Ni, Hongjun mailto:hongjun...@intel.com>>
Cc: t...@lists.fd.io; 
vpp-dev@lists.fd.io; Wang, Xiang W 
mailto:xiang.w.w...@intel.com>>; Hong, Yang A 
mailto:yang.a.h...@intel.com>>; Chang, Harry 
mailto:harry.ch...@intel.com>>; 
gu.ji...@zte.com.cn; Shan Jianghua 
mailto:shanjia...@chinatelecom.cn>>; Zhang Yang 
mailto:zhangy@chinatelecom.cn>>; Li Xingfu 
mailto:lixin...@huachentel.com>>; Wu Shuai 
mailto:wush...@inspur.com>>; Xia Yuying 
mailto:yuying...@yxlink.com>>; Fan Chenggang 
mailto:fanchengg...@sunyainfo.com>>; Gao Feng 
mailto:davidf...@tencent.com>>; Liu Zhong 
mailto:liuzho...@chinaunicom.cn>>; Zhao Yong 
mailto:zhaoyon...@huawei.com>>; Chen Haiquan 
mailto:o...@yunify.com>>
Subject: Re: [vpp-dev] [tsc] Project Proposal for uDPI

Do you have a preference as to dates?

Ed

On Tue, Aug 13, 2019 at 7:44 PM Ni, Hongjun 
mailto:hongjun...@intel.com>> wrote:
Hi Ed,

Thank you for scheduling the proposal review.

I think a TSC meeting after Aug 21 is better, to follow the FD.io TSC policy.

Thanks,
Hongjun

From: Ed Warnicke [mailto:hagb...@gmail.com]
Sent: Wednesday, August 14, 2019 5:09 AM
To: Ni, Hongjun mailto:hongjun...@intel.com>>
Cc: t...@lists.fd.io; 
vpp-dev@lists.fd.io; Wang, Xiang W 
mailto:xiang.w.w...@intel.com>>; Hong, Yang A 
mailto:yang.a.h...@intel.com>>; Chang, Harry 
mailto:harry.ch...@intel.com>>; 
gu.ji...@zte.com.cn; Shan Jianghua 
mailto:shanjia...@chinatelecom.cn>>; Zhang Yang 
mailto:zhangy@chinatelecom.cn>>; Li Xingfu 
mailto:lixin...@huachentel.com>>; Wu Shuai 
mailto:wush...@inspur.com>>; Xia Yuying 
mailto:yuying...@yxlink.com>>; Fan Chenggang 
mailto:fanchengg...@sunyainfo.com>>; Gao Feng 
mailto:davidf...@tencent.com>>; Liu Zhong 
mailto:liuzho...@chinaunicom.cn>>; Zhao Yong 
mailto:zhaoyon...@huawei.com>>; Chen Haiquan 
mailto:o...@yunify.com>>
Subject: Re: [tsc] Project Proposal for uDPI

Hongjun,

You guys are eligible for project creation review starting at the Aug 21 TSC 
meeting I believe (based on sending the notification to the TSC on Aug 8) ... 
when would you like to schedule for that Thu's TSC meeting, or a subsequent one?

Ed

On Thu, Aug 8, 2019 at 8:11 PM Ni, Hongjun 
mailto:hongjun...@intel.com>> wrote:
Hello FD.io TSCs

Please accept this project proposal for uDPI for consideration.
https://wiki.fd.io/view/Project_Proposals/uDPI

So far, this project has 11 founders and 15 initial committers from
Intel, ZTE, China Telecom, HuachenTel, Inspur, Yxlink, Sunyainfo, Tencent, 
China Unicom, Huawei, QingCloud.

If possible, I would like to present this on TSC meeting.

Thanks,
Hongjun
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#1070): https://lists.fd.io/g/tsc/message/1070
Mute This Topic: https://lists.fd.io/mt/32805806/464962
Group Owner: tsc+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/tsc/unsub  

Re: [vpp-dev] FD.io Jenkins Maintenance: 2019-08-29 @ 1700 UTC and 2019-08-30 @ 1700 UTC

[Vanessa Valderrama]

*Maintenance Reminder*


On 08/22/2019 12:00 PM, Vanessa Valderrama wrote:
>
> *What:*
>
>   * Jenkins upgrade to version 2.176.3 LTS
>   * Jenkins OS updates
>   * Jenkins plug-in updates
>
>
> *When:*
> Jenkins sandbox - 2019-08-29 @ 1700 UTC
> Jenkins production - 2019-08-30 @ 1700 UTC
>
> *Impact:*
> This maintenance requires a reboot of Jenkins.  Jenkins will be placed
> in shutdown mode at 1600 UTC. We will terminate jobs at 1700 UTC
>
>   * Jenkins sandbox
>   o Status page -
> https://status.linuxfoundation.org/incidents/96lw8jk1xpxp
>   * Jenkins production
>   o Status page -
> https://status.linuxfoundation.org/incidents/4hzxy36qm7y1
>
> *Why:*
> Jenkins version 2.176.3 LTS will contain fixes for high severity
> security issues present in the current version of Jenkins.
>
>   * Jenkins Security Advisories - https://jenkins.io/security/advisories/
>   * Jenkins Changelog - https://jenkins.io/changelog-stable/
>
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

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

Re: [vpp-dev] Ownership of src/vnet/cop/

[Jim Thompson via Lists.Fd.Io]

https://github.com/FDio/vpp/blob/master/src/vnet/cop/cop.api#L33

I think it’s more metaphor than acronym. 


> On Aug 26, 2019, at 5:52 AM, Ray Kinsella  wrote:
> 
> Better yet - does anyone know what COP is an abbreviation of?
> 
> Ray K
> 
>> On 26/08/2019 09:06, Ole Troan wrote:
>> If not, I will put a "orphaned" status in FEATURE.yaml and NN in MAINTAINERS.
> 
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> 
> View/Reply Online (#13840): https://lists.fd.io/g/vpp-dev/message/13840
> Mute This Topic: https://lists.fd.io/mt/33030661/675164
> Group Owner: vpp-dev+ow...@lists.fd.io
> Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [j...@netgate.com]
> -=-=-=-=-=-=-=-=-=-=-=-
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

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

Re: [vpp-dev] Ownership of src/vnet/cop/

[Ray Kinsella]

Better yet - does anyone know what COP is an abbreviation of?

Ray K

On 26/08/2019 09:06, Ole Troan wrote:
> If not, I will put a "orphaned" status in FEATURE.yaml and NN in MAINTAINERS.



signature.asc
Description: OpenPGP digital signature
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

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

[vpp-dev] Ownership of src/vnet/cop/

[Ole Troan]

What ho,

Does anyone feel they own the src/vnet/cop/ feature?

If not, I will put a "orphaned" status in FEATURE.yaml and NN in MAINTAINERS.

Best regards,
Ole
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

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