[FD.io Helpdesk #56282] [linuxfoundation.org #56282] RE: [EXTERNAL] [vpp-dev] git.fd.io not updating

[Luke, Chris via RT]

The mirror to github[1] has the same last commit, too.

https://github.com/FDio/vpp/commits/master

Chris.

From: vpp-dev@lists.fd.io  On Behalf Of Florin Coras
Sent: Monday, May 21, 2018 19:35
To: helpd...@fd.io
Cc: vpp-dev ; Vanessa Valderrama 

Subject: [EXTERNAL] [vpp-dev] git.fd.io not updating

Hi,

It would seem that git.fd.io [1] thinks that we last 
committed a patch to vpp almost 1 week ago. Any idea what might’ve triggered 
this?

Thanks,
Florin

[1] https://git.fd.io/vpp/log/




-=-=-=-=-=-=-=-=-=-=-=-
Links:

You receive all messages sent to this group.

View/Reply Online (#9355): https://lists.fd.io/g/vpp-dev/message/9355
View All Messages In Topic (1): https://lists.fd.io/g/vpp-dev/topic/19743863
Mute This Topic: https://lists.fd.io/mt/19743863/21656
New Topic: https://lists.fd.io/g/vpp-dev/post

Change Your Subscription: https://lists.fd.io/g/vpp-dev/editsub/21656
Group Home: https://lists.fd.io/g/vpp-dev
Contact Group Owner: vpp-dev+ow...@lists.fd.io
Terms of Service: https://lists.fd.io/static/tos
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] SCTP coverity-scan warnings addressed

[Luke, Chris]

Great, thanks!

Chris

> -Original Message-
> From: Marco Varlese [mailto:mvarl...@suse.de]
> Sent: Thursday, February 8, 2018 5:16
> To: Luke, Chris <chris_l...@cable.comcast.com>
> Cc: Florin Coras <fcoras.li...@gmail.com>; vpp-dev@lists.fd.io
> Subject: SCTP coverity-scan warnings addressed
> 
> Hi Chris,
> 
> Just to update you that I took care of the action item which came up during
> the VPP project-meeting on Tuesday.
> 
> The patch https://gerrit.fd.io/r/#/c/10433/ addressing the warnings (8) re
> SCTP was merged.
> 
> 
> Cheers,
> --
> Marco V
> 
> SUSE LINUX GmbH | GF: Felix Imendörffer, Jane Smithard, Graham Norton
> HRB 21284 (AG Nürnberg) Maxfeldstr. 5, D-90409, Nürnberg

___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] New Committer Nomination: Marco Varlese

[Luke, Chris]

Doh. :)

From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On 
Behalf Of Dave Barach (dbarach)
Sent: Tuesday, February 6, 2018 12:07
To: vpp-dev@lists.fd.io
Subject: [vpp-dev] FW: New Committer Nomination: Marco Varlese

Copying the list...

From: Luke, Chris [mailto:chris_l...@comcast.com]
Sent: Tuesday, February 6, 2018 11:40 AM
To: Dave Barach (dbarach) <dbar...@cisco.com<mailto:dbar...@cisco.com>>; Keith 
Burns (krb) <k...@cisco.com<mailto:k...@cisco.com>>; Florin Coras (fcoras) 
<fco...@cisco.com<mailto:fco...@cisco.com>>; John Lo (loj) 
<l...@cisco.com<mailto:l...@cisco.com>>; Damjan Marion (damarion) 
<damar...@cisco.com<mailto:damar...@cisco.com>>; Neale Ranns (nranns) 
<nra...@cisco.com<mailto:nra...@cisco.com>>; Ole Troan 
<o...@cisco.com<mailto:o...@cisco.com>>; Dave Wallace 
<dwallac...@gmail.com<mailto:dwallac...@gmail.com>>; Ed Warnicke (eaw) 
<e...@cisco.com<mailto:e...@cisco.com>>
Subject: RE: New Committer Nomination: Marco Varlese

+1

From: Dave Barach (dbarach) [mailto:dbar...@cisco.com]
Sent: Tuesday, February 6, 2018 8:56
To: Keith Burns (krb) <k...@cisco.com<mailto:k...@cisco.com>>; Florin Coras 
(fcoras) <fco...@cisco.com<mailto:fco...@cisco.com>>; John Lo (loj) 
<l...@cisco.com<mailto:l...@cisco.com>>; Luke, Chris 
<chris_l...@cable.comcast.com<mailto:chris_l...@cable.comcast.com>>; Damjan 
Marion (damarion) <damar...@cisco.com<mailto:damar...@cisco.com>>; Neale Ranns 
(nranns) <nra...@cisco.com<mailto:nra...@cisco.com>>; Ole Troan 
<o...@cisco.com<mailto:o...@cisco.com>>; Dave Wallace 
<dwallac...@gmail.com<mailto:dwallac...@gmail.com>>; Ed Warnicke (eaw) 
<e...@cisco.com<mailto:e...@cisco.com>>
Subject: New Committer Nomination: Marco Varlese

Folks,

In view of significant code contributions to the vpp project - see below - I'm 
pleased to nominate Marco Varlese as a vpp project committer. I have high 
confidence that he'll be a major asset to the project in a committer role.

Marco has contributed 46 merged patches, including significant new feature 
work.  Example: host stack implementation of SCTP, 8 KLOC 
https://gerrit.fd.io/r/#/c/9150.


Please vote (+1, 0, -1) on vpp-dev@lists.fd.io<mailto:vpp-dev@lists.fd.io>. 
We'll need a recorded vote so that the TSC will approve Marco's nomination.

Thanks... Dave

___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

[vpp-dev] 18.04 tentative release plan

[Luke, Chris]

All,

For any who didn't hear, somehow I've ended up the release manager for 18.04, 
following in the footsteps of others whose notes Dave Wallace has done a 
sterling job coalescing into something I think even I can grok.

I've posted the tentative release plan for 18.04 in the usual place 
(https://wiki.fd.io/view/Projects/vpp/Release_Plans/Release_Plan_18.04) - 
please review the proposed dates and feel free to add release deliverables you 
think you will be producing for 18.04.

Unfortunately I won't be able to make the dev call tomorrow, but please do 
raise any concerns with the release plan there or here on the dev list.

Cheers,
Chris.

___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] [csit-dev] VPP 18.01 Release artifacts are now available on nexus.fd.io

[Luke, Chris]

Woohoo!

From: csit-dev-boun...@lists.fd.io [mailto:csit-dev-boun...@lists.fd.io] On 
Behalf Of Dave Wallace
Sent: Thursday, January 25, 2018 0:23
To: vpp-dev@lists.fd.io; csit-...@lists.fd.io
Subject: [csit-dev] VPP 18.01 Release artifacts are now available on nexus.fd.io

Folks,

The VPP 18.01 Release artifacts are now available on nexus.fd.io

The ubuntu.xenial and centos packages can be installed following the recipe on 
the wiki: https://wiki.fd.io/view/VPP/Installing_VPP_binaries_from_packages

Thank you to all of the VPP community who have contributed to the 18.01 VPP 
Release.


Elvis has left the building!
-daw-
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] sudo vppctl

[Luke, Chris]

I suggest at least a modicum of online searching for trivial issues like this, 
please.

See https://wiki.fd.io/view/VPP/Command-line_Arguments#.22unix.22_parameters 
and look at “cli-listen”. Typically placed inside the VPP startup config file.

Chris.

From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On 
Behalf Of 15803846349
Sent: Saturday, December 16, 2017 3:38
To: vpp-dev ; Damjan Marion (damarion) 
; Klement Sekera -X (ksekera - PANTHEON TECHNOLOGIES at 
Cisco) 
Subject: [vpp-dev] sudo vppctl

Hi, everyone
After installed vpp, we sudo service vpp start.But, sudo vppctl, it show as 
follows:
clib_socket_init: connect (fd 3, '/run/vpp/cli.sock'): Connection refused
WHY?


来自 魅族 MX4 Pro
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] How can i use VPP as MPLS PE/P device

[Luke, Chris]

But to make sure we’re clear, while VPP can provide the dataplane of a P/PE, 
but something else has to provide the control plane (eg, LDP, BGP, SDN 
controller, etc)

 

Chris.

 

From:  on behalf of "Neale Ranns (nranns)" 

Date: Wednesday, December 6, 2017 at 09:33
To: "wangchuan...@163.com" , vpp-dev 
Subject: Re: [vpp-dev] How can i use VPP as MPLS PE/P device

 

 

Another hastily assembled, on-demand guide:

  https://wiki.fd.io/view/VPP/MPLS_FIB

 

/neale

 

From:  on behalf of "wangchuan...@163.com" 

Date: Wednesday, 6 December 2017 at 09:11
To: vpp-dev 
Subject: [vpp-dev] How can i use VPP as MPLS PE/P device

 

hi all，

I want to configure my testing MPLS network.

how can I configure VPP to act as PE or P using CLI cmd?

who can help?




best regards!

 

simon wang



smime.p7s
Description: S/MIME cryptographic signature
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] memory issues

[Luke, Chris]

I agree 5g is large, but I do not think this is the FIB. The default heap maxes 
out much sooner than that. Something else is going on.

 

For DPDK, “show dpdk buffer” and otherwise “show physmem”.

 

Chris.

 

From: 薛欣颖 <xy...@fiberhome.com>
Date: Tuesday, December 5, 2017 at 20:06
To: Chris Luke <chris_l...@cable.comcast.com>, vpp-dev <vpp-dev@lists.fd.io>
Subject: Re: Re: [vpp-dev] memory issues

 

 

Hi Chris，

I see what you mean. I have two other questions: 
1. 200k static routing use 5g memory is also  large , how can I configure it 
use less physical memory?
2. How can I check the packet buffer memory?

BTW, do you have the test similar with 'the memory size 200k static routing 
use'?

Thanks,
Xyxue

 

From: Luke, Chris

Date: 2017-12-05 21:43

To: 薛欣颖; vpp-dev

Subject: Re: [vpp-dev] memory issues

You’re misreading top. “Virt” only means the virtual memory footprint of the 
process. This includes unused heap, shared libraries, anonymous mmap() regions 
etc. “RSS” is the resident-in-memory size. It’s actually using 5G.

 

“show memory” also only shows the heap usage, it does not include packet buffer 
memory.

 

Chris.

 

From: <vpp-dev-boun...@lists.fd.io> on behalf of 薛欣颖 <xy...@fiberhome.com>
Date: Tuesday, December 5, 2017 at 00:51
To: vpp-dev <vpp-dev@lists.fd.io>
Subject: [vpp-dev] memory issues

 

 

Hi guys，

I am using vpp v18.01-rc0~241-g4c9f2a8.
I configured 200K static routing. When I 'show memory' in VPP, '150+k used'. 
But in my machine ,used almost 15g. After del the static routing ,almost using 
16g memory.
More info is shown below:


VPP# show memory 
Thread 0 vpp_main
heap 0x7fffb58e9000, 1076983 objects, 110755k of 151671k used, 15386k free, 
13352k reclaimed, 16829k overhead, 1048572k capacity
User heap index=0:
heap 0x7fffb58e9000, 1076984 objects, 110755k of 151671k used, 15386k free, 
13352k reclaimed, 16829k overhead, 1048572k capacity
User heap index=1:
heap 0x77ed4000, 2 objects, 128k of 130k used, 92 free, 0 reclaimed, 1k 
overhead, 1020k capacity
User heap index=2:
heap 0x7fffb1e28000, 2 objects, 512k of 514k used, 92 free, 0 reclaimed, 1k 
overhead, 8188k capacity
User heap index=3:
heap 0x7fffb1628000, 2 objects, 512k of 514k used, 92 free, 0 reclaimed, 1k 
overhead, 8188k capacity
User heap index=4:
heap 0x7fffaf628000, 2 objects, 512k of 514k used, 92 free, 0 reclaimed, 1k 
overhead, 32764k capacity
User heap index=5:
heap 0x7fffaf528000, 2 objects, 8k of 10k used, 92 free, 0 reclaimed, 1k 
overhead, 1020k capacity
User heap index=6:
heap 0x7fffaf428000, 2 objects, 8k of 10k used, 92 free, 0 reclaimed, 1k 
overhead, 1020k capacity
User heap index=7:
heap 0x7fffaf328000, 2 objects, 120k of 122k used, 92 free, 0 reclaimed, 1k 
overhead, 1020k capacity
User heap index=8:
heap 0x7fffaf228000, 2 objects, 120k of 122k used, 92 free, 0 reclaimed, 1k 
overhead, 1020k capacity
User heap index=9:
heap 0x7fffa7228000, 2 objects, 8k of 10k used, 92 free, 0 reclaimed, 1k 
overhead, 131068k capacity
User heap index=10:
heap 0x7fff9f228000, 2 objects, 8k of 10k used, 92 free, 0 reclaimed, 1k 
overhead, 131068k capacity
User heap index=11:
heap 0x7fff9b228000, 2 objects, 16k of 18k used, 92 free, 0 reclaimed, 1k 
overhead, 65532k capacity
User heap index=12:
heap 0x7fff9b028000, 2 objects, 256k of 258k used, 92 free, 0 reclaimed, 1k 
overhead, 2044k capacity
User heap index=13:
heap 0x7fff9ae28000, 2 objects, 240k of 242k used, 92 free, 0 reclaimed, 1k 
overhead, 2044k capacity
User heap index=14:
heap 0x7fff9ad28000, 5 objects, 8k of 10k used, 168 free, 0 reclaimed, 1k 
overhead, 1020k capacity
User heap index=15:
heap 0x7fff9ac28000, 5 objects, 8k of 10k used, 168 free, 0 reclaimed, 1k 
overhead, 1020k capacity
User heap index=16:
heap 0x7fff9ab28000, 2 objects, 8k of 10k used, 92 free, 0 reclaimed, 1k 
overhead, 1020k capacity
User heap index=17:
heap 0x7fff9a128000, 2 objects, 1k of 3k used, 88 free, 0 reclaimed, 1k 
overhead, 10236k capacity
User heap index=18:
heap 0x7fff9a028000, 2 objects, 8k of 10k used, 92 free, 0 reclaimed, 1k 
overhead, 1020k capacity
User heap index=19:
heap 0x7fff99f28000, 2 objects, 8k of 10k used, 92 free, 0 reclaimed, 1k 
overhead, 1020k capacity
User heap index=20:
heap 0x7fff99e28000, 2 objects, 2k of 4k used, 92 free, 0 reclaimed, 1k 
overhead, 1020k capacity
  
User heap index=21: 

  
heap 0x7fff99d28000, 2 objects, 8k of 10k used, 92 free, 0 reclaimed, 1k 
overhead, 1020k capacity
User heap index=22:
heap 0x7fff99c28000, 2 objects, 8k of 10k used, 92 free, 0 reclaimed, 1k 
overhead, 1020k capacity
User heap index=23:
heap 0x7fff99b28000, 2 objects, 8k of 10k used, 92 free, 0 reclaimed, 1k 
overhead, 1020k capacity
User heap index=24:
heap 0x7fff99a28000

Re: [vpp-dev] Question about Jira

[Luke, Chris]

Replying to an individual who sent me a message on IRC, but was not online when 
I went to reply:

 

    Hi Sir, sorry to bother you. I have some confusion. Is it required to have 
JIRA task for

    each gerrit review? I am new to FD.io, I am not sure If I can post such 
question in

    community mail or not.

 

Short answer: no, we don't typically require that except for bugs, and we only 
really enforce that close to release time. All patches welcome, and we’ll be 
friendly about asking for a Jira ticket if necessary.

 

Cheers,

Chris.

 



smime.p7s
Description: S/MIME cryptographic signature
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] memory issues

[Luke, Chris]

You’re misreading top. “Virt” only means the virtual memory footprint of the 
process. This includes unused heap, shared libraries, anonymous mmap() regions 
etc. “RSS” is the resident-in-memory size. It’s actually using 5G.

 

“show memory” also only shows the heap usage, it does not include packet buffer 
memory.

 

Chris.

 

From:  on behalf of 薛欣颖 
Date: Tuesday, December 5, 2017 at 00:51
To: vpp-dev 
Subject: [vpp-dev] memory issues

 

 

Hi guys，

I am using vpp v18.01-rc0~241-g4c9f2a8.
I configured 200K static routing. When I 'show memory' in VPP, '150+k used'. 
But in my machine ,used almost 15g. After del the static routing ,almost using 
16g memory.
More info is shown below:


VPP# show memory 
Thread 0 vpp_main
heap 0x7fffb58e9000, 1076983 objects, 110755k of 151671k used, 15386k free, 
13352k reclaimed, 16829k overhead, 1048572k capacity
User heap index=0:
heap 0x7fffb58e9000, 1076984 objects, 110755k of 151671k used, 15386k free, 
13352k reclaimed, 16829k overhead, 1048572k capacity
User heap index=1:
heap 0x77ed4000, 2 objects, 128k of 130k used, 92 free, 0 reclaimed, 1k 
overhead, 1020k capacity
User heap index=2:
heap 0x7fffb1e28000, 2 objects, 512k of 514k used, 92 free, 0 reclaimed, 1k 
overhead, 8188k capacity
User heap index=3:
heap 0x7fffb1628000, 2 objects, 512k of 514k used, 92 free, 0 reclaimed, 1k 
overhead, 8188k capacity
User heap index=4:
heap 0x7fffaf628000, 2 objects, 512k of 514k used, 92 free, 0 reclaimed, 1k 
overhead, 32764k capacity
User heap index=5:
heap 0x7fffaf528000, 2 objects, 8k of 10k used, 92 free, 0 reclaimed, 1k 
overhead, 1020k capacity
User heap index=6:
heap 0x7fffaf428000, 2 objects, 8k of 10k used, 92 free, 0 reclaimed, 1k 
overhead, 1020k capacity
User heap index=7:
heap 0x7fffaf328000, 2 objects, 120k of 122k used, 92 free, 0 reclaimed, 1k 
overhead, 1020k capacity
User heap index=8:
heap 0x7fffaf228000, 2 objects, 120k of 122k used, 92 free, 0 reclaimed, 1k 
overhead, 1020k capacity
User heap index=9:
heap 0x7fffa7228000, 2 objects, 8k of 10k used, 92 free, 0 reclaimed, 1k 
overhead, 131068k capacity
User heap index=10:
heap 0x7fff9f228000, 2 objects, 8k of 10k used, 92 free, 0 reclaimed, 1k 
overhead, 131068k capacity
User heap index=11:
heap 0x7fff9b228000, 2 objects, 16k of 18k used, 92 free, 0 reclaimed, 1k 
overhead, 65532k capacity
User heap index=12:
heap 0x7fff9b028000, 2 objects, 256k of 258k used, 92 free, 0 reclaimed, 1k 
overhead, 2044k capacity
User heap index=13:
heap 0x7fff9ae28000, 2 objects, 240k of 242k used, 92 free, 0 reclaimed, 1k 
overhead, 2044k capacity
User heap index=14:
heap 0x7fff9ad28000, 5 objects, 8k of 10k used, 168 free, 0 reclaimed, 1k 
overhead, 1020k capacity
User heap index=15:
heap 0x7fff9ac28000, 5 objects, 8k of 10k used, 168 free, 0 reclaimed, 1k 
overhead, 1020k capacity
User heap index=16:
heap 0x7fff9ab28000, 2 objects, 8k of 10k used, 92 free, 0 reclaimed, 1k 
overhead, 1020k capacity
User heap index=17:
heap 0x7fff9a128000, 2 objects, 1k of 3k used, 88 free, 0 reclaimed, 1k 
overhead, 10236k capacity
User heap index=18:
heap 0x7fff9a028000, 2 objects, 8k of 10k used, 92 free, 0 reclaimed, 1k 
overhead, 1020k capacity
User heap index=19:
heap 0x7fff99f28000, 2 objects, 8k of 10k used, 92 free, 0 reclaimed, 1k 
overhead, 1020k capacity
User heap index=20:
heap 0x7fff99e28000, 2 objects, 2k of 4k used, 92 free, 0 reclaimed, 1k 
overhead, 1020k capacity
  
User heap index=21: 

  
heap 0x7fff99d28000, 2 objects, 8k of 10k used, 92 free, 0 reclaimed, 1k 
overhead, 1020k capacity
User heap index=22:
heap 0x7fff99c28000, 2 objects, 8k of 10k used, 92 free, 0 reclaimed, 1k 
overhead, 1020k capacity
User heap index=23:
heap 0x7fff99b28000, 2 objects, 8k of 10k used, 92 free, 0 reclaimed, 1k 
overhead, 1020k capacity
User heap index=24:
heap 0x7fff99a28000, 2 objects, 8k of 10k used, 92 free, 0 reclaimed, 1k 
overhead, 1020k capacity
User heap index=25:
heap 0x7fff99928000, 2 objects, 8k of 10k used, 92 free, 0 reclaimed, 1k 
overhead, 1020k capacity
User heap index=26:
heap 0x7fff97928000, 2 objects, 8k of 10k used, 92 free, 0 reclaimed, 1k 
overhead, 32764k capacity
User heap index=27:
heap 0x7fff95928000, 2 objects, 8k of 10k used, 92 free, 0 reclaimed, 1k 
overhead, 32764k capacity
User heap index=28:
heap 0x7fff94928000, 2 objects, 1k of 3k used, 92 free, 0 reclaimed, 1k 
overhead, 16380k capacity
User heap index=29:
heap 0x7fff92928000, 2 objects, 128k of 130k used, 92 free, 0 reclaimed, 1k 
overhead, 32764k capacity
User heap index=30:
heap 0x7fff90928000, 2 objects, 128k of 130k used, 92 free, 0 reclaimed, 1k 
overhead, 32764k capacity
User heap index=31:
heap 0x7fff8f928000, 2 objects, 8k of 

Re: [vpp-dev] VPP high level working flowchart

[Luke, Chris]

I may have missed other responses, but the single biggest issue with your flow 
diagram is that there is no Linux network stack interaction unless an agent 
explicitly configures a logical network interface, or other mechanism, that 
does.

 

VPP provides a completely independent packet data-plane which only interacts 
with Linux as a mechanism to run the code; networking with Linux is completely 
optional.

 

Chris.

 

From:  on behalf of Holoo Gulakh 

Date: Monday, December 4, 2017 at 01:28
To: "vpp-dev@lists.fd.io" 
Subject: [vpp-dev] VPP high level working flowchart

 

Hi,

According to my researches around VPP and its workflow, I have prepared a 
flowchart showing VPP's workflow.

 

This flowchart says that all ingress packet to interfaces handled by VPP are 
sent to VPP without Linux network stack intervention. afterward based on the 
packet type/destination one of the flows goes on.

 

Is this flowchart describing VPP's workflow correctly?? (it might be helpful if 
you add more details to it if it's correct OR otherwise correct it if it's 
wrong)

 

thanks in advace



smime.p7s
Description: S/MIME cryptographic signature
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] api functions using shared memory

[Luke, Chris]

Which "show run" info? The stats in the header are calculated and some of the 
base values needed for it are missing in the current API; I intend to fix 
precisely that with this work since they are ideal summary lines for 'vpptop'.

Chris.

From: Gabriel Ganne [mailto:gabriel.ga...@enea.com]
Sent: Thursday, November 30, 2017 9:02 AM
To: Luke, Chris <chris_l...@cable.comcast.com>; Ole Troan <otr...@employees.org>
Cc: vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] api functions using shared memory


Chris,

It seems your work in https://gerrit.fd.io/r/#/c/9483/ does all what Maciek and 
Dave discussed in VPP-55.

Thanks again !



--

Gabriel Ganne


From: Gabriel Ganne
Sent: Thursday, November 30, 2017 2:52:06 PM
To: Luke, Chris; Ole Troan
Cc: vpp-dev@lists.fd.io<mailto:vpp-dev@lists.fd.io>
Subject: Re: [vpp-dev] api functions using shared memory


Actually, during the CSIT weekly call yesterday there was mentioned a missing 
VPP api for "show run".

I think I even found a jira for it : https://jira.fd.io/browse/VPP-55



It seemed like no one was working on it, and so I had a look.

In the ticket, Dave Barach  suggested to add this to the get_node_graph api 
function which is why I went there.



If you could add the infos from "show run" into your dev, this would be great.

Otherwise I can work on it after you've finished. There's no rush.



Regards,



--

Gabriel Ganne

____
From: Luke, Chris <chris_l...@comcast.com<mailto:chris_l...@comcast.com>>
Sent: Thursday, November 30, 2017 2:39:02 PM
To: Gabriel Ganne; Ole Troan
Subject: RE: [vpp-dev] api functions using shared memory


What data for each node are you looking for? So I can make sure it ends up 
included. The existing get_node_graph is fairly limited in what it retrieves 
aside from the adjacencies and a handful of stats.



My approach right now, to keep it simple, is to use the _dump/_details 
mechanism to return a list of items that encode the thread index and node index 
with the other details in a pretty flat structure; this should then be easily 
consumed by any binding. For Python I'll also provide a way to reanimate the 
data into a fairly simple object model.



You can see the first pass of my work at 
https://gerrit.fd.io/r/#/c/9222/<https://url10.mailanyone.net/v1/?m=1eKP3X-0004K2-4e=57e1b682=xpknLc81XbQlb0xvMXmP6LdQAhC9C-WkmvMZX_MyITOJvHIiAsAxybY7ldR6DsgpJ5FCoNL3Jo2iG9YbBigZEerbiFmF2qB-jovMxvNhAjOt69WE34BtnoQEXB6493yuyST9yzhnu_Z63w0ImBcsUPpNN_mdDmLi0RcARoD6KR9aixyc9umJ7hxu3Q6Y-EsWzzp2V9LnUIzwkWhK1lR6fEK1F0gwkYO9hqjl_PyjipY>
 and the two patches leading up to it which exposed a mechanism to interpret 
the result_in_shmem from Python and dezerialize into an object model. Ole 
rightly objects to using shmem, though I think there is still merit in merging 
the basic shmem reader since, while the mechanism exists in the API, we should 
support it where we can. Otherwise we should remove it from the API altogether.



My current work on this I expect to have cleaned up and usable in a few days, 
though I'm travelling next week (Kubecon) which may interrupt things if I don't 
make enough progress this week.



Chris.



From: Gabriel Ganne [mailto:gabriel.ga...@enea.com]
Sent: Thursday, November 30, 2017 7:47 AM
To: Ole Troan <otr...@employees.org<mailto:otr...@employees.org>>; Luke, Chris 
<chris_l...@cable.comcast.com<mailto:chris_l...@cable.comcast.com>>
Subject: Re: [vpp-dev] api functions using shared memory



Great !

Thanks.



--

Gabriel Ganne





From: Ole Troan <otr...@employees.org<mailto:otr...@employees.org>>
Sent: Thursday, November 30, 2017 12:50
To: Gabriel Ganne
Cc: vpp-dev@lists.fd.io<mailto:vpp-dev@lists.fd.io>
Subject: Re: [vpp-dev] api functions using shared memory



Gabriel,

> I am looking at the get_node_graph() api function, for use in python.
> It returns  a u64 reply_in_shmem value which points to the shared memory and 
> must then be processed by vlib_node_unserialize() (as is done in vat) but I 
> only saw such a function in C.
> Is there any way to do this in python ? (other languages should have the same 
> issue).
>
> Also, I had a look at the the cli api function (which works the same way) and 
> saw that it had an cli_inband version which apparently was designed to 
> replace the cli api function because it was using shared memory 
> (https://gerrit.fd.io/r/#/c/2575/<https://url10.mailanyone.net/v1/?m=1eKP3X-0004K2-4e=57e1b682=9lLDLNFIPw66omxD7Xax5tRUJNBd1qBZ0kxnVJ1-awHNTm2422SYts4YSy-uiYv-sIkxnmVM_AUhU5ffVfWJwXzdtn-FQcePME2XF4G4td9Ry9_yZTXJOVLj-uUyvUQJOFHEKDnb-QuZgYoYAo5qN0hHRrE03NUG8B-FccnprFXO-5lHSBuhJXFJS2Burywj_iD1TCOzaF0ybCtKzKgSDgOjtP9XhQ51M3FpinXrAHg>)
> Should the get_node_graph api function also get an *_inband version ?

Yes. That's also a prerequis

Re: [vpp-dev] api functions using shared memory

[Luke, Chris]

I’m already working on making this easier to consume. Stay tuned. 

Chris.

From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On 
Behalf Of Gabriel Ganne
Sent: Thursday, November 30, 2017 4:44
To: vpp-dev@lists.fd.io
Subject: [vpp-dev] api functions using shared memory


Hi,



I am looking at the get_node_graph() api function, for use in python.

It returns  a u64 reply_in_shmem value which points to the shared memory and 
must then be processed by vlib_node_unserialize() (as is done in vat) but I 
only saw such a function in C.

Is there any way to do this in python ? (other languages should have the same 
issue).



Also, I had a look at the the cli api function (which works the same way) and 
saw that it had an cli_inband version which apparently was designed to replace 
the cli api function because it was using shared memory 
(https://gerrit.fd.io/r/#/c/2575/)

Should the get_node_graph api function also get an *_inband version ?



Best regards,



--

Gabriel Ganne
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] vpp-api python error during vpp installation

[Luke, Chris]

Need the error in question, which would have been much earlier in the output.

But as another commenter mentions, if you ‘dpkg -i’ packages with dependencies 
you don’t have, ‘apt install -f’ can usually resolve those for you.

Chris.

From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On 
Behalf Of Pradeep Patel (pradpate)
Sent: Wednesday, November 22, 2017 12:58
To: vpp-dev@lists.fd.io
Subject: [vpp-dev] vpp-api python error during vpp installation

Team,

I am seeing the same 
issue(https://lists.fd.io/pipermail/vpp-dev/2017-April/004608.html) as seen 
earlier while installing debian package. Do we know a workaround?

Processing triggers for libc-bin (2.23-0ubuntu3) ...
Errors were encountered while processing:
vpp-api-python

Please see, I am newbie so any pointers on rules on using the mailer will be 
helpful.

Thank you,
Pradeep

___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] Can't run tests (ImportError: No module named bier)

[Luke, Chris]

That caught me out last week, too, so yes please.

Chris.

> -Original Message-
> From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On
> Behalf Of Marco Varlese
> Sent: Wednesday, November 22, 2017 10:43
> To: Klement Sekera -X (ksekera - PANTHEON TECHNOLOGIES at Cisco)
> ; vpp-dev 
> Subject: Re: [vpp-dev] Can't run tests (ImportError: No module named bier)
> 
> On Wed, 2017-11-22 at 15:31 +, Klement Sekera -X (ksekera - PANTHEON
> TECHNOLOGIES at Cisco) wrote:
> > Hi,
> >
> > `make test-wipe` should help
> Interesting... I ran "make wipe" before.
> May I suggest to have test-wipe run as part of the more generic wipe ???
> I'll submit a patch...
> >
> > Regards,
> > Klement
> Cheers,
> Marco
> >
> > > -Original Message-
> > > From: vpp-dev-boun...@lists.fd.io
> > > [mailto:vpp-dev-boun...@lists.fd.io] On Behalf Of Marco Varlese
> > > Sent: Wednesday, November 22, 2017 4:30 PM
> > > To: vpp-dev 
> > > Subject: [vpp-dev] Can't run tests (ImportError: No module named
> > > bier)
> > >
> > > Hi,
> > >
> > > I just took latest master and cannot run tests anymore...
> > >
> > > Adding tests from directory tree /home/mvarlese/repo/vpp/test
> > > Traceback (most recent call last):
> > >   File "run_tests.py", line 146, in 
> > > discover_tests(d, cb)
> > >   File "/home/mvarlese/repo/vpp/test/discover_tests.py", line 27, in
> > > discover_tests
> > > module = importlib.import_module(name)
> > >   File "/usr/lib64/python2.7/importlib/__init__.py", line 37, in
> > > import_module
> > > __import__(name)
> > >   File "/home/mvarlese/repo/vpp/test/test_bier.py", line 17, in
> 
> > > from scapy.contrib.bier import *
> > > ImportError: No module named bier
> > > Killing possible remaining process IDs:  9912 9914 No symlinks to
> > > failed tests'
> > > temporary directories found in /tmp/vpp-failed- unittests/.
> > > make[1]: *** [Makefile:124: test] Error 1
> > > make[1]: Leaving directory '/home/mvarlese/repo/vpp/test'
> > > make: *** [Makefile:362: test] Error 2
> > >
> > > Am I missing something? :(
> > >
> > >
> > > Cheers,
> > > Marco
> > >
> > > ___
> > > vpp-dev mailing list
> > > vpp-dev@lists.fd.io
> > > https://lists.fd.io/mailman/listinfo/vpp-dev
> ___
> vpp-dev mailing list
> vpp-dev@lists.fd.io
> https://lists.fd.io/mailman/listinfo/vpp-dev

___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] There was a conflict between vpp-devel-17.10-release.x86_64.rpm and vpp-dpdk-devel-17.08-vpp2.x86_64.rpm

[Luke, Chris]

Looks like an issue in the RPM packaging. The .spec file for the -devel package 
includes the line:

  %{_includedir}/*

Which will include the dpdk dir if it exists at that build time. The dpdk devel 
package is usually built elsewhere so I am surprised the vpp build dir has 
this, but I guess something touches the directory on the vpp-devel build. You 
should open a bug report at https://jira.fd.io ; I've also cc'ed the person who 
has worked the most on the RPM packaging in case he can enlighten us.

Last thing, did you build the packages from source yourself, or use one of our 
pre-built packages from a repository?

Thanks,
Chris.


From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On 
Behalf Of wanghongbo
Sent: Tuesday, November 21, 2017 8:49
To: vpp-dev@lists.fd.io
Subject: [vpp-dev] There was a conflict between 
vpp-devel-17.10-release.x86_64.rpm and vpp-dpdk-devel-17.08-vpp2.x86_64.rpm


hi all:

 The vpp-devel-17.10-release.x86_64.rpm conflicted with 
vpp-dpdk-devel-17.08-vpp2.x86_64 when I installed the rpm package. Should I 
used the rpm -force parameter. Thank you very much!


[root@localhost rpm]# ls
Makefile  vpp-17.10.0
vpp-api-lua-17.10-release.x86_64.rpm vpp-lib-17.10-release.x86_64.rpm  
vpp.spec
RPMS  vpp-17.10-release.x86_64.rpm   
vpp-api-python-17.10-release.x86_64.rpm  vpp-plugins-17.10-release.x86_64.rpm
SOURCES   vpp-api-java-17.10-release.x86_64.rpm  
vpp-devel-17.10-release.x86_64.rpm   vpp.service
[root@localhost rpm]# rpm -ivh *.rpm
Preparing...  # [100%]
file /usr/include/dpdk from install of vpp-devel-17.10-release.x86_64 
conflicts with file from package vpp-dpdk-devel-17.08-vpp2.x86_64
[root@localhost rpm]# rpm -qa | grep vpp
vpp-dpdk-devel-17.08-vpp2.x86_64
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] hi vpp-dev, another question about hugepage

[Luke, Chris]

As I recall, VPP only looks for 2MB pages; 1GB would be huge and wasteful.

A quick search reminded me of this thread, which may be instructive for you: 
https://lists.fd.io/pipermail/vpp-dev/2017-September/006364.html

Chris.


From: wanghongbo [mailto:wanghon...@kingsoft.com]
Sent: Tuesday, November 21, 2017 7:41
To: Luke, Chris <chris_l...@cable.comcast.com>
Cc: vpp-dev@lists.fd.io
Subject: 答复: [vpp-dev] hi vpp-dev, another question about hugepage


Hi, chris:



Can you spare a few minutes to help me? I have config the 1GB hugepages . But 
vpp still used the 2M hugepage. I want to know configurations How VPP run with 
1GB huge pages.



[root@localhost ~]# cat /proc/cmdline

BOOT_IMAGE=/vmlinuz-3.10.0-693.el7.x86_64 root=/dev/mapper/centos-root ro 
crashkernel=auto rd.lvm.lv=centos/root rd.lvm.lv=centos/swap 
default_hugepagesz=1G hugepagesz=1G hugepages=64 iommu=pt intel_iommu=on 
isolcpus=0-11 rhgb quiet



/usr/bin/vpp[1815]: clib_sysfs_read: open 
`/sys/devices/system/node/node0/hugepages/hugepages-2048kB/free_hugepages': No 
such file or directory

/usr/bin/vpp[1815]: clib_sysfs_read: open 
`/sys/devices/system/node/node1/hugepages/hugepages-2048kB/free_hugepages': No 
such file or directory



Thanks

wanghongbo


发件人: Luke, Chris [mailto:chris_l...@comcast.com]
发送时间: 2017年11月21日 10:31
收件人: WANGHONGBO [王洪波]
主题: RE: [vpp-dev] hi vpp-dev, another question about hugepage

I understand too, I am just trying to make it easier for people to answer your 
questions and to make it useful for others in future who can search 

Chris.

From: wanghongbo [mailto:wanghon...@kingsoft.com]
Sent: Monday, November 20, 2017 21:14
To: Luke, Chris 
<chris_l...@cable.comcast.com<mailto:chris_l...@cable.comcast.com>>
Subject: 答复: [vpp-dev] hi vpp-dev, another question about hugepage

OK, understand. I just want to list more information for question. Thank you.

发件人: Luke, Chris [mailto:chris_l...@comcast.com]
发送时间: 2017年11月20日 22:14
收件人: WANGHONGBO [王洪波]; vpp-dev@lists.fd.io<mailto:vpp-dev@lists.fd.io>
主题: RE: [vpp-dev] hi vpp-dev, another question about hugepage

Hello,

Apologies for not answering your query, however is there any chance you could 
stop pasting images all the time?  Cut-and-paste will suffice. Including images 
will routinely trip the list-max-message-size limits.

Besides, text is searchable and images are not, thus limiting the usefulness to 
future generations.

Thanks,
Chris.


From: vpp-dev-boun...@lists.fd.io<mailto:vpp-dev-boun...@lists.fd.io> 
[mailto:vpp-dev-boun...@lists.fd.io] On Behalf Of wanghongbo
Sent: Monday, November 20, 2017 9:11 AM
To: vpp-dev@lists.fd.io<mailto:vpp-dev@lists.fd.io>
Subject: [vpp-dev] hi vpp-dev, another question about hugepage

Hi vpp-dev:

   I configure the 1G hugepage in /boot/grub2/grub.cfg and split cpu core. 
Then I configure the /etc/sysctl.d/80-vpp.conf.  After reboot the kernel was 
crash. How can I configure the vpp hugepage? Thank you very much.

___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] gerrit http authentication

[Luke, Chris]

Just FYI, I use ssh-agent to avoid storing my key on shared devices.

Chris.

From: Pierre Pfister (ppfister) [mailto:ppfis...@cisco.com]
Sent: Tuesday, November 21, 2017 3:31
To: vpp-dev@lists.fd.io
Cc: Andrew Yourtchenko <ayour...@gmail.com>; Luke, Chris 
<chris_l...@cable.comcast.com>; John Lo (loj) <l...@cisco.com>
Subject: Re: [vpp-dev] gerrit http authentication

Hello all,

Heads up on this one since it still does not work for me.

I was using https auth on servers that are shared between multiple people (any 
ssh private key left there could be accessed by other root users).
It seems safer to rely on copy/pasting a password for every push than 
multiplying private keys.

Cheers,

- Pierre




Le 19 oct. 2017 à 20:25, John Lo (loj) <l...@cisco.com<mailto:l...@cisco.com>> 
a écrit :

Yes, I can confirm using LF password does work while https password failed.  
-John

From: vpp-dev-boun...@lists.fd.io<mailto:vpp-dev-boun...@lists.fd.io> 
[mailto:vpp-dev-boun...@lists.fd.io] On Behalf Of Andrew Yourtchenko
Sent: Thursday, October 19, 2017 1:29 PM
To: Luke, Chris <chris_l...@comcast.com<mailto:chris_l...@comcast.com>>
Cc: vpp-dev@lists.fd.io<mailto:vpp-dev@lists.fd.io>
Subject: Re: [vpp-dev] gerrit http authentication

I got a reply from Vanessa on my ticket - apparently after upgrade the Linux 
foundation password should work... I will test tomorrow but sending mail here 
in case anyone else is interested to try before that.
--a

On 19 Oct 2017, at 16:14, Luke, Chris 
<chris_l...@comcast.com<mailto:chris_l...@comcast.com>> wrote:
…and certainly not on port != 22.

Chris.

From: Andrew Yourtchenko [mailto:ayour...@gmail.com]
Sent: Thursday, October 19, 2017 9:16
To: Gabriel Ganne <gabriel.ga...@enea.com<mailto:gabriel.ga...@enea.com>>
Cc: Luke, Chris 
<chris_l...@cable.comcast.com<mailto:chris_l...@cable.comcast.com>>; 
vpp-dev@lists.fd.io<mailto:vpp-dev@lists.fd.io>
Subject: Re: [vpp-dev] gerrit http authentication

I sent the mail to help desk, which opened the ticket 47239. Not sure if there 
is a way to “pile up” a “me too” it’s pretty much a showstopper for me, 
since same as Gabriel - not all of the environments allow SSH...
--a

On 19 Oct 2017, at 13:56, Gabriel Ganne 
<gabriel.ga...@enea.com<mailto:gabriel.ga...@enea.com>> wrote:
Yes, I do.
Pulling works fine, only the review action is an issue.

This is what shoud correspond to (previously) "HTTP Password" in the gerrit 
settings menu.
The gerrit link seems to be still active : 
https://gerrit.fd.io/r/#/settings/http-password
However, the functionnality itself is deactivated

--
Gabriel Ganne

From: Luke, Chris <chris_l...@comcast.com<mailto:chris_l...@comcast.com>>
Sent: Thursday, October 19, 2017 1:50:30 PM
To: Gabriel Ganne; vpp-dev@lists.fd.io<mailto:vpp-dev@lists.fd.io>
Subject: RE: gerrit http authentication

Just to be unambiguous for the archives, you mean HTTP authentication when 
pushing patches to Gerrit with Git, and not interactive browsing of the UI?

Chris.

From: vpp-dev-boun...@lists.fd.io<mailto:vpp-dev-boun...@lists.fd.io> 
[mailto:vpp-dev-boun...@lists.fd.io] On Behalf Of Gabriel Ganne
Sent: Thursday, October 19, 2017 4:13
To: vpp-dev@lists.fd.io<mailto:vpp-dev@lists.fd.io>
Subject: [vpp-dev] gerrit http authentication

Hi,

Unless I'm mistaken, it seems http authentication has been removed from gerrit.
It was useful to me, as I work in a company where any non-http traffic is 
blocked.

Do you think it's possible to restore it ?

Best regards,

--
Gabriel Ganne
___
vpp-dev mailing list
vpp-dev@lists.fd.io<mailto:vpp-dev@lists.fd.io>
https://lists.fd.io/mailman/listinfo/vpp-dev
___
vpp-dev mailing list
vpp-dev@lists.fd.io<mailto:vpp-dev@lists.fd.io>
https://lists.fd.io/mailman/listinfo/vpp-dev

___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] Import/includes in .api files

[Luke, Chris]

What Ole said.

This requires careful thought for impact to downstream API users.

Chris.

> -Original Message-
> From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On
> Behalf Of Ole Troan
> Sent: Monday, November 20, 2017 8:17 AM
> To: Dave Barach (dbarach) 
> Cc: vpp-dev@lists.fd.io
> Subject: Re: [vpp-dev] Import/includes in .api files
> 
> > Since the beginning of time, we've been running .api files through the C
> preprocessor. Put all of your "typeonly..." definitions in a file, and 
> #include it.
> Should work immediately.
> 
> But not for any of the other language bindings...
> 
> Ole
> 
> >
> > Thanks to Damjan, there's only one copy of the suffix rule, in 
> > .../src/suffix-
> rules.mk. Here's the relevant rule:
> >
> > %.api.h: %.api @VPPAPIGEN@
> > @echo "  APIGEN  " $@ ; \
> > mkdir -p `dirname $@` ; \
> > $(CC) $(CPPFLAGS) -E -P -C -x c $<  \
> > | @VPPAPIGEN@ --input - --output $@ --show-name $@ > /dev/null
> >
> > HTH… Dave
> >
> > -Original Message-
> > From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io]
> On Behalf Of Neale Ranns (nranns)
> > Sent: Monday, November 20, 2017 3:28 AM
> > To: vpp-dev@lists.fd.io
> > Subject: [vpp-dev] RFC: Import/includes in .api files
> >
> >
> > Hi All,
> >
> > I’d like to be able to re-use types defined in one .api file in many other 
> > .api
> files. My specific objective is to re-use a fib_path_t across the many APIs 
> that
> describe a destination to which to send packets.
> >
> > My first attempt at this is:
> >  https://gerrit.fd.io/r/#/c/9489/
> >
> > I updated vppapigen to accept the keyword ‘import’, munch the
> subsequent string, and then generate the #include in the resulting .api.h.
> then the fun started… multiple type definitions, include guards, here be
> dragons, turn back now and seek assistance.
> > I later realised that an import statement is not required. If I create
> vnet/fib/fib.api and add it to vnet_all_api_h.h at the top, then that has some
> success. However, no import statement is not so friendly to other tools that
> parse the .api files.
> >
> > So an RFC that is really an RFH; how is it best to approach this?
> >
> > Regards,
> > Neale
> >
> >
> > ___
> > vpp-dev mailing list
> > vpp-dev@lists.fd.io
> > https://lists.fd.io/mailman/listinfo/vpp-dev
> > ___
> > vpp-dev mailing list
> > vpp-dev@lists.fd.io
> > https://lists.fd.io/mailman/listinfo/vpp-dev

___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] Please Call DigSafe...

[Luke, Chris]

Hi Dave,

After spending a few minutes to work out that you were talking about a proposed 
patch and not something any of us had merged (and, especially not that I 
merged!), I see that what we need is a balance between not discouraging people 
to experiment, or submit their ideas, but to also steer people towards relevant 
leads before they get in too deep.

Problem is, if people make huge patches before ever talking to someone, our 
first contact is when they submit it. The teaching moment is when the reviewer 
notices it. That is obviously too late for the first patch, but should help 
with subsequent work.

This is why open source generally prefers people to keep their patches small 
and thematic; most reviewers tire of seeing many large patches when they are 
developed in isolation and are directionally unsound - to the point that they 
start to see the color bar in the review list and if it's yellow-or-worse, and 
not from someone they specifically associate with quality work, typically those 
submissions end up ignored.

I don't think we have contribution guidelines for VPP or fd.io in general 
(apart from the style and doc guides); at least a very quick scan of the wiki 
was not fruitful. We should have somewhere to send new people (can we nudge 
people who login to Gerrit for the first time?), and also people whose first 
submission is unacceptable (too big, too complex, directionally unsound). And 
we as reviewers should remain vigilant and, importantly, consistent.

Chris.


> -Original Message-
> From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On
> Behalf Of Dave Barach
> Sent: Friday, November 17, 2017 7:45
> To: vpp-dev@lists.fd.io
> Subject: [vpp-dev] Please Call DigSafe...
> 
> Folks,
> 
> At our next project meeting, I'd like to spend a few minutes talking about a
> good-news / bad-news situation affecting the vpp project.
> 
> As the community has expanded, committers have begun noticing
> unacceptable and unfixable patches in mission-critical code. Yesterday's
> soap-opera episode involved the ip4/6 speed-paths.
> 
> I think we should allocate a bit of meeting time for folks to talk about what
> they're trying to develop, with an eye towards engaging with relevant area
> experts from the start.
> 
> In most places in the US, folks planning to dig holes on their property are
> required to call 811 (DigSafe): to avoid hitting buried gas lines and blowing 
> up
> the neighborhood. It seems like we need to create something
> similar for the vpp project.
> 
> Thoughts?
> 
> Thanks... Dave
> 
> ___
> vpp-dev mailing list
> vpp-dev@lists.fd.io
> https://lists.fd.io/mailman/listinfo/vpp-dev

___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] [csit-dev] vpp continuous integration on armv8

[Luke, Chris]

Ed,

Based on Tina saying the ones delivered are OD1000’s, Overdrive machines seem 
to come from the factory with Suse on them according to their website.

Chris.

From: csit-dev-boun...@lists.fd.io [mailto:csit-dev-boun...@lists.fd.io] On 
Behalf Of Ed Warnicke
Sent: Thursday, November 16, 2017 18:32
To: Gabriel Ganne 
Cc: csit-...@lists.fd.io; Dave Barach (dbarach) ; Tina Tsou 
; vpp-dev ; Nicolas Bouthors 

Subject: Re: [csit-dev] [vpp-dev] vpp continuous integration on armv8

Gabriel,

We do need to have multiple workers to service the verify queue... having the 
queue back up behind a single server wouldn't be good.  Do you know if these 
boxes are installed with Ubuntu 16.04 already?

Ed

On Thu, Nov 16, 2017 at 9:03 AM Gabriel Ganne 
> wrote:

Yes, they are.

I estimate it should take about 40 minutes to build and test with 8 cores in 
release mode, therefore I do not think that using all 3 ThunderX is necessary.

I do not have access to a ThunderX platform on my side (I ran my tests on NXP 
and Hierofalcon platforms), if needed please see with Tina Tsou (in CC) for the 
specifics of ThunderX.



I was thinking about duplicating the *vpp-verify-master-ubuntu1604* target as a 
first step.

Ubuntu 16.04 is a LTS for armv8 and is one of the distributions already used 
for vpp x86 continuous testing.



If all goes well, I was thinking about using fedora-26 (or above) as rhel-based 
distribution, since it also has aarch64 official support.

But since it's not one of the distros already used in ci, let's keep it for 
later.



Regards,



--

Gabriel Ganne


From: Ed Warnicke >
Sent: Thursday, November 16, 2017 4:47:14 PM
To: Gabriel Ganne
Cc: vpp-dev; Dave Barach (dbarach); Nicolas Bouthors; 
csit-...@lists.fd.io; Vanessa Valderrama
Subject: Re: [vpp-dev] vpp continuous integration on armv8

Gabriel,

This is awesome news!

Do I understand correctly that these ThunderX boards are intended to be used 
for build/make test/packaging?  If so, I've cced in Vanessa, our fearless 
sysadmin to help in figuring these things out :)

Do you have opinions about which Linux distributions you want to package for 
(Ubuntu?, Centos?) and versions?

Ed

On Thu, Nov 16, 2017 at 5:27 AM Gabriel Ganne 
> wrote:

Hi,



We've been working on preparing vpp for armv8 continuous testing (See 
https://wiki.fd.io/view/VPP/AArch64),

and we think that we now have everything which is required to add arm as ci 
platform in the vpp review process (build, test and packaging). All the test 
have been done on "native".

Also 3 thunderX platforms sent by ARM should have arrived yesterday in the fdio 
lab.


I *think* that all that is required should be to set the platforms with VMs on 
it, and add them as build slaves.



How should we proceed from here ?



--
Gabriel Ganne


___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] Odd behavior running ping via vppctl

[Luke, Chris]

Addendum: https://jira.fd.io/browse/VPP-1038 has the history.

Chris.

From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On 
Behalf Of Luke, Chris
Sent: Wednesday, November 15, 2017 14:30
To: Ed Warnicke <hagb...@gmail.com>; vpp-dev <vpp-dev@lists.fd.io>
Subject: Re: [vpp-dev] Odd behavior running ping via vppctl

Update to master or latest commits on stable/17.10. The fix just missed the 
release.

Chris.

From: vpp-dev-boun...@lists.fd.io<mailto:vpp-dev-boun...@lists.fd.io> 
[mailto:vpp-dev-boun...@lists.fd.io] On Behalf Of Ed Warnicke
Sent: Wednesday, November 15, 2017 13:14
To: vpp-dev <vpp-dev@lists.fd.io<mailto:vpp-dev@lists.fd.io>>
Subject: [vpp-dev] Odd behavior running ping via vppctl

When I attempt to run ping via vppctl I get:

sudo vppctl -s /run/vpp/cli-vpp1.sock ping 10.10.1.1
64 bytes from 10.10.1.1<http://10.10.1.1>: icmp_seq=1 ttl=64 time=.0715 ms
Aborted due to a keypress.

Statistics: 1 sent, 1 received, 0% packet loss

Note: I'm not pressing any keys.  How would we go about fixing this?

Ed
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] Odd behavior running ping via vppctl

[Luke, Chris]

Update to master or latest commits on stable/17.10. The fix just missed the 
release.

Chris.

From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On 
Behalf Of Ed Warnicke
Sent: Wednesday, November 15, 2017 13:14
To: vpp-dev 
Subject: [vpp-dev] Odd behavior running ping via vppctl

When I attempt to run ping via vppctl I get:

sudo vppctl -s /run/vpp/cli-vpp1.sock ping 10.10.1.1
64 bytes from 10.10.1.1: icmp_seq=1 ttl=64 time=.0715 ms
Aborted due to a keypress.

Statistics: 1 sent, 1 received, 0% packet loss

Note: I'm not pressing any keys.  How would we go about fixing this?

Ed
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] hi vpp-dev, need you help!

[Luke, Chris]

You can safely ignore those messages. They're just odd artifacts of how the 
build system is assembled.

Chris.

From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On 
Behalf Of wanghongbo
Sent: Wednesday, November 15, 2017 5:50
To: vpp-dev@lists.fd.io
Subject: [vpp-dev] hi vpp-dev, need you help!

Hi guys:

  Need you help! I have built vpp success in vmware environment. But i got 
three problem about "libtool" when I built vpp on x86 server. My environment 
was real server + centos7.4 and the vpp's version was v17.10. The capture as 
follows. Thank you very much!


[cid:image002.png@01D35DF8.EEB8D700]

[cid:image003.png@01D35DF8.EEB8D700]

[cid:image004.png@01D35DF8.EEB8D700]



___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] hi vpp-dev, need you help!

[Luke, Chris]

Likely you ran out of memory. A patch was merged last night that should help 
alleviate this by reducing the number of parallel builds.

The new C++ stuff is a hog and is triggering this for several people. If you 
don't intend to use it, then perhaps looking for this section in 
builds-data/platforms/vpp.mk will help too:

+# To disable the VPP object model build - and save about half the build time -
+# uncomment the following...
+# vpp_configure_args_vpp += --disable-vom

Chris.

From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On 
Behalf Of wanghongbo
Sent: Tuesday, November 14, 2017 7:33 AM
To: vpp-dev@lists.fd.io
Subject: [vpp-dev] hi vpp-dev, need you help!

Hi vpp-dev:

  Excuse me. Could you give me a hand?  I have a problem when I build vpp. 
My environment is vmware workstation + centos7.4 . The capture as follows. Was 
this error caused by "make build-release".



[??: cid:image001.png@01D35D70.582DE740]

 I used this command "./build-root/vagrant/build.sh". The building 
didn't have error. Is it right?

[??: cid:image002.png@01D35D73.62DCDC20]


 Thank you very much!
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] vlib_validate_buffer_enqueue

[Luke, Chris]

The x4 variant was introduced chronologically after the sample plugin and 
nobody went back to update it. However, generally speaking the four-wide-stride 
is only beneficial in some cases, the reasoning for which is a bit arcane based 
on the likelihood of being able to keep the CPU cache primed and similar. The 
best I can tell is that there's a bit of judgement based on the empirical 
experience of a handful of the wizened. By extension the gains from a x8 
version is likely marginal.

Chris

> -Original Message-
> From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On
> Behalf Of Justin Iurman
> Sent: Monday, November 13, 2017 5:51 AM
> To: vpp-dev 
> Subject: [vpp-dev] vlib_validate_buffer_enqueue
> 
> Hey guys,
> 
> In buffer_node.h, there are the following macros:
> - vlib_validate_buffer_enqueue_x1
> - vlib_validate_buffer_enqueue_x2
> - vlib_validate_buffer_enqueue_x4
> 
> In a node, I was just wondering what was the use idea behind that ? Is it for 
> a
> reason of speed ? I mean, you're obviously faster if you process 4 packets
> horizontally than one after the other. Why then, in the sample plugin, is the
> "x4" version not used ? A "perfect" plugin would use each of them to cover
> each case, right ? Also, why not having a "x8" (or more) version ? I guess 
> it's
> either for a performance issue or to stop at a specific ceiling.
> 
> Thanks !
> 
> Justin
> ___
> vpp-dev mailing list
> vpp-dev@lists.fd.io
> https://lists.fd.io/mailman/listinfo/vpp-dev

___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] VPP 17.07 file not found and option not found for vppctl

[Luke, Chris]

There’s no reason that I know of that would cause this to change for master.

Try looking in your system log, or run them in separate windows with the 
“interactive” keyword to get diagnostic output to the console to see why it is 
unhappy.

Chris.

From: sample project [mailto:intentnlpproj...@gmail.com]
Sent: Monday, November 13, 2017 1:08 AM
To: Luke, Chris <chris_l...@cable.comcast.com>; vpp-dev@lists.fd.io
Subject: Fwd: [vpp-dev] VPP 17.07 file not found and option not found for vppctl


Hi Chris,
Thanks for reply.

vagrant@localhost:~$ file `which vppctl`
/usr/bin/vppctl: a /usr/bin/python script, ASCII text executable

I was using 17.07 to run multi instance. In this version I can see two vpp 
instance got created.

vagrant@localhost:/vpp/build-root$ ps aux | grep vpp
root 22341  0.0  0.5 3511140 40976 ?   Ssl  02:53   0:01 vpp unix 
{cli-listen /run/vpp/cli-vpp1.sock} api-segment { prefix vpp1 }
root 22348  0.0  0.5 3511140 44584 ?   Ssl  02:54   0:01 vpp unix 
{cli-listen /run/vpp/cli-vpp2.sock} api-segment { prefix vpp2 }
vagrant@localhost:/vpp/build-root$

but If I use master/latest one it is always showing only one instance. I am not 
sure if the procedure to create multi instance has been changed or not or I am 
doing something wrong.
I am using following command to create vpp instance.

sudo vpp unix {cli-listen /run/vpp/cli-vpp1.sock} api-segment { prefix vpp1 }

Thanks,
nic


On Sun, Nov 12, 2017 at 7:05 PM, Luke, Chris 
<chris_l...@comcast.com<mailto:chris_l...@comcast.com>> wrote:
Check that you’re calling the binary vppctl program, not the script of the same 
name. The latter does not have the -s option and there was a period where both 
variants were still in the build tree.

For example, you want ‘file’ to say something like this:

$ file `which vppctl`
/[…]/vppctl: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically 
linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 2.6.32, 
BuildID[sha1]=d4817270c0f39a0e6fa466241d46ad8de29442f4, not stripped

Is there a reason you’re using 17.07? It feels like ancient history to me. :)

Chris.

From: vpp-dev-boun...@lists.fd.io<mailto:vpp-dev-boun...@lists.fd.io> 
[mailto:vpp-dev-boun...@lists.fd.io<mailto:vpp-dev-boun...@lists.fd.io>] On 
Behalf Of sample project
Sent: Sunday, November 12, 2017 6:03
To: vpp-dev@lists.fd.io<mailto:vpp-dev@lists.fd.io>
Subject: [vpp-dev] VPP 17.07 file not found and option not found for vppctl

Hi,
I am new to fd.io<http://fd.io>. I am trying to run multi instance vpp using 
https://wiki.fd.io/view/VPP/Progressive_VPP_Tutorial.

I am using 17.07. Its showing some error I am not able to figure it out where I 
am doing wrong. If someone know how or solved this issue, kindly let me know, 
it'll be very helpful. Thanks in advance.

vagrant@localhost:/vpp$ git describe
v17.07

First problem:
vagrant@localhost:/vpp$ sudo vppctl  -s /run/vpp/cli-vpp1.sock show ver
Usage: vppctl [options]
vppctl: error: no such option: -s


2nd problem:
vagrant@localhost:/vpp$
looking at src/script/vppctl I did this. use option "-p" instead of "-s"
vagrant@localhost:/vpp$ sudo vppctl  -p /run/vpp/cli-vpp1.sock show ver
FileNotFoundError error(2): No such file or directory as:
/dev/shm//run/vpp/cli-vpp1.sock-vpe-api
vagrant@localhost:/vpp$

Thanks,
nic




___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] problem with vppctl restart

[Luke, Chris]

Please file a bug in Jira with the component “CLI”. This is an interaction 
issue between VPP and vppctl; it seems to restart fine for me but, as you say, 
vppctl hangs.

We need to have VPP actively kill open CLI sessions upon restart.

Chris.

From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On 
Behalf Of chore
Sent: Monday, November 13, 2017 3:35
To: vpp-dev 
Subject: [vpp-dev] problem with vppctl restart

Dear Team,
A problem observed when i was trying to run "vppctl restart" command in 17.10 
version of vpp. I had tested this command in 17.07v and it had returned Misc 
error. however in 17.10v after entering this command vppctl never returns any 
prompt.
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] VPP 17.07 file not found and option not found for vppctl

[Luke, Chris]

Check that you’re calling the binary vppctl program, not the script of the same 
name. The latter does not have the -s option and there was a period where both 
variants were still in the build tree.

For example, you want ‘file’ to say something like this:

$ file `which vppctl`
/[…]/vppctl: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically 
linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 2.6.32, 
BuildID[sha1]=d4817270c0f39a0e6fa466241d46ad8de29442f4, not stripped

Is there a reason you’re using 17.07? It feels like ancient history to me. :)

Chris.

From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On 
Behalf Of sample project
Sent: Sunday, November 12, 2017 6:03
To: vpp-dev@lists.fd.io
Subject: [vpp-dev] VPP 17.07 file not found and option not found for vppctl

Hi,
I am new to fd.io. I am trying to run multi instance vpp using 
https://wiki.fd.io/view/VPP/Progressive_VPP_Tutorial.

I am using 17.07. Its showing some error I am not able to figure it out where I 
am doing wrong. If someone know how or solved this issue, kindly let me know, 
it'll be very helpful. Thanks in advance.

vagrant@localhost:/vpp$ git describe
v17.07

First problem:
vagrant@localhost:/vpp$ sudo vppctl  -s /run/vpp/cli-vpp1.sock show ver
Usage: vppctl [options]
vppctl: error: no such option: -s


2nd problem:
vagrant@localhost:/vpp$
looking at src/script/vppctl I did this. use option "-p" instead of "-s"
vagrant@localhost:/vpp$ sudo vppctl  -p /run/vpp/cli-vpp1.sock show ver
FileNotFoundError error(2): No such file or directory as:
/dev/shm//run/vpp/cli-vpp1.sock-vpe-api
vagrant@localhost:/vpp$

Thanks,
nic


___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] ACL Build/Test Issues

[Luke, Chris]

Since the tests reside in the same repo and they’re run from the checkout copy 
of the patch, you should be able to simply update the tests in the same patch 
that changes the result codes, without need for backward compatibility.

If you’re wondering where the tests are:

$ ls test/*acl*
test/test_acl_plugin_conns.py  test/test_acl_plugin_macip.py
test/test_acl_plugin_l2l3.py   test/test_acl_plugin.py

Chris.

From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On 
Behalf Of Jon Loeliger
Sent: Friday, November 10, 2017 19:17
To: Andrew Yourtchenko 
Cc: vpp-dev 
Subject: Re: [vpp-dev] ACL Build/Test Issues

On Fri, Nov 10, 2017 at 5:54 PM, Andrew Yourtchenko 
> wrote:
Hi Jon,

On 10 Nov 2017, at 23:11, Jon Loeliger 
> wrote:
Folks,

Every error from the ACL implementation is -1.  Generically bad.
Without regard for what might be more useful to an upper-layer UI.

When we discussed with the openstack folks the way they are treating errors was 
all as catastrophic, but yes more distinction would be better, so thanks a lot 
for taking care of it!

Happy to try to help. :-)

So I submitted a patch to help this situation some.
https://gerrit.fd.io/r/#/c/9383/

I have built and tested it locally, but it fails the Verify Tests because
it has a test that is expecting a hard-coded -1 return from some tests.
Returning a -6 wasn't good enough.

First, this is draconian for no really good reason.  Second, it should be
fixed.  Third, I would do that except I am stupid and need a clue where
or how to fix this situation so the tests are less draconian.  (Can we
get a "less than 0" test instead of "equal to -1"?)

Yeah. So we would need to first submit new test(s) that pass on both current 
and new code and then the new code itself... wanna take a shot at it  or should 
I ?

I don't even know where I would begin on that front, except
to say the test should maybe be " actual < 0" for now.
Oh, and, it's pretty clear why the Verify failed, despite the Jenkins job
saying it was unable to determine a cause.  Um, double blerg.

Alas, this one I leave to someone else to comment on :)

I hear that!

jdl

___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] FW: Coverity build failed with 18 errors

[Luke, Chris]

Thanks Neale; merged. Hopefully normal service will be resumed on this 
afternoons run! :)

Chris.

> -Original Message-
> From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On
> Behalf Of Neale Ranns (nranns)
> Sent: Friday, November 10, 2017 7:33
> To: Chris Luke ; vpp-dev@lists.fd.io
> Subject: Re: [vpp-dev] FW: Coverity build failed with 18 errors
> 
> Hi Chris,
> 
> And this one for VOM:
>   https://gerrit.fd.io/r/#/c/9374/
> 
> /neale
> 
> -Original Message-
> From:  on behalf of "Neale Ranns (nranns)"
> 
> Date: Friday, 10 November 2017 at 11:59
> To: Chris Luke , "vpp-dev@lists.fd.io"  d...@lists.fd.io>
> Subject: Re: [vpp-dev] FW: Coverity build failed with 18 errors
> 
> 
> Hi Chris,
> 
> I just pushed:
>   https://gerrit.fd.io/r/#/c/9370/
> to fix the use of integer types in BIER.
> 
> I’ll look at the VOM ones too.
> 
> /neale
> 
> 
> -Original Message-
> From:  on behalf of Chris Luke
> 
> Date: Thursday, 9 November 2017 at 22:05
> To: "vpp-dev@lists.fd.io" 
> Subject: [vpp-dev] FW: Coverity build failed with 18 errors
> 
> FYI, Coverity has just failed to build because of issues in BIER (and 
> maybe
> VOM); some of these may have existed a while, because these all seem
> to be
> warnings and Coverity fails a build based on number of rejected build
> units
> exceeding a % threshold. Likely BIER was merged and triggered the
> threshold.
> 
> I note that BIER is using C99 stdint types; Coverity appears to be 
> fussy
> about how these get defined (missing include?); also we agreed here on
> this
> list just a few weeks ago that VPP uses its own typedefs for 
> specified-
> width
> integers (u64 etc) so we should not be using such C99 types anyway.
> 
> For those interested, the Coverity build log is available at
> https://vpp.flirble.org/coverity/20171109/build-log.txt though please
> don't
> ask me to interpret it!
> 
> Chris.
> 
> -Original Message-
> From: VPP [mailto:v...@brae.flirble.org]
> Sent: Thursday, November 9, 2017 15:29
> To: chr...@flirble.org
> Subject: Coverity build failed with 18 errors
> 
> Coverity build failed with 18 errors.
> 
> Latest commit: v18.01-rc0-251-g75e974b
> 
> Error counts from cov-int/build-log.txt:
> 84205:[ERROR] [104291] EXECUTING: /bin/sed s|:*$||
> 84459:[ERROR] 1 error detected in the compilation of
> "../../../src/vnet/fib/fib_path.c".
> 91374:[ERROR] 1 error detected in the compilation of
> "../../../src/vnet/bier/bier_fmask.c".
> 91462:[ERROR] 1 error detected in the compilation of
> "../../../src/vnet/bier/bier_fmask_db.c".
> 91532:[ERROR] 1 error detected in the compilation of
> "../../../src/vnet/bier/bier_entry.c".
> 91700:[ERROR] 1 error detected in the compilation of
> "../../../src/vnet/bier/bier_output.c".
> 91775:[ERROR] 1 error detected in the compilation of
> "../../../src/vnet/bier/bier_table.c".
> 91828:[ERROR] 1 error detected in the compilation of
> "../../../src/vnet/bier/bier_lookup.c".
> 91840:[ERROR] 1 error detected in the compilation of
> "../../../src/vnet/bier/bier_fmask.c".
> 91847:[ERROR] 1 error detected in the compilation of
> "../../../src/vnet/bier/bier_fmask_db.c".
> 91954:[ERROR] 5 errors detected in the compilation of
> "../../../src/vnet/bier/bier_types.c".
> 91982:[ERROR] 1 error detected in the compilation of
> "../../../src/vnet/bier/bier_entry.c".
> 92104:[ERROR] 1 error detected in the compilation of
> "../../../src/vnet/bier/bier_output.c".
> 92160:[ERROR] 1 error detected in the compilation of
> "../../../src/vnet/bier/bier_table.c".
> 92396:[ERROR] 1 error detected in the compilation of
> "../../../src/vnet/bier/bier_lookup.c".
> 92796:[ERROR] 5 errors detected in the compilation of
> "../../../src/vnet/bier/bier_types.c".
> 93191:[ERROR] 1 error detected in the compilation of
> "../../../src/vnet/bier/bier_test.c".
> 93644:[ERROR] 1 error detected in the compilation of
> "../../../src/vnet/bier/bier_test.c".
> 
> Probable error information from the compiler:
> 84180:"/home/vpp/dev/fdio/coverity/vpp/build-
> data/../src/vnet/bier/bier_fmas
> k.h",
> 84181-  line 57: error #20: identifier "uint32_t" is undefined
> 84182-  uint32_t bfmb_count;
> 84183-  ^
> --
> 84428:"/home/vpp/dev/fdio/coverity/vpp/build-
> data/../src/vnet/bier/bier_fmas
> 

[vpp-dev] FW: Coverity build failed with 18 errors

[Luke, Chris]

Doh. Repost. I sent the original from the wrong account. 

(mods, pls ignore the one held for moderation!)

-Original Message-
From: Chris Luke [mailto:chr...@flirble.org] 
Sent: Thursday, November 9, 2017 16:06
To: 'vpp-dev@lists.fd.io' 
Subject: FW: Coverity build failed with 18 errors

FYI, Coverity has just failed to build because of issues in BIER (and maybe 
VOM); some of these may have existed a while, because these all seem to be 
warnings and Coverity fails a build based on number of rejected build units 
exceeding a % threshold. Likely BIER was merged and triggered the threshold.

I note that BIER is using C99 stdint types; Coverity appears to be fussy about 
how these get defined (missing include?); also we agreed here on this list just 
a few weeks ago that VPP uses its own typedefs for specified-width integers 
(u64 etc) so we should not be using such C99 types anyway.

For those interested, the Coverity build log is available at 
https://vpp.flirble.org/coverity/20171109/build-log.txt though please don't ask 
me to interpret it!

Chris.

-Original Message-
From: VPP [mailto:v...@brae.flirble.org] 
Sent: Thursday, November 9, 2017 15:29
To: mailto:chr...@flirble.org
Subject: Coverity build failed with 18 errors

Coverity build failed with 18 errors.

Latest commit: v18.01-rc0-251-g75e974b

Error counts from cov-int/build-log.txt:
84205:[ERROR] [104291] EXECUTING: /bin/sed s|:*$||
84459:[ERROR] 1 error detected in the compilation of 
"../../../src/vnet/fib/fib_path.c".
91374:[ERROR] 1 error detected in the compilation of 
"../../../src/vnet/bier/bier_fmask.c".
91462:[ERROR] 1 error detected in the compilation of 
"../../../src/vnet/bier/bier_fmask_db.c".
91532:[ERROR] 1 error detected in the compilation of 
"../../../src/vnet/bier/bier_entry.c".
91700:[ERROR] 1 error detected in the compilation of 
"../../../src/vnet/bier/bier_output.c".
91775:[ERROR] 1 error detected in the compilation of 
"../../../src/vnet/bier/bier_table.c".
91828:[ERROR] 1 error detected in the compilation of 
"../../../src/vnet/bier/bier_lookup.c".
91840:[ERROR] 1 error detected in the compilation of 
"../../../src/vnet/bier/bier_fmask.c".
91847:[ERROR] 1 error detected in the compilation of 
"../../../src/vnet/bier/bier_fmask_db.c".
91954:[ERROR] 5 errors detected in the compilation of 
"../../../src/vnet/bier/bier_types.c".
91982:[ERROR] 1 error detected in the compilation of 
"../../../src/vnet/bier/bier_entry.c".
92104:[ERROR] 1 error detected in the compilation of 
"../../../src/vnet/bier/bier_output.c".
92160:[ERROR] 1 error detected in the compilation of 
"../../../src/vnet/bier/bier_table.c".
92396:[ERROR] 1 error detected in the compilation of 
"../../../src/vnet/bier/bier_lookup.c".
92796:[ERROR] 5 errors detected in the compilation of 
"../../../src/vnet/bier/bier_types.c".
93191:[ERROR] 1 error detected in the compilation of 
"../../../src/vnet/bier/bier_test.c".
93644:[ERROR] 1 error detected in the compilation of 
"../../../src/vnet/bier/bier_test.c".

Probable error information from the compiler:
84180:"/home/vpp/dev/fdio/coverity/vpp/build-data/../src/vnet/bier/bier_fmask.h",
84181-  line 57: error #20: identifier "uint32_t" is undefined
84182-  uint32_t bfmb_count;
84183-  ^
--
84428:"/home/vpp/dev/fdio/coverity/vpp/build-data/../src/vnet/bier/bier_fmask.h",
84429-  line 57: error #20: identifier "uint32_t" is undefined
84430-  uint32_t bfmb_count;
84431-  ^
--
87392:"/home/vpp/dev/fdio/coverity/vpp/build-data/../src/vnet/bier/bier_bit_string
87393-  .h", line 56: warning #20: identifier "uint16_t" is undefined
87394-  uint16_t index;
87395-  ^
--
87397:"/home/vpp/dev/fdio/coverity/vpp/build-data/../src/vnet/bier/bier_bit_string
87398-  .h", line 72: warning #20: identifier "uint16_t" is undefined
87399-  uint16_t index;
87400-  ^
--
87402:"/home/vpp/dev/fdio/coverity/vpp/build-data/../src/vnet/bier/bier_bit_string
87403-  .h", line 87: warning #20: identifier "uint16_t" is undefined
87404-  uint16_t index;
87405-  ^
--
87423:"/home/vpp/dev/fdio/coverity/vpp/build-data/../src/vnet/bier/bier_bit_string
87424-  .h", line 54: warning #1563: function "bier_bit_string_is_zero" 
not
87425-  emitted, consider modeling it or review parse diagnostics to 
improve
87426-  fidelity
--
87430:"/home/vpp/dev/fdio/coverity/vpp/build-data/../src/vnet/bier/bier_bit_string
87431-  .h", line 69: warning #1563: function 
"bier_bit_string_clear_string"
87432-  not emitted, consider modeling it or review parse diagnostics to
87433-  improve fidelity
--
87437:"/home/vpp/dev/fdio/coverity/vpp/build-data/../src/vnet/bier/bier_bit_string
87438-  .h", line 84: warning #1563: function
87439-  "bier_bit_string_logical_and_string" not emitted, consider 
modeling
87440-  it or review parse diagnostics to improve fidelity
--

[vpp-dev] Merge jobs faiing

[Luke, Chris]

The post-merge jobs are failing with errors like this:


16:04:05 [ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy-file (default-cli) on 
project standalone-pom: Failed to deploy artifacts: Could not transfer artifact 
io.fd.vpp:vpp-dpdk-dev:deb:deb:17.08-vpp2_amd64 from/to 
fd.io.master.ubuntu.xenial.main 
(https://nexus.fd.io/content/repositories/fd.io.master.ubuntu.xenial.main): 
Failed to transfer file: 
https://nexus.fd.io/content/repositories/fd.io.master.ubuntu.xenial.main/io/fd/vpp/vpp-dpdk-dev/17.08-vpp2_amd64/vpp-dpdk-dev-17.08-vpp2_amd64-deb.deb.
 Return code is: 400, ReasonPhrase: Bad Request. -> [Help 1]

(from https://jenkins.fd.io/job/vpp-merge-master-ubuntu1604/3148/consoleFull)

This is sufficiently voodoo for me to not know how to proceed. (The Nexus stuff 
consistently annoys and baffles me, not least the overly-verbose chatter in 
build logs)

Could someone take a look, please?

Net result: No packages are being stored from master, and docs are not getting 
generated. It has been doing for thia a few days as best I can tell.

Thanks,
Chris.
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] Ask a question, thanks!

[Luke, Chris]

One looks up the FIB attached to the interface the packet arrives on. The other 
checks whether a previous node indicated which FIB this packet should be 
forwarded via. Many nodes have documented how they use sw_if_index[], see 
https://docs.fd.io/vpp/18.01/dc/da9/ip4__forward_8c.html#a981572b77836b7b06de0d93847867180

Chris.

From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On 
Behalf Of yao.chen...@zte.com.cn
Sent: Saturday, November 4, 2017 1:45
To: vpp-dev@lists.fd.io
Cc: lou.fangli...@zte.com.cn; wan.jun...@zte.com.cn
Subject: [vpp-dev] Ask a question, thanks!


 Hi,

in below  fun ip4_lookup_inline,i have a question,  please see also the 
following red part.

always_inline uword

ip4_lookup_inline (vlib_main_t * vm,

 vlib_node_runtime_t * node,

 vlib_frame_t * frame,

 int lookup_for_responses_to_locally_received_packets)



fib_index0 =

  vec_elt (im->fib_index_by_sw_if_index,

   vnet_buffer (p0)->sw_if_index[VLIB_RX]);

//above code ,get fib table index from vnet_buffer 
(p0)->sw_if_index[VLIB_RX] by vec_elt



fib_index0 =

  (vnet_buffer (p0)->sw_if_index[VLIB_TX] ==

   (u32) ~ 0) ? fib_index0 : vnet_buffer (p0)->sw_if_index[VLIB_TX];

  // here my question:if vnet_buffer (p0)->sw_if_index[VLIB_TX] is 
valid(not -1) , direct use vnet_buffer (p0)->sw_if_index[VLIB_TX] as fib table  
 index  .why direct use  vnet_buffer 
(p0)->sw_if_index[VLIB_TX]  instead of use vec_elt to get ?


regards,

chenghu yao
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

[vpp-dev] VPP node graph visualization

[Luke, Chris]

All,

I finally got around[1] to bashing together something to dump the graph as a 
.dot. It's a Python script that uses the papi module. It's not ready to merge 
yet IMO but I've made the patch public[2] in case anyone else wants to play 
with it while I work on it. The commit message has my current TODO list for the 
patch, and an example invocation to produce an SVG of the graph using Graphiz.

Enjoy,
Chris.

[1] To be precise, I did this already over a year ago 
https://lists.fd.io/pipermail/vpp-dev/2016-May/001201.html  but that was a CLI 
command inside VPP. I wanted to build something that used the API instead since 
I feel we can do more sophisticated things there.
[2] https://gerrit.fd.io/r/#/c/9222/
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] How to get VPP core dump and run exec file in interactive mode

[Luke, Chris]

/etc/vpp/startup.conf only loads if you tell it to. See 
https://wiki.fd.io/view/VPP/Command-line_Arguments#Configuration_file . I’m 
pretty sure the exec will occur whether interactive or not.

You may have the generation of coredumps disabled. In any case, “make debug” 
will run VPP under gdb and is by far the easiest way to look at stack traces.

Chris.

From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On 
Behalf Of John Wei
Sent: Thursday, November 2, 2017 18:13
To: vpp-dev 
Subject: [vpp-dev] How to get VPP core dump and run exec file in interactive 
mode

I added an exec file into /etc/vpp/startup.conf. It seems that it is executed 
only when it is started by systemd (systemctl start vpp)? If I run "vpp unix 
interactive", it does not run the exec file, is this expected?

I was running 17.10 debug build. My vpp crashed and I was not able to find core 
file. That is why I switched to run vpp interactively. Will this get me the 
needed coredump?

I guess my real, important question is how to get stack trace to find out why 
my vpp crashed.

John



___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] WHERE IS libpneum.so ???

[Luke, Chris]

Already on it :)

> -Original Message-
> From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On
> Behalf Of Ole Troan
> Sent: Thursday, November 2, 2017 10:13
> To: Holoo Gulakh 
> Cc: vpp-dev@lists.fd.io
> Subject: Re: [vpp-dev] WHERE IS libpneum.so ???
> 
> Hi,
> 
> as Chris said it has been renamed to libvppapiclient.so First to update the 
> wiki
> gets an ice cream in the mail!
> 
> Best regards,
> Ole
> 
> > On 2 Nov 2017, at 14:31, Holoo Gulakh  wrote:
> >
> > Hi
> > I am installing VPP Python API
> > Here https://wiki.fd.io/view/VPP/Python_API
> > there is a command :
> > export LD_LIBRARY_PATH=`find $VPP -name "libpneum.so" -exec dirname
> {}
> > \; | grep python | head -n 1`
> >
> > but there is no libpneum.so in $VPP and anywhere else :( Please help
> >
> > ___
> > vpp-dev mailing list
> > vpp-dev@lists.fd.io
> > https://lists.fd.io/mailman/listinfo/vpp-dev

___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] WHERE IS libpneum.so ???

[Luke, Chris]

Hello,

Please see the reply I sent just now to the same question asked by another 
person on this list.

Short version: I believe libpneum was superceded; the wiki was not updated.  
Details in other msg.

Chris.

From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On 
Behalf Of Holoo Gulakh
Sent: Thursday, November 2, 2017 9:31
To: vpp-dev@lists.fd.io
Subject: [vpp-dev] WHERE IS libpneum.so ???

Hi
I am installing VPP Python API
Here https://wiki.fd.io/view/VPP/Python_API
there is a command :

export LD_LIBRARY_PATH=`find $VPP -name "libpneum.so" -exec dirname {} \; | 
grep python | head -n 1`

but there is no libpneum.so in $VPP and anywhere else :(

Please help


___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] libpneum.so not exist, installing vpp python api

[Luke, Chris]

I believe libpneum is a historical artifact and no longer accurate.

The Python binding module now uses libvppapiclient, built from 
src/vpp-api/client/client.c.

By way of example, for development, I use these env vars:

vppinst="$HOME/dev/fdio/vpp/build-root/install-vpp_debug-native/vpp"
export LD_LIBRARY_PATH="$vppinst/lib64"
export PYTHONPATH="$vppinst/lib/python2.7/site-packages"

Chris

From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On 
Behalf Of mirzaei.reza
Sent: Thursday, November 2, 2017 8:55
To: vpp-dev@lists.fd.io
Subject: [vpp-dev] libpneum.so not exist, installing vpp python api


Hi

I was installed vpp from source according to this 
link
 and it was successful. then i tried to install VPP/Python API according to 
this link:

First of all it says:

The main VPP build will build the C library (libpneum.so). If VPP is installed 
via the Linux package system that library will be available on the system. To 
run within a build directory, set LD_LIBRARY_PATH to point to the location of 
libpneum.so

However, there was no libpneum.so at all.

How can i fix this problem?

Best regards,

Reza


___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] vpp building problem

[Luke, Chris]

Hello,

If you want to run it as a service then I suggest you use the pre-built 
packages, or build the packages yourself and install those. Only the act of 
installing a package prepares the underlying system to run VPP as a system 
service.

The build instruction you gave leaves the built binaries in-situ in the 
build-root tree of the source directory; this is intended for development. You 
can run it in-situ with helper commands like “make debug” or “make run”. There 
are many such helpers, simply type “make” to see them.

What you do depends on what you are trying to achieve.

Cheers,
Chris.

From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On 
Behalf Of Holoo Gulakh
Sent: Wednesday, November 01, 2017 12:50 PM
To: vpp-dev@lists.fd.io
Subject: [vpp-dev] vpp building problem

Hi all
i'm trying to install vpp from source on Ubuntu 16.04 server (without 
virtualization). I obeyed the following this link:

https://wiki.fd.io/view/VPP/Pulling,_Building,_Running,_Hacking_and_Pushing_VPP_Code#Pulling_anonymously_.28https.29

So i did as such:
sudo -s
cd /

git clone https://gerrit.fd.io/r/vpp

cd vpp/
make install-dep
make bootstrap
make build

reboot

after boot:
sudo -s
service vpp start

But i got:
 Failed to start vpp.service: Unit vpp.service not found.

What should i do?

Thanks.

___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] Number of interfaces configurable restriction

[Luke, Chris]

# cat /proc/sys/fs/nr_open
1048576


That is the ceiling on what value can be set for the open files limit (aka 
RLIMIT_NOFILE) with Linux.

Chris.

From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On 
Behalf Of Jan Srnicek -X (jsrnicek - PANTHEON TECHNOLOGIES at Cisco)
Sent: Sunday, October 29, 2017 11:17
To: Steven Luong (sluong) ; vpp-dev 
Subject: Re: [vpp-dev] Number of interfaces configurable restriction

Thanks for info Steven

Is there any upper boundary for „ulimit –n“, or is it just till i run out of 
memory ?

[banner11]



Jan Srnicek
Engineer - Software
jsrni...@cisco.com
Tel:

Cisco Systems, Inc.



Slovakia
cisco.com


[http://www.cisco.com/assets/swa/img/thinkbeforeyouprint.gif]Think before you 
print.

This email may contain confidential and privileged material for the sole use of 
the intended recipient. Any review, use, distribution or disclosure by others 
is strictly prohibited. If you are not the intended recipient (or authorized to 
receive for the recipient), please contact the sender by reply email and delete 
all copies of this message.
Please click 
here for 
Company Registration Information.


From: Steven Luong (sluong)
Sent: Friday, October 27, 2017 6:20 PM
To: Jan Srnicek -X (jsrnicek - PANTHEON TECHNOLOGIES at Cisco) 
>; vpp-dev 
>
Subject: Re: [vpp-dev] Number of interfaces configurable restriction

Jan,

You have to use ulimit –n to raise the number of open files if you are going to 
create a lot of interfaces.

Steven

From: > on 
behalf of "Jan Srnicek -X (jsrnicek - PANTHEON TECHNOLOGIES at Cisco)" 
>
Date: Friday, October 27, 2017 at 3:31 AM
To: vpp-dev >
Subject: [vpp-dev] Number of interfaces configurable restriction

Hi

While doing some perf testing for honeycomb , i’ve came about something that 
seems like internal restriction of vpp.

While trying to configure as much Tap interfaces as possible, when i got to 
510, i started to get

Caused by: io.fd.vpp.jvpp.VppCallbackException: vppApi.tap_connect_reply 
failed: System call error #1 (error code: -11)

Is this internal restriction of vpp on number of interfaces or bug ?

Note: Happens for Vhost too

[anner11]



Jan Srnicek
Engineer - Software
jsrni...@cisco.com
Tel:

Cisco Systems, Inc.



Slovakia
cisco.com


[ttp://www.cisco.com/assets/swa/img/thinkbeforeyouprint.gif]Think before you 
print.

This email may contain confidential and privileged material for the sole use of 
the intended recipient. Any review, use, distribution or disclosure by others 
is strictly prohibited. If you are not the intended recipient (or authorized to 
receive for the recipient), please contact the sender by reply email and delete 
all copies of this message.
Please click 
here for 
Company Registration Information.


___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] Not able to see PCI NICs in show int

[Luke, Chris]

Run the VPP binary by hand, with something like “vpp unix interactive” to see 
what it says about DPDK.

It will tell you whether your ports are unsupported. I have a feeling that 
Broadcom part is not supported by DPDK, but the Intel one should be.

Other reasons why it may ignore them include if they are already configured 
(logically “up” or have an IP address). You can override that with something 
like “dpdk { dev :42:00.0 dev :42:00.1 }” in the startup.conf or 
similar.

Chris.

From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On 
Behalf Of John Wei
Sent: Friday, October 27, 2017 15:09
To: vpp-dev 
Subject: Re: [vpp-dev] Not able to see PCI NICs in show int

Additional info:

./usertools/dpdk-devbind.py --status
Network devices using DPDK-compatible driver



Network devices using kernel driver
===
:01:00.0 'NetXtreme BCM5720 Gigabit Ethernet PCIe 165f' if=em1 drv=tg3 
unused=uio_pci_generic *Active*
:01:00.1 'NetXtreme BCM5720 Gigabit Ethernet PCIe 165f' if=em2 drv=tg3 
unused=uio_pci_generic
:02:00.0 'NetXtreme BCM5720 Gigabit Ethernet PCIe 165f' if=em3 drv=tg3 
unused=uio_pci_generic
:02:00.1 'NetXtreme BCM5720 Gigabit Ethernet PCIe 165f' if=em4 drv=tg3 
unused=uio_pci_generic
:04:00.0 'NetXtreme BCM5719 Gigabit Ethernet PCIe 1657' if=p5p1 drv=tg3 
unused=uio_pci_generic
:04:00.1 'NetXtreme BCM5719 Gigabit Ethernet PCIe 1657' if=p5p2 drv=tg3 
unused=uio_pci_generic
:04:00.2 'NetXtreme BCM5719 Gigabit Ethernet PCIe 1657' if=p5p3 drv=tg3 
unused=uio_pci_generic
:04:00.3 'NetXtreme BCM5719 Gigabit Ethernet PCIe 1657' if=p5p4 drv=tg3 
unused=uio_pci_generic
:42:00.0 '82599ES 10-Gigabit SFI/SFP+ Network Connection 10fb' if=p4p1 
drv=ixgbe unused=uio_pci_generic
:42:00.1 '82599ES 10-Gigabit SFI/SFP+ Network Connection 10fb' if=p4p2 
drv=ixgbe unused=uio_pci_generic


On Fri, Oct 27, 2017 at 11:51 AM, John Wei 
> wrote:
I am following the instructions below:
https://wiki.fd.io/view/VPP/How_To_Connect_A_PCI_Interface_To_VPP

"show int" just returned one local0 device
If a NIC is not shown in the "show int" output, I can't configure further.

Need advice on how to get these PCI devices shown in "show int"

John

I am running v17.10-release bits on CentOS 7 using  uio_pci_generic, and two 
plugins:
  1. dpdk_plugin.so   17.10-release
Data Plane Development Kit (DPDK)
  2. lb_plugin.so 17.10-release
Load Balancer


I can see my pci nics through "vppctl show pci | grep '^000'"
:01:00.0   0  14e4:165f   5.0 GT/s x1  tg3 Broadcom NetXtreme 
Gigabit Ether PN: BCM95720
:01:00.1   0  14e4:165f   5.0 GT/s x1  tg3 Broadcom NetXtreme 
Gigabit Ether PN: BCM95720
:02:00.0   0  14e4:165f   5.0 GT/s x1  tg3 Broadcom NetXtreme 
Gigabit Ether PN: BCM95720
:02:00.1   0  14e4:165f   5.0 GT/s x1  tg3 Broadcom NetXtreme 
Gigabit Ether PN: BCM95720
:04:00.0   0  14e4:1657   5.0 GT/s x4  tg3 Broadcom NetXtreme 
Gigabit Ether PN: BCM95719
:04:00.1   0  14e4:1657   5.0 GT/s x4  tg3 Broadcom NetXtreme 
Gigabit Ether PN: BCM95719
:04:00.2   0  14e4:1657   5.0 GT/s x4  tg3 Broadcom NetXtreme 
Gigabit Ether PN: BCM95719
:04:00.3   0  14e4:1657   5.0 GT/s x4  tg3 Broadcom NetXtreme 
Gigabit Ether PN: BCM95719

output from "lshw -class network -businfo"
Bus info  Device  Class  Description

pci@:02:00.0  em3 networkNetXtreme 
BCM5720 Gigabit Ethernet PCIe
pci@:02:00.1  em4 networkNetXtreme 
BCM5720 Gigabit Ethernet PCIe
pci@:01:00.0  em1 networkNetXtreme 
BCM5720 Gigabit Ethernet PCIe
pci@:01:00.1  em2 networkNetXtreme 
BCM5720 Gigabit Ethernet PCIe
pci@:04:00.0  p5p1networkNetXtreme 
BCM5719 Gigabit Ethernet PCIe
pci@:04:00.1  p5p2networkNetXtreme 
BCM5719 Gigabit Ethernet PCIe
pci@:04:00.2  p5p3networkNetXtreme 
BCM5719 Gigabit Ethernet PCIe
pci@:04:00.3  p5p4networkNetXtreme 
BCM5719 Gigabit Ethernet PCIe
pci@:42:00.0  p4p1network82599ES 
10-Gigabit SFI/SFP+ Network Connection
pci@:42:00.1  p4p2network82599ES 
10-Gigabit SFI/SFP+ Network Connection






___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] VPP 17.10 Released

[Luke, Chris]

Nice! :)

> -Original Message-
> From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On
> Behalf Of Florin Coras
> Sent: Thursday, October 26, 2017 17:36
> To: vpp-dev 
> Subject: [vpp-dev] VPP 17.10 Released
> 
> Dear VPP community,
> 
> The VPP 17.10 release is complete. The release artefacts are now available on
> the nexus server and the repos have been updated.
> 
> I’d like to take this opportunity to thank you all for your continued support
> for VPP.
> 
> Regards,
> Florin
> ___
> vpp-dev mailing list
> vpp-dev@lists.fd.io
> https://lists.fd.io/mailman/listinfo/vpp-dev
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] 17.10 draft release notes

[Luke, Chris]

Hrm, I personally feel the breakdown by file to be more useful than who made 
the change.

Chris

> -Original Message-
> From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On
> Behalf Of Florin Coras
> Sent: Wednesday, October 25, 2017 1:58 PM
> To: Ole Troan 
> Cc: vpp-dev 
> Subject: Re: [vpp-dev] 17.10 draft release notes
> 
> Updated release notes to use the format Jon proposed.
> 
> Florin
> 
> > On Oct 25, 2017, at 9:11 AM, Ole Troan  wrote:
> >
> > Thanks Jon, love that!
> >
> > So something like:
> > git shortlog --format="* [%h] %s" v17.07..v17.10-rc2 -- *.api
> >
> > Cheers,
> > Ole
> >
> >
> >> On 25 Oct 2017, at 07:13, Jon Loeliger  wrote:
> >>
> >> On Wed, Oct 25, 2017 at 7:28 AM, Ole Troan 
> wrote:
> >> Hi Florin,
> >>
> >> Hi Ole,
> >>
> >> What about something like this?
> >>
> >> #!/usr/bin/env python
> >> import os, fnmatch, subprocess
> >> starttag = 'v17.07'
> >> endtag = 'v17.10-rc2'
> >> apifiles = []
> >> for root, dirnames, filenames in os.walk('.'):
> >>for filename in fnmatch.filter(filenames, '*.api'):
> >>apifiles.append(os.path.join(root, filename)) for f in
> >> apifiles:
> >>commits = subprocess.check_output(['git', 'log',
> >>   '--oneline', starttag + '..' + 
> >> endtag,
> >>   f])
> >>if commits:
> >>print f
> >>print commits
> >>
> >>
> >> Just as an FYI, Git might be able to help simplify some of this
> >> script for you too.  For example:
> >>
> >>$ git ls-files *.api
> >>src/examples/sample-plugin/sample/sample.api
> >>src/plugins/acl/acl.api
> >>src/plugins/dpdk/api/dpdk.api
> >>src/plugins/flowprobe/flowprobe.api
> >>src/plugins/gtpu/gtpu.api
> >>
> >>
> >> Depending on development at HEAD, you may want:
> >>$ git ls-files v17.10-rc2 *.api
> >> or so.
> >>
> >> Then, if you are not too concerned about the individual break-down by
> >> file, you can one-line it:
> >>
> >>$ git log --oneline v17.07..v17.10-rc2 -- *.api
> >>50570ec Update of free text tag patch for BD
> >>831fb59 Stats refactor
> >>2297af0 Add a name to the creation of an IP and MPLS table
> >>c29940c ACL-plugin add "replace" semantics for adding a new MacIP acl
> >>8a19f12 Allow individual stats API and introduce stats.api -
> want_interface_simple_stats - want_interface_combined_stats -
> want_ip4|6_fib|nbr_stats
> >>d630713 LISP: add neighbor discovery and CP protocol separation APIs
> >>111a5ce LISP: Add APIs for enable/disable xTR/P-ITR/P-ETR modes
> >>4802632 Punt socket: Fix coverity error for pathname length mismatch
> between API and sun_path.
> >>33e002b Fix session connect_* api message handling.
> >>
> >>
> >> Also, the "shortlog" command is tailored to producing release notes:
> >>
> >>$ git shortlog v17.07..v17.10-rc2 -- *.api
> >>Dave Barach (1):
> >>  TCP source address automation
> >>
> >>Dave Wallace (1):
> >>  Fix session connect_* api message handling.
> >>
> >>Eyal Bari (3):
> >>  API:fix arp/ND event messages - remove context
> >>  SPAN:add l2 mirror
> >>  SPAN/API:enable L2 dump
> >>
> >>Filip Tehlar (4):
> >>  LISP: make TTL for map register messages configurable
> >>  LISP: Map-server fallback feature
> >>  LISP: Add APIs for enable/disable xTR/P-ITR/P-ETR modes
> >>  LISP: add neighbor discovery and CP protocol separation APIs
> >>
> >>
> >> HTH,
> >> jdl
> >
> 
> ___
> vpp-dev mailing list
> vpp-dev@lists.fd.io
> https://lists.fd.io/mailman/listinfo/vpp-dev

___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] a vppctl ping bug in 17.10-rc2?

[Luke, Chris]

Yes, please file a bug at jira.fd.io . I’ll look into this soon, suspect it’s 
an interaction of the non-interactive cli interface.

Chris.

From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On 
Behalf Of John Wei
Sent: Wednesday, October 25, 2017 18:53
To: vpp-dev@lists.fd.io
Subject: [vpp-dev] a vppctl ping bug in 17.10-rc2?

in 17.07.01
a vppctl ping  works. It ping 5 times, then stop.

in 17.10-rc2
same vppctl ping command, got aborted:

64 bytes from 10.10.2.2: icmp_seq=2 ttl=64 time=.3473 ms
Aborted due to a keypress.

I not familiar with the code yet. Just to file bug. :)

John

___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] gerrit http authentication

[Luke, Chris]

Just to be unambiguous for the archives, you mean HTTP authentication when 
pushing patches to Gerrit with Git, and not interactive browsing of the UI?

Chris.

From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On 
Behalf Of Gabriel Ganne
Sent: Thursday, October 19, 2017 4:13
To: vpp-dev@lists.fd.io
Subject: [vpp-dev] gerrit http authentication


Hi,



Unless I'm mistaken, it seems http authentication has been removed from gerrit.

It was useful to me, as I work in a company where any non-http traffic is 
blocked.



Do you think it's possible to restore it ?



Best regards,



--

Gabriel Ganne
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] syslog in snat

[Luke, Chris]

I’m sure there is, but it’s not a very squeaky wheel.

Also, patches welcome. :) Best way to get familiar with the code is to get up 
to your elbows in it!

Cheers,
Chris.

From: Matt Paska [mailto:mattjpa...@gmail.com]
Sent: Friday, October 13, 2017 18:51
To: Florin Coras <fcoras.li...@gmail.com>
Cc: Luke, Chris <chris_l...@cable.comcast.com>; Matus Fabian -X (matfabia - 
PANTHEON TECHNOLOGIES at Cisco) <matfa...@cisco.com>; vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] syslog in snat

I understand, thanks! I just mean in general if there wasn't interest in Syslog 
in SNAT. Looking back the thread, I chimed in June about it being included 
17.07. I'm not too familiar with the SNAT codebase myself to help directly so 
I'm trying to figure out if there is possibility for the future.

On Fri, Oct 13, 2017 at 3:40 PM, Florin Coras 
<fcoras.li...@gmail.com<mailto:fcoras.li...@gmail.com>> wrote:
Indeed!

Florin

On Oct 13, 2017, at 3:31 PM, Luke, Chris 
<chris_l...@comcast.com<mailto:chris_l...@comcast.com>> wrote:

The release stable branch was forked several weeks ago; at this point it the 
release only accepts bug fixes.

Chris.

From: vpp-dev-boun...@lists.fd.io<mailto:vpp-dev-boun...@lists.fd.io> 
[mailto:vpp-dev-boun...@lists.fd.io] On Behalf Of Matt Paska
Sent: Friday, October 13, 2017 17:11
To: Matus Fabian -X (matfabia - PANTHEON TECHNOLOGIES at Cisco) 
<matfa...@cisco.com<mailto:matfa...@cisco.com>>
Cc: vpp-dev@lists.fd.io<mailto:vpp-dev@lists.fd.io>
Subject: Re: [vpp-dev] syslog in snat

Thanks for the info. Is there not enough interest to warrant being included?

On Thu, Oct 12, 2017 at 9:26 PM, Matus Fabian -X (matfabia - PANTHEON 
TECHNOLOGIES at Cisco) <matfa...@cisco.com<mailto:matfa...@cisco.com>> wrote:
Syslog in NAT plugin is not a part of 17.10 release.

Matus


From: vpp-dev-boun...@lists.fd.io<mailto:vpp-dev-boun...@lists.fd.io> 
[mailto:vpp-dev-boun...@lists.fd.io<mailto:vpp-dev-boun...@lists.fd.io>] On 
Behalf Of Matt Paska
Sent: Friday, October 13, 2017 2:48 AM
To: Ole Troan <otr...@employees.org<mailto:otr...@employees.org>>
Cc: vpp-dev@lists.fd.io<mailto:vpp-dev@lists.fd.io>

Subject: Re: [vpp-dev] syslog in snat

Hi all,

Is Syslog in SNAT planned for the upcoming 17.10 release?

Thanks!

On Thu, Jun 22, 2017 at 6:48 PM, Matt Paska 
<mattjpa...@gmail.com<mailto:mattjpa...@gmail.com>> wrote:
We just don't have ipfix collectors setup right now. We have a system for 
syslog and I was hoping to integrate vpp snat into that as well.

Thanks for the quick response.

On Thu, Jun 22, 2017 at 2:50 PM, Ole Troan 
<otr...@employees.org<mailto:otr...@employees.org>> wrote:
Tell me more.

Ole

On 22 Jun 2017, at 23:37, Matt Paska 
<mattjpa...@gmail.com<mailto:mattjpa...@gmail.com>> wrote:
Yes, we do need it. What's the current plan?

On Thu, Jun 22, 2017 at 1:05 PM, Ole Troan 
<otr...@employees.org<mailto:otr...@employees.org>> wrote:
Matt,

It will not have it for 17.07.
We have ipfix support now as well as deterministic.

Do you need it?

Cheers
Ole

On 22 Jun 2017, at 21:33, Matt Paska 
<mattjpa...@gmail.com<mailto:mattjpa...@gmail.com>> wrote:
Hi,

Is Snat syslog based logging support still planned for 17.07? I see it 
mentioned on the release plan 
wiki(https://wiki.fd.io/view/Projects/vpp/Release_Plans/Release_Plan_17.07) but 
not on the snat work list(https://wiki.fd.io/view/VPP/SNAT).

Thanks

On Tue, May 23, 2017 at 10:45 PM, Matus Fabian -X (matfabia - PANTHEON 
TECHNOLOGIES at Cisco) <matfa...@cisco.com<mailto:matfa...@cisco.com>> wrote:
Hi,

Snat plugin doesn’t support syslog logging, currently support only IPFIX.

Regards,
Matus

From: vpp-dev-boun...@lists.fd.io<mailto:vpp-dev-boun...@lists.fd.io> 
[mailto:vpp-dev-boun...@lists.fd.io<mailto:vpp-dev-boun...@lists.fd.io>] On 
Behalf Of Matt Paska
Sent: Tuesday, May 23, 2017 8:23 PM
To: vpp-dev@lists.fd.io<mailto:vpp-dev@lists.fd.io>; Jim Thompson 
<j...@netgate.com<mailto:j...@netgate.com>>
Cc: Andrew Taylor 
<andrew2016tay...@gmail.com<mailto:andrew2016tay...@gmail.com>>
Subject: Re: [vpp-dev] syslog in snat

Is there further info/docs on using syslog for snat on the wiki? I searched 
through but couldn't find anything.

Thanks.

On Sat, May 13, 2017 at 10:32 PM, Jim Thompson 
<j...@netgate.com<mailto:j...@netgate.com>> wrote:

On May 13, 2017, at 11:58 PM, Andrew Taylor 
<andrew2016tay...@gmail.com<mailto:andrew2016tay...@gmail.com>> wrote:

Hi,
Could you please explain what is "Syslog based SNAT login" in Release Plan 17.07

Added here, so you could ask
https://wiki.fd.io/index.php?title=Projects%2Fvpp%2FRelease_Plans%2FRelease_Plan_17.07<https://wiki.fd.io/index.php?title=Projects/vpp/Release_Plans/Release_Plan_17.07>iff=5072=5

Re: [vpp-dev] syslog in snat

[Luke, Chris]

The release stable branch was forked several weeks ago; at this point it the 
release only accepts bug fixes.

Chris.

From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On 
Behalf Of Matt Paska
Sent: Friday, October 13, 2017 17:11
To: Matus Fabian -X (matfabia - PANTHEON TECHNOLOGIES at Cisco) 

Cc: vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] syslog in snat

Thanks for the info. Is there not enough interest to warrant being included?

On Thu, Oct 12, 2017 at 9:26 PM, Matus Fabian -X (matfabia - PANTHEON 
TECHNOLOGIES at Cisco) > wrote:
Syslog in NAT plugin is not a part of 17.10 release.

Matus


From: vpp-dev-boun...@lists.fd.io 
[mailto:vpp-dev-boun...@lists.fd.io] On 
Behalf Of Matt Paska
Sent: Friday, October 13, 2017 2:48 AM
To: Ole Troan >
Cc: vpp-dev@lists.fd.io

Subject: Re: [vpp-dev] syslog in snat

Hi all,

Is Syslog in SNAT planned for the upcoming 17.10 release?

Thanks!

On Thu, Jun 22, 2017 at 6:48 PM, Matt Paska 
> wrote:
We just don't have ipfix collectors setup right now. We have a system for 
syslog and I was hoping to integrate vpp snat into that as well.

Thanks for the quick response.

On Thu, Jun 22, 2017 at 2:50 PM, Ole Troan 
> wrote:
Tell me more.

Ole

On 22 Jun 2017, at 23:37, Matt Paska 
> wrote:
Yes, we do need it. What's the current plan?

On Thu, Jun 22, 2017 at 1:05 PM, Ole Troan 
> wrote:
Matt,

It will not have it for 17.07.
We have ipfix support now as well as deterministic.

Do you need it?

Cheers
Ole

On 22 Jun 2017, at 21:33, Matt Paska 
> wrote:
Hi,

Is Snat syslog based logging support still planned for 17.07? I see it 
mentioned on the release plan 
wiki(https://wiki.fd.io/view/Projects/vpp/Release_Plans/Release_Plan_17.07) but 
not on the snat work list(https://wiki.fd.io/view/VPP/SNAT).

Thanks

On Tue, May 23, 2017 at 10:45 PM, Matus Fabian -X (matfabia - PANTHEON 
TECHNOLOGIES at Cisco) > wrote:
Hi,

Snat plugin doesn’t support syslog logging, currently support only IPFIX.

Regards,
Matus

From: vpp-dev-boun...@lists.fd.io 
[mailto:vpp-dev-boun...@lists.fd.io] On 
Behalf Of Matt Paska
Sent: Tuesday, May 23, 2017 8:23 PM
To: vpp-dev@lists.fd.io; Jim Thompson 
>
Cc: Andrew Taylor 
>
Subject: Re: [vpp-dev] syslog in snat

Is there further info/docs on using syslog for snat on the wiki? I searched 
through but couldn't find anything.

Thanks.

On Sat, May 13, 2017 at 10:32 PM, Jim Thompson 
> wrote:

On May 13, 2017, at 11:58 PM, Andrew Taylor 
> wrote:

Hi,
Could you please explain what is "Syslog based SNAT login" in Release Plan 17.07

Added here, so you could ask
https://wiki.fd.io/index.php?title=Projects%2Fvpp%2FRelease_Plans%2FRelease_Plan_17.07iff=5072=5071


Is it an alternative option for logging session like IPFIX ?

I suspect this was intended to be “syslog-based SNAT logging”, and that only 
the final ‘g’ is missing.



___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev


___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev




___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] Mac Address Api Changes

[Luke, Chris]

+1 Sounds good to me

From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On 
Behalf Of John Lo (loj)
Sent: Tuesday, October 10, 2017 15:42
To: Jerome Tollet (jtollet) ; Mohsin Kazmi (sykazmi) 
; vpp-dev 
Subject: Re: [vpp-dev] Mac Address Api Changes

The two APIs affected are the older ones in L2FIB which use “u64 mac” instead 
of “u8 mac[6]” to pass MAC addresses:

  *   L2fib_add_del
  *   L2_fib_table_details

I believe it is a good change to reduce confusion wrt how 6-byte MAC is stored 
in u64 with big/little endian hosts. The change would also require updates to 
user programs of these APIs, which we believe should be minimal.

If we don’t get strong objections within a week, we will assume the change is 
acceptable and allow this API change in the master branch. It won’t affect 
17.10 release.

Regards,
John

From: vpp-dev-boun...@lists.fd.io 
[mailto:vpp-dev-boun...@lists.fd.io] On Behalf Of Jerome Tollet (jtollet)
Sent: Tuesday, October 10, 2017 3:10 PM
To: Mohsin Kazmi (sykazmi) >; 
vpp-dev >
Subject: Re: [vpp-dev] Mac Address Api Changes

+1, it would be nice to harmonize those API calls.
Jerome

De : > au nom 
de Mohsin Kazmi >
Date : lundi 9 octobre 2017 à 19:06
À : vpp-dev >
Objet : [vpp-dev] Mac Address Api Changes


Hello,​



I am writing regarding a proposal to change API messages related to l2fib mac 
address.



In vpp/src/vnet/l2/l2.api file, currently two API messages related to l2fib 
uses u64 for mac address instead of u8 mac[6]. While rest of VPP API calls use 
array of six bytes to store mac address.



As u64 to store mac address is inconsistent with rest of VPP and may create 
conversion troubles to interpret to/from u8 mac[6].



The proposal is to change those API messages definitions to use standard u8 
mac[6] to store mac address. But this change may impact the users of VPP API 
and they will need to update their code.



​That said, Please let the community know if there is any specific objection or 
opinion to above proposal.



Thanks,

Mohsin




___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] vlan sub interfaces

[Luke, Chris]

Eeh, we haven't previously advertised support for VLAN tags on af_packet 
before; I could believe it was a missing feature, but I have a harder time 
accepting it was a bug.

I'm not strongly against the merge (though I do have a preference for strongly 
encouraging people to keep up with releases at this time), but I do want us to 
be clear about the disposition of this change.

Chris.

> -Original Message-
> From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On
> Behalf Of prabh...@techtrueup.com
> Sent: Friday, September 29, 2017 11:43
> To: Neale Ranns (nranns) 
> Cc: vpp-dev@lists.fd.io
> Subject: Re: [vpp-dev] vlan sub interfaces
> 
> well looking at the change it definitely suggests to be a bug fix.
> 
> we are currently using 1707 builds, and dont have plan to move to newer
> release right now, so would prefer a merge to 1707.
> 
> Regards,
> Prabhjot
> 
> Quoting "Neale Ranns (nranns)"
> :
> 
> > With my release manager hat on …
> > Do we consider support for VLAN tags on an AF packet interface a bug
> > fix (to be back ported) or a new feature (available from 17.10
> > onwards)?
> >
> > /neale
> >
> > -Original Message-
> > From: "prabh...@techtrueup.com" 
> > Date: Thursday, 28 September 2017 at 13:07
> > To: "Dave Barach (dbarach)" 
> > Cc: "Neale Ranns (nranns)" , "John Lo (loj)"
> > , "vpp-dev@lists.fd.io" , Akshaya
> > Nadahalli 
> > Subject: Re: [vpp-dev] vlan sub interfaces
> >
> > yes i verified it on stable/1707 itself.
> >
> > Regards,
> > Prabhjot
> >
> > Quoting "Dave Barach (dbarach)" :
> >
> > > See https://gerrit.fd.io/r/#/c/8590. The patch cherry-picked easily
> > > to stable/1707.
> > >
> > > Assuming that the cherry-pick patch validates - and that it solves
> > > your problem - it will be up to Neale [as the 17.07 release manager]
> > > whether to merge it or not.
> > >
> > > Please let us know whether the cherry-pick patch works for you.
> > >
> > > Thanks… Dave
> > >
> > > From: vpp-dev-boun...@lists.fd.io
> > > [mailto:vpp-dev-boun...@lists.fd.io] On Behalf Of Prabhjot Singh Sethi
> > > Sent: Thursday, September 28, 2017 3:27 PM
> > > To: Akshaya Nadahalli ; Prabhjot Singh Sethi
> > > ; vpp-dev@lists.fd.io; John Lo (loj)
> > > 
> > > Subject: Re: [vpp-dev] vlan sub interfaces
> > >
> > > yes it works perfectly fine with this patch.
> > > i hope this will be pushed to 17.07 branch as well.
> > >
> > > Thanks for the help :)
> > >
> > > Regards,
> > > Prabhjot
> > >
> > > - Original Message -
> > > From:
> > > "Akshaya Nadahalli"
> >
> > >
> > > To:
> > > "Prabhjot Singh Sethi"
> > > >,
> > > >, "John Lo"
> > > >
> > > Cc:
> > >
> > > Sent:
> > > Thu, 28 Sep 2017 19:18:50 +0530
> > > Subject:
> > > Re: [vpp-dev] vlan sub interfaces
> > >
> > >
> > > Hi Prabhjot,
> > >
> > >
> > >
> > > Can you pls try with below patch and see if it helps:
> > >
> > > https://gerrit.fd.io/r/#/c/8435/
> > >
> > >
> > >
> > > Regards,
> > >
> > > Akshaya N
> > >
> > > On Thursday 28 September 2017 03:45 PM, Prabhjot Singh Sethi wrote:
> > > trying again with more appropriate subject
> > >
> > > Can some one please help if i am missing any thing over here ?
> > >
> > > As mentioned earlier, i have interface host-eth10 and sub interface
> > > host-eth10.10 (create sub host-eth10 10)
> > > host-eth10 is associated to bridge domain 2 and sub interface is
> > > associated to bridge domain 3
> > > when VPP receives tagged packet with vlan 10 it still associates it
> > > to bd 2 and not bd 3
> > >
> > > Note: if i don't associate any bd with base interface it just drops
> > > the packet with some error.
> > >
> > > Regards,
> > > Prabhjot
> > >
> > >
> > > ___
> > > vpp-dev mailing list
> > > vpp-dev@lists.fd.io
> > > https://lists.fd.io/mailman/listinfo/vpp-dev
> > >
> > > --
> > > Regards,
> > > Akshaya N
> 
> 
> ___
> vpp-dev mailing list
> vpp-dev@lists.fd.io
> https://lists.fd.io/mailman/listinfo/vpp-dev
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] Stable branch for 17.10 pulled

[Luke, Chris]

Great work, Florin!

Cheers,
Chris.

From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On 
Behalf Of Florin Coras
Sent: Wednesday, September 27, 2017 21:46
To: vpp-dev 
Subject: [vpp-dev] Stable branch for 17.10 pulled

Folks,

The release branch, stable/1710, for VPP 17.10 has now been pulled and tags 
have been laid. As a result, master is yet again open for all changes.

From this point onward, up until the release date on October 25th [1], we need 
to be disciplined with respect to bugfixes. Here is the traditional list of 
common-sense suggestions:

  • All bug fixes must be double-committed to the release throttle 
as well as to the master branch
  • Commit first to the release throttle, then "git 
cherry-pick" into master
  • Manual merges may be required, depending on the 
degree of divergence between throttle and master
  • All bug fixes need to have a Jira ticket
  • Please put Jira IDs into the commit messages.
  • Please use the same Jira ID

Regards,
Florin

[1] https://wiki.fd.io/view/Projects/vpp/Release_Plans/Release_Plan_17.10
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] [discuss] FD.io Jenkins : 2017-09-21 @ 0430 UTC (9:30am PDT)

[Luke, Chris]

The idea was suggested so that to start with the suse jobs would not downvote 
the verified tag on failure, or upvote on success, so we could work on the 
environment without interfering with the rest of VPP.

What I don’t know is if we decided it was possible or not.

Chris.

From: Marco Varlese [mailto:marco.varl...@suse.com]
Sent: Friday, September 22, 2017 8:27
To: Luke, Chris <chris_l...@cable.comcast.com>; Vanessa Valderrama 
<vvalderr...@linuxfoundation.org>; infra-steer...@lists.fd.io; 
t...@lists.fd.io; disc...@lists.fd.io; vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] [discuss] FD.io Jenkins : 2017-09-21 @ 0430 UTC (9:30am 
PDT)

I think we had the issue with virtualenv before and I thought that was fixed 
(zypper in python-virtualenv python3-virtualenv).

Now, since you mentioned something new to me; what's the difference between 
voting and non-voting jobs? How are they chosen?


Cheers,
Marco

On Fri, 2017-09-22 at 12:10 +, Luke, Chris wrote:
I’m sure Vanessa will correct me where I am wrong, but I the suse build was 
failing on basic things (missing virtualenv) and downvoting otherwise good 
patches; After I reported this I thought she was going to make them non-voting 
jobs (since it I thought I saw somewhere this is what they ought to be), but it 
seems it was removed from the trigger entirely.

Chris.

From: vpp-dev-boun...@lists.fd.io<mailto:vpp-dev-boun...@lists.fd.io> 
[mailto:vpp-dev-boun...@lists.fd.io] On Behalf Of Marco Varlese
Sent: Friday, September 22, 2017 3:29
To: Vanessa Valderrama 
<vvalderr...@linuxfoundation.org<mailto:vvalderr...@linuxfoundation.org>>; 
infra-steer...@lists.fd.io<mailto:infra-steer...@lists.fd.io>; 
t...@lists.fd.io<mailto:t...@lists.fd.io>; 
disc...@lists.fd.io<mailto:disc...@lists.fd.io>; 
vpp-dev@lists.fd.io<mailto:vpp-dev@lists.fd.io>
Subject: Re: [vpp-dev] [discuss] FD.io Jenkins : 2017-09-21 @ 0430 UTC (9:30am 
PDT)

Hi Vanessa,

Did this happen yesterday? I can see VPP being built on CentOS and Ubuntu only.

Can you please advice?


Thanks,
Marco

On Thu, 2017-09-21 at 10:57 -0500, Vanessa Valderrama wrote:

I'll be enabling openSUSE minions for VPP in Jenkins shortly.  I'll be 
monitoring VPP builds throughout the day. Please contact me via IRC fdio-infra 
(valderrv) if you experience any issues.
When:
2017-09-21 @ 0430 UTC (9:30am PDT)

Thank you,
Vanessa
On 09/14/2017 11:04 AM, Vanessa Valderrama wrote:

This change will be rescheduled at a later date.
Thank you,
Vanessa
On 09/13/2017 03:34 PM, Vanessa Valderrama wrote:

What:

LF is enabling openSUSE minions for VPP jobs in Jenkins

When:
2017-09-14 @ 0500 UTC (10am PDT)

Where:

Please contact valderrv via IRC fdio-meeting if you experiene any issue related 
to this change
Impact:
No restart is required for this change.  Once the change is made VPP jobs will 
build on openSUSE minions.



___

discuss mailing list

disc...@lists.fd.io<mailto:disc...@lists.fd.io>

https://lists.fd.io/mailman/listinfo/discuss
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] [discuss] FD.io Jenkins : 2017-09-21 @ 0430 UTC (9:30am PDT)

[Luke, Chris]

I’m sure Vanessa will correct me where I am wrong, but I the suse build was 
failing on basic things (missing virtualenv) and downvoting otherwise good 
patches; After I reported this I thought she was going to make them non-voting 
jobs (since it I thought I saw somewhere this is what they ought to be), but it 
seems it was removed from the trigger entirely.

Chris.

From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On 
Behalf Of Marco Varlese
Sent: Friday, September 22, 2017 3:29
To: Vanessa Valderrama ; 
infra-steer...@lists.fd.io; t...@lists.fd.io; disc...@lists.fd.io; 
vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] [discuss] FD.io Jenkins : 2017-09-21 @ 0430 UTC (9:30am 
PDT)

Hi Vanessa,

Did this happen yesterday? I can see VPP being built on CentOS and Ubuntu only.

Can you please advice?


Thanks,
Marco

On Thu, 2017-09-21 at 10:57 -0500, Vanessa Valderrama wrote:

I'll be enabling openSUSE minions for VPP in Jenkins shortly.  I'll be 
monitoring VPP builds throughout the day. Please contact me via IRC fdio-infra 
(valderrv) if you experience any issues.
When:
2017-09-21 @ 0430 UTC (9:30am PDT)

Thank you,
Vanessa
On 09/14/2017 11:04 AM, Vanessa Valderrama wrote:

This change will be rescheduled at a later date.
Thank you,
Vanessa
On 09/13/2017 03:34 PM, Vanessa Valderrama wrote:

What:

LF is enabling openSUSE minions for VPP jobs in Jenkins

When:
2017-09-14 @ 0500 UTC (10am PDT)

Where:

Please contact valderrv via IRC fdio-meeting if you experiene any issue related 
to this change
Impact:
No restart is required for this change.  Once the change is made VPP jobs will 
build on openSUSE minions.



___

discuss mailing list

disc...@lists.fd.io

https://lists.fd.io/mailman/listinfo/discuss
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

[vpp-dev] vppctl / cli improvements

[Luke, Chris]

FYI all, https://gerrit.fd.io/r/8491 fixes several vppctl and cli issues and 
generally makes them work together better.

Of most note to people is it (finally) fixes the noise vppctl was producing 
when used non-interactively. Ie, the command echo, welcome banner and CLI 
prompt are no more when you use it in a script or pass commands on the command 
line. This is achieved by having vppctl use a magic terminal type ("vppctl") to 
inform VPP to not dress the session up as an interactive one.

In working this I uncovered several long-standing issues, not least if the CLI 
socket dies before VPP has spoken to it, VPP didn't notice and ended up 
triggering a fatal SIGPIPE. Lovely! The commit message has extensive notes for 
the morbidly interested.

Anyway, once merged, keep a watch for any CLI issues I may have introduced; let 
me know if you come across anything odd or fatal.

Chris.
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] memmove fault

[Luke, Chris]

Decided it was the correct fix and just merged it, thanks.

 

Chris.

 

From: <vpp-dev-boun...@lists.fd.io> on behalf of "Luke, Chris" 
<chris_l...@comcast.com>
Date: Wednesday, September 20, 2017 at 07:04
To: "Yoann Desmouceaux (ydesmouc)" <ydesm...@cisco.com>, Florin Coras 
<fcoras.li...@gmail.com>, 薛欣颖 <xy...@fiberhome.com>
Cc: vpp-dev <vpp-dev@lists.fd.io>
Subject: Re: [vpp-dev] memmove fault

 

Thanks Yoann.

 

I’ll review it properly in a bit, have a bit of a drive this morning before I 
can get to it properly however.

 

On first reading though it seems that it always places the cursor at the end of 
the line when you cursor up or down. This is consistent with “bash” behavior. 
Will ponder if that is the behavior we want; I think I tried to deliberately 
avoid that, but this would be a simple range check if so. Thoughts anyone?

 

Chris.

 

From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On 
Behalf Of Yoann Desmouceaux (ydesmouc)
Sent: Wednesday, September 20, 2017 4:22
To: Florin Coras <fcoras.li...@gmail.com>; 薛欣颖 <xy...@fiberhome.com>
Cc: vpp-dev <vpp-dev@lists.fd.io>
Subject: Re: [vpp-dev] memmove fault

 

Hello,

 

I also stumbled upon this bug a few times. I just submitted 
https://gerrit.fd.io/r/#/c/8468, hopefully this fixes this issue.

 

Cheers,

Yoann

 

From: <vpp-dev-boun...@lists.fd.io> on behalf of Florin Coras 
<fcoras.li...@gmail.com>
Date: Wednesday, 20 September 2017 at 08:10
To: 薛欣颖 <xy...@fiberhome.com>
Cc: vpp-dev <vpp-dev@lists.fd.io>
Subject: Re: [vpp-dev] memmove fault

 

Hi,  

 

Could this be a result of: type a command in the cli and don’t execute it, 
press up-arrow, try to input a new command in the empty prompt line, sigsegv?

 

Florin

 

P.S. Chris, apologies, I plead guilty for not trying to debug it … 

 

On Sep 19, 2017, at 10:52 PM, 薛欣颖 <xy...@fiberhome.com> wrote:

 


Hi Chris,

 

Until today, the problem only appeared again:

 

Program received signal SIGSEGV, Segmentation fault.
__memmove_ssse3_back () at ../sysdeps/x86_64/multiarch/memcpy-ssse3-back.S:1663
1663../sysdeps/x86_64/multiarch/memcpy-ssse3-back.S: No such file or 
directory.
(gdb) bt
#0  __memmove_ssse3_back () at 
../sysdeps/x86_64/multiarch/memcpy-ssse3-back.S:1663
#1  0x7796531f in unix_cli_line_process_one (cm=0x77ba6d80 
, um=0x77ba77e0 , cf=0x7fffb5e5bf80, 
uf=0x7fffb5e5bf24, 
input=115 's', action=UNIX_CLI_PARSE_ACTION_NOMATCH) at 
/home/vpp/17.07_x64/vpp/build-data/../src/vlib/unix/cli.c:2065
#2  0x77965911 in unix_cli_line_edit (cm=0x77ba6d80 
, um=0x77ba77e0 , cf=0x7fffb5e5bf80)
at /home/vpp/17.07_x64/vpp/build-data/../src/vlib/unix/cli.c:2154
#3  0x77965c49 in unix_cli_process_input (cm=0x77ba6d80 
, cli_file_index=0)
at /home/vpp/17.07_x64/vpp/build-data/../src/vlib/unix/cli.c:2194
#4  0x77966814 in unix_cli_process (vm=0x77ba7080 
, rt=0x7fffb5e5c000, f=0x0)
at /home/vpp/17.07_x64/vpp/build-data/../src/vlib/unix/cli.c:2320
#5  0x77928699 in vlib_process_bootstrap (_a=140736239855696) at 
/home/vpp/17.07_x64/vpp/build-data/../src/vlib/main.c:1275
#6  0x7695fddc in clib_calljmp () at 
/home/vpp/17.07_x64/vpp/build-data/../src/vppinfra/longjmp.S:128
#7  0x7fffb5956820 in ?? ()
#8  0x779287ce in vlib_process_startup (vm=0x7795c5b2 
<clib_mem_size+141>, p=0x7fffb5956880, f=0x8496528d2a6d3500)
at /home/vpp/17.07_x64/vpp/build-data/../src/vlib/main.c:1300
Backtrace stopped: previous frame inner to this frame (corrupt stack?)
(gdb) f 1
#1  0x7796531f in unix_cli_line_process_one (cm=0x77ba6d80 
, um=0x77ba77e0 , cf=0x7fffb5e5bf80, 
uf=0x7fffb5e5bf24, 
input=115 's', action=UNIX_CLI_PARSE_ACTION_NOMATCH) at 
/home/vpp/17.07_x64/vpp/build-data/../src/vlib/unix/cli.c:2065
2065  memmove (cf->current_command + cf->cursor + 1,
(gdb) p cf->current_command 
$36 = (u8 *) 0x7fffb5e5b740 "Ahow interface ipsec-gre "
(gdb) p  cf->cursor
$37 = 15
(gdb) p j
$38 = -15
(gdb) 




Until now I have not figured out the rule that it appears.

 

Thanks,

xyxue




 

From: Luke, Chris

Date: 2017-08-17 04:54

To: 薛欣颖; vpp-dev@lists.fd.io

Subject: RE: [vpp-dev] memmove fault

Can you be more specific about the steps that led up to this issue?

 

I won’t be able to work on it until September (about to go on vacation) but I 
do want to try to capture the details so I can try to recreate it.

 

Chris.

 

From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On 
Behalf Of ???
Sent: Tuesday, August 15, 2017 5:14
To: vpp-dev@lists.fd.io
Subject: [vpp-dev] memmove fault

 

 

Hi,

When I failed to configure a command, then click the up key , there is a 
Segmentation fault(not every time):

Program received signal SIGSEGV, Segmentation fault.
__memmove_ssse3_back () at ../sysdeps/x86

[vpp-dev] Coverity runs

[Luke, Chris]

All,

Coverity have increased the limits for our project size again; effective 
yesterday I run the build twice daily. 0600 and 1500 Eastern is what I have in 
cron currently, which I hope will be useful times for the majority of the 
current contributors to get feedback on their patches once merged. Thoughts on 
the timing welcome.

Chris.
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

[vpp-dev] Jira cleanup, FYI

[Luke, Chris]

All,

As an FYI... I just did a bunch of cleanup in Jira. Closed a lot of issues 
(~100) that were marked Complete but never actually Closed. A significant 
number of these did not have fixed in dates, so for the ones completed in 2017 
I worked out which release they likely would have landed in before closing.

As usual, if any of this was in error, feel free to undo.

Chris.
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] 回复：RE: 回复：RE: plugin compile error

[Luke, Chris]

There’s nothing obvious in these files; I guess I need to see your .am file. It 
would be easier if you could just share your plugin whole, perhaps on github.

Chris.

From: 重新开始 [mailto:15803846...@qq.com]
Sent: Friday, September 15, 2017 12:15
To: Luke, Chris <chris_l...@cable.comcast.com>; vpp-dev <vpp-dev@lists.fd.io>
Subject: 回复：RE: 回复：RE: [vpp-dev] plugin compile error




-- 原始邮件 --
发件人: "Luke, Chris";<chris_l...@comcast.com<mailto:chris_l...@comcast.com>>;
发送时间: 2017年9月16日(星期六) 凌晨0:08
收件人: "重新开始"<15803846...@qq.com<mailto:15803846...@qq.com>>; 
"vpp-dev"<vpp-dev@lists.fd.io<mailto:vpp-dev@lists.fd.io>>;
主题: RE: 回复：RE: [vpp-dev] plugin compile error

Can you show your .api and the generated .json?

Chris.

From: 重新开始 [mailto:15803846...@qq.com]
Sent: Friday, September 15, 2017 11:51
To: Luke, Chris 
<chris_l...@cable.comcast.com<mailto:chris_l...@cable.comcast.com>>; vpp-dev 
<vpp-dev@lists.fd.io<mailto:vpp-dev@lists.fd.io>>
Subject: 回复：RE: [vpp-dev] plugin compile error

Hi, Luke,
   Thank your reply. I have written some apis. The .json file and 
myplugin.api.h file have made  correctly.. Any other problems?


-- 原始邮件 --
发件人: "Luke, Chris";<chris_l...@comcast.com<mailto:chris_l...@comcast.com>>;
发送时间: 2017年9月15日(星期五) 晚上11:11
收件人: "重新开始"<15803846...@qq.com<mailto:15803846...@qq.com>>; 
"vpp-dev"<vpp-dev@lists.fd.io<mailto:vpp-dev@lists.fd.io>>;
主题: RE: [vpp-dev] plugin compile error

It’s complaining about invalid JSON in the .json file; that is built from the 
.api file of the plugin. Check it is valid, or if you have no API at this time, 
remove the .api file from API_FILES in the .am of the plugin.

Chris.

From: vpp-dev-boun...@lists.fd.io<mailto:vpp-dev-boun...@lists.fd.io> 
[mailto:vpp-dev-boun...@lists.fd.io] On Behalf Of 
Sent: Friday, September 15, 2017 10:46
To: vpp-dev <vpp-dev@lists.fd.io<mailto:vpp-dev@lists.fd.io>>
Subject: [vpp-dev] plugin compile error

Hi, everyone:
   I writed a new plugin. When i make this plugin, all the *.o files have made. 
But in the end, it outputs the contents as follow:
make  all-am
make[1]: Entering directory `/home/plugins/myplugin'
   API
 at line 1ken
(null):1 syntax error
Removing myplugin.api.json
make[1]: *** [myplugin.api.json] Error 1
make[1]: Leaving directory `/home/plugins/myplugin'
make: *** [all] Error 2

I don''t know why? Can anyone help me? THank you!

___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] 回复：RE: plugin compile error

[Luke, Chris]

Can you show your .api and the generated .json?

Chris.

From: 重新开始 [mailto:15803846...@qq.com]
Sent: Friday, September 15, 2017 11:51
To: Luke, Chris <chris_l...@cable.comcast.com>; vpp-dev <vpp-dev@lists.fd.io>
Subject: 回复：RE: [vpp-dev] plugin compile error

Hi, Luke,
   Thank your reply. I have written some apis. The .json file and 
myplugin.api.h file have made  correctly.. Any other problems?


-- 原始邮件 --
发件人: "Luke, Chris";<chris_l...@comcast.com<mailto:chris_l...@comcast.com>>;
发送时间: 2017年9月15日(星期五) 晚上11:11
收件人: "重新开始"<15803846...@qq.com<mailto:15803846...@qq.com>>; 
"vpp-dev"<vpp-dev@lists.fd.io<mailto:vpp-dev@lists.fd.io>>;
主题: RE: [vpp-dev] plugin compile error

It’s complaining about invalid JSON in the .json file; that is built from the 
.api file of the plugin. Check it is valid, or if you have no API at this time, 
remove the .api file from API_FILES in the .am of the plugin.

Chris.

From: vpp-dev-boun...@lists.fd.io<mailto:vpp-dev-boun...@lists.fd.io> 
[mailto:vpp-dev-boun...@lists.fd.io] On Behalf Of 
Sent: Friday, September 15, 2017 10:46
To: vpp-dev <vpp-dev@lists.fd.io<mailto:vpp-dev@lists.fd.io>>
Subject: [vpp-dev] plugin compile error

Hi, everyone:
   I writed a new plugin. When i make this plugin, all the *.o files have made. 
But in the end, it outputs the contents as follow:
make  all-am
make[1]: Entering directory `/home/plugins/myplugin'
   API
 at line 1ken
(null):1 syntax error
Removing myplugin.api.json
make[1]: *** [myplugin.api.json] Error 1
make[1]: Leaving directory `/home/plugins/myplugin'
make: *** [all] Error 2

I don''t know why? Can anyone help me? THank you!

___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] plugin compile error

[Luke, Chris]

It’s complaining about invalid JSON in the .json file; that is built from the 
.api file of the plugin. Check it is valid, or if you have no API at this time, 
remove the .api file from API_FILES in the .am of the plugin.

Chris.

From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On 
Behalf Of 
Sent: Friday, September 15, 2017 10:46
To: vpp-dev 
Subject: [vpp-dev] plugin compile error

Hi, everyone:
   I writed a new plugin. When i make this plugin, all the *.o files have made. 
But in the end, it outputs the contents as follow:
make  all-am
make[1]: Entering directory `/home/plugins/myplugin'
   API
 at line 1ken
(null):1 syntax error
Removing myplugin.api.json
make[1]: *** [myplugin.api.json] Error 1
make[1]: Leaving directory `/home/plugins/myplugin'
make: *** [all] Error 2

I don''t know why? Can anyone help me? THank you!

___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] VPP contribute

[Luke, Chris]

Gerrit definitely has a valid SSL cert. Are you at a site that intercepts HTTPS 
traffic?

Chris.

From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On 
Behalf Of Shachar Beiser
Sent: Tuesday, September 12, 2017 1:25
To: Dave Barach (dbarach) ; vpp-dev@lists.fd.io
Cc: Shahaf Shuler ; Damjan Marion (damarion) 

Subject: Re: [vpp-dev] VPP contribute

Hi Dave,

   Is there a simple solution to the “hooks/commit-msg” I have ?
 -Shachar Beiser.

[shacharbe@pegasus08 vpp]$ git review
Using global/system git-review config files (/etc/git-review/git-review.conf) 
is deprecated
/usr/lib/python2.7/site-packages/urllib3/connectionpool.py:858: 
InsecureRequestWarning: Unverified HTTPS request is being made. Adding 
certificate verification is strongly advised. See: 
https://urllib3.readthedocs.io/en/latest/advanced-usage.html#ssl-warnings
  InsecureRequestWarning)
Problems encountered installing commit-msg hook
The following command failed with exit code 104
"GET https://shacha...@gerrit.fd.io/tools/hooks/commit-msg;
---



Error 404 


HTTP ERROR: 404
Problem accessing /tools/hooks/commit-msg. Reason:
Not Found
Powered by Jetty://



From: Dave Barach (dbarach) [mailto:dbar...@cisco.com]
Sent: Monday, September 11, 2017 2:57 PM
To: Shachar Beiser >; 
vpp-dev@lists.fd.io
Cc: Damjan Marion (damarion) >
Subject: RE: VPP contribute

That’s right, no need to send patches to a mailing list. In fact, please don’t 
send patches to this list. ()...

Thanks… Dave

From: vpp-dev-boun...@lists.fd.io 
[mailto:vpp-dev-boun...@lists.fd.io] On Behalf Of Shachar Beiser
Sent: Monday, September 11, 2017 7:48 AM
To: vpp-dev@lists.fd.io
Cc: Damjan Marion (damarion) >
Subject: [vpp-dev] VPP contribute

Hi ,

   I contribute to the VPP for the first time.
   I am following the instructions in your web-site : 
https://wiki.fd.io/view/VPP/Pulling,_Building,_Running,_Hacking_and_Pushing_VPP_Code#Setting_up_Gerrit
   Is that it ? don’t I need to send my patches to the mailing-list ?

   -Shachar Beiser.

___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] u32 vs uint32_t

[Luke, Chris]

Thanks.

To be honest I would prefer using the standard type, but I also have a much 
stronger preference for consistency.

Chris.

From: Neale Ranns (nranns) [mailto:nra...@cisco.com]
Sent: Monday, September 11, 2017 1:18 PM
To: Dave Barach (dbarach) <dbar...@cisco.com>; Dave Wallace 
<dwallac...@gmail.com>; Florin Coras <fcoras.li...@gmail.com>; Luke, Chris 
<chris_l...@cable.comcast.com>
Cc: vpp-dev <vpp-dev@lists.fd.io>
Subject: Re: [vpp-dev] u32 vs uint32_t

+1. I’ll patch the uses of uin32_t.

/neale

From: <vpp-dev-boun...@lists.fd.io<mailto:vpp-dev-boun...@lists.fd.io>> on 
behalf of "Dave Barach (dbarach)" <dbar...@cisco.com<mailto:dbar...@cisco.com>>
Date: Monday, 11 September 2017 at 18:59
To: Dave Wallace <dwallac...@gmail.com<mailto:dwallac...@gmail.com>>, Florin 
Coras <fcoras.li...@gmail.com<mailto:fcoras.li...@gmail.com>>, "Luke, Chris" 
<chris_l...@comcast.com<mailto:chris_l...@comcast.com>>
Cc: vpp-dev <vpp-dev@lists.fd.io<mailto:vpp-dev@lists.fd.io>>
Subject: Re: [vpp-dev] u32 vs uint32_t

+1, let’s stick with u32... Thanks… Dave

From: vpp-dev-boun...@lists.fd.io<mailto:vpp-dev-boun...@lists.fd.io> 
[mailto:vpp-dev-boun...@lists.fd.io] On Behalf Of Dave Wallace
Sent: Monday, September 11, 2017 12:36 PM
To: Florin Coras <fcoras.li...@gmail.com<mailto:fcoras.li...@gmail.com>>; Luke, 
Chris <chris_l...@comcast.com<mailto:chris_l...@comcast.com>>
Cc: vpp-dev <vpp-dev@lists.fd.io<mailto:vpp-dev@lists.fd.io>>
Subject: Re: [vpp-dev] u32 vs uint32_t

+1
On 09/11/2017 11:27 AM, Florin Coras wrote:
Hi Chris,

Personally, I’d like to enforce the use of u32. Is it an option to just replace 
all occurrences of uint32_t in ip.h/mpls.h?

Thanks,
Florin

On Sep 11, 2017, at 7:55 AM, Luke, Chris 
<chris_l...@comcast.com<mailto:chris_l...@comcast.com>> wrote:

For discussion: VPP has traditionally used its own fixed-width types, such as 
u32 and u64 and only uses standard types when referring to the external world 
(eg, to talk to libc, etc). Recently I’ve noticed the C99 variant, uint32_t 
creeping in more and into VPP internal matters. As a matter of style and 
consistency, which should we as a project be using?

Reason I ask: The recent MPLS patch (https://gerrit.fd.io/r/#/c/8371) uses both 
styles in .h files but doesn’t have stdint.h included in any path leading to 
those .h’s; Coverity appears to be fussy about this – it checks that all types 
used in a .h are defined in the scope of that .h. Upshot is that Coverity is 
balking at this and only 54% of the project now compiles under Coverity

To resolve the issue with Coverity, I am torn with adding “#include ” 
to ip.h/mpls.h to fix it where it happens, or just accept that humans are 
inconsistent and add it to vppinfra/types.h. Thoughts?

Chris.

___
vpp-dev mailing list
vpp-dev@lists.fd.io<mailto:vpp-dev@lists.fd.io>
https://lists.fd.io/mailman/listinfo/vpp-dev





___

vpp-dev mailing list

vpp-dev@lists.fd.io<mailto:vpp-dev@lists.fd.io>

https://lists.fd.io/mailman/listinfo/vpp-dev

___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

[vpp-dev] u32 vs uint32_t

[Luke, Chris]

For discussion: VPP has traditionally used its own fixed-width types, such as 
u32 and u64 and only uses standard types when referring to the external world 
(eg, to talk to libc, etc). Recently I've noticed the C99 variant, uint32_t 
creeping in more and into VPP internal matters. As a matter of style and 
consistency, which should we as a project be using?

Reason I ask: The recent MPLS patch (https://gerrit.fd.io/r/#/c/8371) uses both 
styles in .h files but doesn't have stdint.h included in any path leading to 
those .h's; Coverity appears to be fussy about this - it checks that all types 
used in a .h are defined in the scope of that .h. Upshot is that Coverity is 
balking at this and only 54% of the project now compiles under Coverity

To resolve the issue with Coverity, I am torn with adding "#include " 
to ip.h/mpls.h to fix it where it happens, or just accept that humans are 
inconsistent and add it to vppinfra/types.h. Thoughts?

Chris.

___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] vpp graph dump

[Luke, Chris]

Eyal,

I didn't release that code because it was embedded into VPP and fragile; I had 
intended to rewrite it to make use of the API and never got round to it.

As Ole mentioned the API should now have all the required data; if you can wait 
until I return from vacation (read: remind me in September so I don't forget) I 
may have a stab at a small standalone utility using the API to generate the 
.dot and ultimately the .svg as I did before. There were many suggestions for 
adding things like runtime statistics to the edges etc which are still on the 
wishlist.

But if it's just the packet path, again as Ole mentions, "show vlib graph" is 
>90% of what you likely need.

Chris.

From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On 
Behalf Of Eyal Lavee
Sent: Tuesday, August 15, 2017 8:23
To: vpp-dev@lists.fd.io
Subject: [vpp-dev] vpp graph dump


Is there any method to dump the vpp node graph?
I'm looking to understand the supported feature path(s) without needing to 
reverse engineer from the code.

I have seen a previous post from mid 2016 entitled "[vpp-dev] Node graph 
visualization" on such a potential utility, but there do not seem to be any 
follow-ups to this.

Regards,
Eyal.

___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] memmove fault

[Luke, Chris]

Can you be more specific about the steps that led up to this issue?

I won’t be able to work on it until September (about to go on vacation) but I 
do want to try to capture the details so I can try to recreate it.

Chris.

From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On 
Behalf Of ???
Sent: Tuesday, August 15, 2017 5:14
To: vpp-dev@lists.fd.io
Subject: [vpp-dev] memmove fault


Hi,

When I failed to configure a command, then click the up key , there is a 
Segmentation fault(not every time):

Program received signal SIGSEGV, Segmentation fault.
__memmove_ssse3_back () at ../sysdeps/x86_64/multiarch/memcpy-ssse3-back.S:1664
1664../sysdeps/x86_64/multiarch/memcpy-ssse3-back.S: No such file or 
directory.
(gdb) bt
#0  __memmove_ssse3_back () at 
../sysdeps/x86_64/multiarch/memcpy-ssse3-back.S:1664
#1  0x77966f56 in unix_cli_line_process_one (cm=0x77ba4960 
,
um=0x77ba7dc0 , cf=0x7fffb5de5b3c, uf=0x7fffb5de5ae0, 
input=102 'f',
action=UNIX_CLI_PARSE_ACTION_NOMATCH) at 
/home/vpp/17.07_x64/vpp/build-data/../src/vlib/unix/cli.c:2063
#2  0x77967548 in unix_cli_line_edit (cm=0x77ba4960 
, um=0x77ba7dc0 ,
cf=0x7fffb5de5b3c) at 
/home/vpp/17.07_x64/vpp/build-data/../src/vlib/unix/cli.c:2152
#3  0x77967880 in unix_cli_process_input (cm=0x77ba4960 
, cli_file_index=0)
at /home/vpp/17.07_x64/vpp/build-data/../src/vlib/unix/cli.c:2192
#4  0x7796844b in unix_cli_process (vm=0x77ba7560 
, rt=0x7fffb5e7, f=0x0)
at /home/vpp/17.07_x64/vpp/build-data/../src/vlib/unix/cli.c:2318
#5  0x7792a320 in vlib_process_bootstrap (_a=140736239921232)
at /home/vpp/17.07_x64/vpp/build-data/../src/vlib/main.c:1274
#6  0x7696fd4c in clib_calljmp () at 
/home/vpp/17.07_x64/vpp/build-data/../src/vppinfra/longjmp.S:128
#7  0x7fffb5966820 in ?? ()
#8  0x7792a455 in vlib_process_startup (vm=0x7795e1e9 
, p=0x7fffb5966880,
f=0xedcb4a35d968b00) at 
/home/vpp/17.07_x64/vpp/build-data/../src/vlib/main.c:1299
Backtrace stopped: previous frame inner to this frame (corrupt stack?)

How should we solve this problem?

Thanks,
xyxue

___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] [csit-dev] API Change: Dedicated SW interface Event

[Luke, Chris]

Yeah, I suspect the API was simple enough back at the beginning that it just 
made sense to do it that way. This message, and presumably others, suffer from 
legacy cruft.

Assuming the downstream consumers are okay with it, I fully support blowing out 
the cruft.

Chris.

> -Original Message-
> From: Neale Ranns (nranns) [mailto:nra...@cisco.com]
> Sent: Wednesday, August 9, 2017 13:38
> To: Luke, Chris <chris_l...@cable.comcast.com>; vpp-dev@lists.fd.io; csit-
> d...@lists.fd.io; honeycomb-...@lists.fd.io
> Subject: Re: [csit-dev] API Change: Dedicated SW interface Event
> 
> 
> Hi Chris,
> 
> I don’t know the history. Convenience probably. In the absence of our
> attempt at auto-generating/auto-detecting event-notify pairs, the message
> re-use is understandable. I’m just trying to avoid the special cases in those
> generators (like-wise with the recent ACL dump addition).
> 
> I’ll give it till the end of the week, then press the button if there are no
> objections.
> 
> Thanks,
> neale
> 
> -Original Message-
> From: "Luke, Chris" <chris_l...@comcast.com>
> Date: Wednesday, 9 August 2017 at 14:25
> To: "Neale Ranns (nranns)" <nra...@cisco.com>, "vpp-dev@lists.fd.io"
> <vpp-dev@lists.fd.io>, "csit-...@lists.fd.io" <csit-...@lists.fd.io>,
> "honeycomb-...@lists.fd.io" <honeycomb-...@lists.fd.io>
> Subject: RE: [csit-dev] API Change: Dedicated SW interface Event
> 
> No specific objection, though I don't think I understand why it was done
> this way in the first place. Laziness, perhaps?
> 
> Chris.
> 
> > -Original Message-
> > From: csit-dev-boun...@lists.fd.io [mailto:csit-dev-boun...@lists.fd.io]
> On
> > Behalf Of Neale Ranns (nranns)
> > Sent: Wednesday, August 9, 2017 8:51
> > To: vpp-dev@lists.fd.io; csit-...@lists.fd.io; honeycomb-...@lists.fd.io
> > Subject: Re: [csit-dev] API Change: Dedicated SW interface Event
> >
> >
> > Hi All,
> >
> > Any objections or support for this proposal?
> >
> > Thanks,
> > neale
> >
> > -Original Message-
> > From: <csit-dev-boun...@lists.fd.io> on behalf of "Neale Ranns
> (nranns)"
> > <nra...@cisco.com>
> > Date: Monday, 7 August 2017 at 16:02
> > To: "vpp-dev@lists.fd.io" <vpp-dev@lists.fd.io>, "csit-...@lists.fd.io"
>  > d...@lists.fd.io>, "honeycomb-...@lists.fd.io"  > d...@lists.fd.io>
> > Subject: [csit-dev] API Change: Dedicated SW interface Event
> >
> >
> > Hi All,
> >
> > I would like to propose the addition of a dedicated SW interface 
> event
> > message type rather than overload the set flags request. The over-
> loading of
> > types causes problems for the automatic API generation tools.
> >
> > https://gerrit.fd.io/r/#/c/7925/
> >
> > regards,
> > neale
> >
> >
> > ___
> > csit-dev mailing list
> > csit-...@lists.fd.io
> > https://lists.fd.io/mailman/listinfo/csit-dev
> >
> >
> > ___
> > csit-dev mailing list
> > csit-...@lists.fd.io
> > https://lists.fd.io/mailman/listinfo/csit-dev
> 
> 

___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] [csit-dev] "vpp-make-test-docs-verify-master" job failure

[Luke, Chris]

I'm not making any request; I'm merely positing ways forward to avoid the below 
issue, assuming this is in fact what the issue is.

Chris.

> -Original Message-
> From: Klement Sekera -X (ksekera - PANTHEON TECHNOLOGIES at Cisco)
> [mailto:ksek...@cisco.com]
> Sent: Tuesday, August 08, 2017 11:47 AM
> To: Dave Barach (dbarach) <dbar...@cisco.com>; Luke, Chris
> <chris_l...@cable.comcast.com>; csit-...@lists.fd.io
> Cc: vpp-dev@lists.fd.io
> Subject: RE: [csit-dev] [vpp-dev] "vpp-make-test-docs-verify-master" job
> failure
> 
> Are you suggesting we put all the dependent python packages as part of the
> vpp source code tree then?
> Or is this request aimed at the test box maintainers?
> 
> Thanks,
> Klement
> 
> Quoting Luke, Chris (2017-08-08 17:04:57)
> > Sure, I know what pip is.
> >
> > My contention is that virtualenv should not be going to the network; in the
> old days it would dip into the system packages for anything the base venv
> needed. It's a really poor and insecure assumption that unfettered internet
> access is universally available. In this case, I suspect wherever the job runs
> needs an HTTP proxy to fit that assumption.
> >
> > So either pre-stage the packages you need, and tell pip where to find
> > them, or provide a proxy. :)
> >
> > Chris.
> >
> >
> > > -Original Message-
> > > From: Klement Sekera -X (ksekera - PANTHEON TECHNOLOGIES at Cisco)
> > > [mailto:ksek...@cisco.com]
> > > Sent: Tuesday, August 08, 2017 10:51 AM
> > > To: Dave Barach (dbarach) <dbar...@cisco.com>; Luke, Chris
> > > <chris_l...@cable.comcast.com>; csit-...@lists.fd.io
> > > Cc: vpp-dev@lists.fd.io
> > > Subject: RE: [csit-dev] [vpp-dev] "vpp-make-test-docs-verify-master"
> > > job failure
> > >
> > > Think of pip (used by virtualenv) like apt-get.  Python maintainers
> > > are innocent in this case. When adding the virtualenv feature to
> > > test framework, it never occured to me that somebody might be doing
> > > vpp development on an offline machine. Laptop which was online and
> > > later went offline doesn't count, because virtualenv uses cached
> > > versions for subsequent installations afaik.
> > >
> > > If this is a requirement, we'll need to think of a way to ship the
> > > python packages which virtualenv requires - e.g. setuptools - ourselves.
> > > But if we do that, we also need to have all the other packages which
> > > the test framework uses (e.g. scapy) somewhere in-tree(?).
> > >
> > > The packages currently used by test framework (apart from the
> > > implicit
> > > requirements) are:
> > >
> > > scapy==2.3.3 pexpect subprocess32 cffi
> > > git+https://github.com/klement/py-lispnetworking@setup
> > >
> > > the last one is a fork of py-lispnetworking, which is used by some
> > > LISP tests. I forked it and added an installation script, which was
> > > missing in the original repo so that we can install it in the same way as
> other packages.
> > >
> > > I have a strong feeling that this isn't something which we want to do...
> > >
> > > Klement
> > >
> > > Quoting Luke, Chris (2017-08-08 16:31:31)
> > > > I've seen precisely this issue with Python's virtualenv whenever
> > > > the host
> > > doesn't have internet access while the venv is being created; I work
> > > around it using an HTTP proxy, though requiring internet access just
> > > to create a venv seems like a particularly braindead decision by the
> Python maintainers.
> > > >
> > > > Chris.
> > > >
> > > > > -Original Message-
> > > > > From: csit-dev-boun...@lists.fd.io
> > > > > [mailto:csit-dev-boun...@lists.fd.io] On Behalf Of Klement
> > > > > Sekera -X (ksekera - PANTHEON TECHNOLOGIES at Cisco)
> > > > > Sent: Tuesday, August 08, 2017 8:23 AM
> > > > > To: Dave Barach (dbarach) <dbar...@cisco.com>;
> > > > > csit-...@lists.fd.io
> > > > > Cc: vpp-dev@lists.fd.io
> > > > > Subject: Re: [csit-dev] [vpp-dev] "vpp-make-test-docs-verify-master"
> > > > > job failure
> > > > >
> > > > > Looks to me like a bug in the urllib3 python library while
> > > > > reporting some kind of connection failure.. never seen it before..
> > > > >
> > > > > Klement
> 

Re: [vpp-dev] [csit-dev] "vpp-make-test-docs-verify-master" job failure

[Luke, Chris]

Sure, I know what pip is.

My contention is that virtualenv should not be going to the network; in the old 
days it would dip into the system packages for anything the base venv needed. 
It's a really poor and insecure assumption that unfettered internet access is 
universally available. In this case, I suspect wherever the job runs needs an 
HTTP proxy to fit that assumption.

So either pre-stage the packages you need, and tell pip where to find them, or 
provide a proxy. :)

Chris.


> -Original Message-
> From: Klement Sekera -X (ksekera - PANTHEON TECHNOLOGIES at Cisco)
> [mailto:ksek...@cisco.com]
> Sent: Tuesday, August 08, 2017 10:51 AM
> To: Dave Barach (dbarach) <dbar...@cisco.com>; Luke, Chris
> <chris_l...@cable.comcast.com>; csit-...@lists.fd.io
> Cc: vpp-dev@lists.fd.io
> Subject: RE: [csit-dev] [vpp-dev] "vpp-make-test-docs-verify-master" job
> failure
> 
> Think of pip (used by virtualenv) like apt-get.  Python maintainers are
> innocent in this case. When adding the virtualenv feature to test framework,
> it never occured to me that somebody might be doing vpp development on
> an offline machine. Laptop which was online and later went offline doesn't
> count, because virtualenv uses cached versions for subsequent installations
> afaik.
> 
> If this is a requirement, we'll need to think of a way to ship the python
> packages which virtualenv requires - e.g. setuptools - ourselves.
> But if we do that, we also need to have all the other packages which the test
> framework uses (e.g. scapy) somewhere in-tree(?).
> 
> The packages currently used by test framework (apart from the implicit
> requirements) are:
> 
> scapy==2.3.3 pexpect subprocess32 cffi
> git+https://github.com/klement/py-lispnetworking@setup
> 
> the last one is a fork of py-lispnetworking, which is used by some LISP 
> tests. I
> forked it and added an installation script, which was missing in the original
> repo so that we can install it in the same way as other packages.
> 
> I have a strong feeling that this isn't something which we want to do...
> 
> Klement
> 
> Quoting Luke, Chris (2017-08-08 16:31:31)
> > I've seen precisely this issue with Python's virtualenv whenever the host
> doesn't have internet access while the venv is being created; I work around it
> using an HTTP proxy, though requiring internet access just to create a venv
> seems like a particularly braindead decision by the Python maintainers.
> >
> > Chris.
> >
> > > -Original Message-
> > > From: csit-dev-boun...@lists.fd.io
> > > [mailto:csit-dev-boun...@lists.fd.io] On Behalf Of Klement Sekera -X
> > > (ksekera - PANTHEON TECHNOLOGIES at Cisco)
> > > Sent: Tuesday, August 08, 2017 8:23 AM
> > > To: Dave Barach (dbarach) <dbar...@cisco.com>; csit-...@lists.fd.io
> > > Cc: vpp-dev@lists.fd.io
> > > Subject: Re: [csit-dev] [vpp-dev] "vpp-make-test-docs-verify-master"
> > > job failure
> > >
> > > Looks to me like a bug in the urllib3 python library while reporting
> > > some kind of connection failure.. never seen it before..
> > >
> > > Klement
> > >
> > > Quoting Dave Barach (dbarach) (2017-08-08 14:05:16)
> > > >Please see [1]https://gerrit.fd.io/r/#/c/7885,
> > > >[2]https://jenkins.fd.io/job/vpp-make-test-docs-verify-
> > > master/2814/console.
> > > >
> > > >
> > > >
> > > >Any idea what this is all about?
> > > >
> > > >
> > > >
> > > >Thanks… Dave
> > > >
> > > >
> > > >
> > > > References
> > > >
> > > >Visible links
> > > >1. https://gerrit.fd.io/r/#/c/7885
> > > >2.
> > > > https://jenkins.fd.io/job/vpp-make-test-docs-verify-master/2814/co
> > > > nsol
> > > > e
> > > ___
> > > csit-dev mailing list
> > > csit-...@lists.fd.io
> > > https://lists.fd.io/mailman/listinfo/csit-dev
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] [csit-dev] "vpp-make-test-docs-verify-master" job failure

[Luke, Chris]

I've seen precisely this issue with Python's virtualenv whenever the host 
doesn't have internet access while the venv is being created; I work around it 
using an HTTP proxy, though requiring internet access just to create a venv 
seems like a particularly braindead decision by the Python maintainers.

Chris.

> -Original Message-
> From: csit-dev-boun...@lists.fd.io [mailto:csit-dev-boun...@lists.fd.io] On
> Behalf Of Klement Sekera -X (ksekera - PANTHEON TECHNOLOGIES at Cisco)
> Sent: Tuesday, August 08, 2017 8:23 AM
> To: Dave Barach (dbarach) ; csit-...@lists.fd.io
> Cc: vpp-dev@lists.fd.io
> Subject: Re: [csit-dev] [vpp-dev] "vpp-make-test-docs-verify-master" job
> failure
> 
> Looks to me like a bug in the urllib3 python library while reporting some kind
> of connection failure.. never seen it before..
> 
> Klement
> 
> Quoting Dave Barach (dbarach) (2017-08-08 14:05:16)
> >Please see [1]https://gerrit.fd.io/r/#/c/7885,
> >[2]https://jenkins.fd.io/job/vpp-make-test-docs-verify-
> master/2814/console.
> >
> >
> >
> >Any idea what this is all about?
> >
> >
> >
> >Thanks… Dave
> >
> >
> >
> > References
> >
> >Visible links
> >1. https://gerrit.fd.io/r/#/c/7885
> >2.
> > https://jenkins.fd.io/job/vpp-make-test-docs-verify-master/2814/consol
> > e
> ___
> csit-dev mailing list
> csit-...@lists.fd.io
> https://lists.fd.io/mailman/listinfo/csit-dev
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] API Change Proposal: explicit FIB table create and delete

[Luke, Chris]

+1

Do you intend to block fib deletion until nothing uses it, or flush those 
things at deletion?

Chris.

> -Original Message-
> From: csit-dev-boun...@lists.fd.io [mailto:csit-dev-boun...@lists.fd.io] On
> Behalf Of Neale Ranns (nranns)
> Sent: Thursday, August 3, 2017 3:57
> To: vpp-dev@lists.fd.io; csit-...@lists.fd.io; honeycomb-...@lists.fd.io
> Subject: [csit-dev] API Change Proposal: explicit FIB table create and delete
> 
> 
> Dear All,
> 
> I would like to propose the addition of a new API to explicitly create and
> delete FIB tables. At present the only way to create FIB tables (for e.g. 
> VRFs)
> is to:
> 1) Bind an interface to a new table index; ‘set int ip table Eth0  TABLE_ID>
> 2) Add a route in a new table and set the create_vrf_if_needed flag
> 
> With the addition of an explicit create we have the possibility to set 
> per-table
> properties, like the flow-hash and (potentially) the mtrie stride (to favour
> memory over performance for small VRFs). With an explicit delete VPP is
> aware when it is safe to delete the table.
> 
> An explicit API makes the management of FIB tables by the agent/client the
> same as managing any other table resource, like Bridge-Domains or classify
> tables.
> 
> Regards,
> neale
> 
> ___
> csit-dev mailing list
> csit-...@lists.fd.io
> https://lists.fd.io/mailman/listinfo/csit-dev
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] Merge job failing

[Luke, Chris]

One failed because a test didn’t receive packets on pg0; possibly a fluke

 

Two failed because:

 

16:15:11 Using https://packagecloud.io with token:**

16:15:11 Looking for repository at fdio/master... failed!

16:15:11 Build step 'Execute shell' marked build as failure

 

I suspect this last is the real issue; don’t we normally use the name of the 
next release for this sort of thing, rather than ‘master’?

 

Chris.

 

From: "Jan Srnicek -X (jsrnicek - PANTHEON TECHNOLOGIES at Cisco)" 
<jsrni...@cisco.com>
Date: Tuesday, August 1, 2017 at 07:16
To: Chris Luke <chris_l...@cable.comcast.com>, vpp-dev <vpp-dev@lists.fd.io>
Cc: "Peter Lapos -X (plapos - PANTHEON TECHNOLOGIES at Cisco)" 
<pla...@cisco.com>, "Samuel Elias -X (samelias - PANTHEON TECHNOLOGIES at 
Cisco)" <samel...@cisco.com>
Subject: RE: [vpp-dev] Merge job failing

 

This is the first run that failed

 

https://jenkins.fd.io/job/vpp-merge-master-ubuntu1604/2628/

 

 
Jan SrnicekEngineer - Softwarejsrnicek@cisco.comTel: Cisco Systems, Inc.


Slovakia
cisco.com

 

Think before you print.
This email may contain confidential and privileged material for the sole use of 
the intended recipient. Any review, use, distribution or disclosure by others 
is strictly prohibited. If you are not the intended recipient (or authorized to 
receive for the recipient), please contact the sender by reply email and delete 
all copies of this message.Please click here for Company Registration 
Information.
 

From: Luke, Chris [mailto:chris_l...@comcast.com] 
Sent: Tuesday, August 1, 2017 3:10 PM
To: Jan Srnicek -X (jsrnicek - PANTHEON TECHNOLOGIES at Cisco) 
<jsrni...@cisco.com>; vpp-dev <vpp-dev@lists.fd.io>
Cc: Peter Lapos -X (plapos - PANTHEON TECHNOLOGIES at Cisco) 
<pla...@cisco.com>; Samuel Elias -X (samelias - PANTHEON TECHNOLOGIES at Cisco) 
<samel...@cisco.com>
Subject: Re: [vpp-dev] Merge job failing

 

When did that start? We re-instated the hook that builds docs after the Ubuntu 
merge job finishes; possibly related?

 

It seems to work fine on the stable branch.

 

Chris

 

From: <vpp-dev-boun...@lists.fd.io> on behalf of "Jan Srnicek -X (jsrnicek - 
PANTHEON TECHNOLOGIES at Cisco)" <jsrni...@cisco.com>
Date: Tuesday, August 1, 2017 at 04:36
To: vpp-dev <vpp-dev@lists.fd.io>
Cc: "Peter Lapos -X (plapos - PANTHEON TECHNOLOGIES at Cisco)" 
<pla...@cisco.com>, "Samuel Elias -X (samelias - PANTHEON TECHNOLOGIES at 
Cisco)" <samel...@cisco.com>
Subject: [vpp-dev] Merge job failing

 

Hi everyone

 

Can somebody please look at vpp-merge jobs ? 
(https://jenkins.fd.io/job/vpp-merge-master-ubuntu1604/ , 
https://jenkins.fd.io/job/vpp-merge-master-centos7/)

They failed on last 8 occasions, which also translates to honeycomb integration 
jobs not beeing triggered which prevents deb/rpm packages to be published 
correctly.

 

 
Jan SrnicekEngineer - Softwarejsrnicek@cisco.comTel: Cisco Systems, Inc.


Slovakia
cisco.com

 

Think before you print.
This email may contain confidential and privileged material for the sole use of 
the intended recipient. Any review, use, distribution or disclosure by others 
is strictly prohibited. If you are not the intended recipient (or authorized to 
receive for the recipient), please contact the sender by reply email and delete 
all copies of this message.Please click here for Company Registration 
Information.

 



smime.p7s
Description: S/MIME cryptographic signature
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] Merge job failing

[Luke, Chris]

When did that start? We re-instated the hook that builds docs after the Ubuntu 
merge job finishes; possibly related?

 

It seems to work fine on the stable branch.

 

Chris

 

From:  on behalf of "Jan Srnicek -X (jsrnicek - 
PANTHEON TECHNOLOGIES at Cisco)" 
Date: Tuesday, August 1, 2017 at 04:36
To: vpp-dev 
Cc: "Peter Lapos -X (plapos - PANTHEON TECHNOLOGIES at Cisco)" 
, "Samuel Elias -X (samelias - PANTHEON TECHNOLOGIES at 
Cisco)" 
Subject: [vpp-dev] Merge job failing

 

Hi everyone

 

Can somebody please look at vpp-merge jobs ? 
(https://jenkins.fd.io/job/vpp-merge-master-ubuntu1604/ , 
https://jenkins.fd.io/job/vpp-merge-master-centos7/)

They failed on last 8 occasions, which also translates to honeycomb integration 
jobs not beeing triggered which prevents deb/rpm packages to be published 
correctly.

 

 
Jan SrnicekEngineer - Softwarejsrnicek@cisco.comTel: Cisco Systems, Inc.


Slovakia
cisco.com

 

Think before you print.
This email may contain confidential and privileged material for the sole use of 
the intended recipient. Any review, use, distribution or disclosure by others 
is strictly prohibited. If you are not the intended recipient (or authorized to 
receive for the recipient), please contact the sender by reply email and delete 
all copies of this message.Please click here for Company Registration 
Information.

 



smime.p7s
Description: S/MIME cryptographic signature
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] 17.07 Release

[Luke, Chris]

The next merge job to run on each branch will trigger it; or at least I hope it 
does.

I’ll do a ‘remerge’ on the current HEAD commit to see if that will do the 
needful

Chris.


On 7/31/17, 10:34, "vpp-dev-boun...@lists.fd.io on behalf of Neale Ranns 
(nranns)"  wrote:

Hi Ray,

The release notes will appear here eventually:
 https://docs.fd.io/vpp/17.07/release_notes.html

there was a breakage in the generation of the docs, which Chris fixed, and 
was recently merged:
  https://gerrit.fd.io/r/#/c/7818/

hopefully we will get the docs updated when the next patched is merged.

Regards,
neale

-Original Message-
From:  on behalf of "Kinsella, Ray" 

Date: Monday, 31 July 2017 at 15:42
To: "vpp-dev@lists.fd.io" 
Subject: Re: [vpp-dev] 17.07 Release

Hi Neale,

Thanks for this - great work.
Are there release notes archived anywhere?

Ray K

On 20/07/2017 16:56, Neale Ranns (nranns) wrote:
>
> Dear VPP community,
>
> The VPP 17.07 release is complete. The release artefacts are now 
available on the nexus server.
>
> I’d like to take this opportunity to thank you all for your continued 
support for VPP.
>
> Best regards,
> Neale
>
>
> ___
> vpp-dev mailing list
> vpp-dev@lists.fd.io
> https://lists.fd.io/mailman/listinfo/vpp-dev
>
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev


smime.p7s
Description: S/MIME cryptographic signature
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] Capturing Packets with Particular Ethertypes

[Luke, Chris]

Anyone can edit the wiki, hint hint :)

Chris.

From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On 
Behalf Of Alessio Silvestro
Sent: Friday, July 28, 2017 14:13
To: John Lo (loj) 
Cc: vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] Capturing Packets with Particular Ethertypes

Thanks, that was the issue.

It would be nice to have such information in the wiki page.

It would help people to work with VPP :)

Alessio

On Thu, Jul 27, 2017 at 8:58 PM, John Lo (loj) 
> wrote:
Hi Alessio,

The mechanism you are using to handle ethertype works only when the interface 
is in L3 mode which is the default, unless an interface is set to L2 bridging 
(or xconnect) mode. When an interface is in L2 mode, VPP will always get into 
l2-input mode to forward ethernet packet based on ethernet header and not care 
about ethertype of the packet. From your description, the interface appear to 
be in L2 mode.

Regards,
John

From: vpp-dev-boun...@lists.fd.io 
[mailto:vpp-dev-boun...@lists.fd.io] On 
Behalf Of Alessio Silvestro
Sent: Thursday, July 27, 2017 12:16 PM
To: vpp-dev@lists.fd.io
Subject: [vpp-dev] Capturing Packets with Particular Ethertypes

Dear all,

I am trying to capture packets with a particular Ethertype.

Let's say I want the ethertype 0x2323.

I first define the new protocol type in vpp/srv/vnet/ethernet/types.def

ethernet_type (0x2323, MY_PROTOCOL)
Thus, I created and registered a new node "my_node".

In the init function of my_node I call the function:

ethernet_register_input_type (vm, MY_PROTOCOL ,my_node.index);


I compile and run vpp. When I send the packet with the new ethertype, my node 
is not invoked.

In particular, the result of show trace tells me that the packet is arriving at 
the interface.The new procotol is recognized but the chain of node is 
dpdk-input -> ethernet-input -> l2-input -> l2-output -> 
TenGigabitEthernet7/0/1-output.

The wiki page 
(https://wiki.fd.io/view/VPP/Modifying_The_Packet_Processing_Directed_Graph) 
does not mention anything else.

Do you have an idea where could be the problem or what is missing?

Thanks.

Best regards,
Alessio


___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] What is "pneum_read filed"?

[Luke, Chris]

Suspect it’s a typographical error; read it as “failed”.

Do you open the API connection per thread? I suspect you will need to. It’s 
based on shared memory that may not survive thread spawning in some threading 
models in Python.

Chris

From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On 
Behalf Of Weitao Han
Sent: Monday, July 24, 2017 20:29
To: vpp-dev@lists.fd.io
Subject: [vpp-dev] What is "pneum_read filed"?

When I use multithreads(python threading) to send msg to vpp, it raises 
"IOError - pneum_read filed".

In vpp_papi.py

rv = vpp_api.pneum_read(mem, size, self.read_timeout)
if rv:
raise IOError(rv, 'pneum_read filed')

What does IOError - pneum_read filed mean?


___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] 17.07 Release

[Luke, Chris]

Woohoo!

> -Original Message-
> From: csit-dev-boun...@lists.fd.io [mailto:csit-dev-boun...@lists.fd.io] On
> Behalf Of Neale Ranns (nranns)
> Sent: Thursday, July 20, 2017 19:57
> To: vpp-dev@lists.fd.io; csit-...@lists.fd.io
> Subject: [csit-dev] 17.07 Release
> 
> 
> Dear VPP community,
> 
> The VPP 17.07 release is complete. The release artefacts are now available on
> the nexus server.
> 
> I’d like to take this opportunity to thank you all for your continued support
> for VPP.
> 
> Best regards,
> Neale
> 
> 
> ___
> csit-dev mailing list
> csit-...@lists.fd.io
> https://lists.fd.io/mailman/listinfo/csit-dev
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] TWS call scheduled for 7/18 8am PDT / 11am EDT / 5pm CEST

[Luke, Chris]

For clarity, which dial in will be used? The thread below references the 
details for both the VPP dev call and the TWS call. My best guess is it’s the 
VPP dev call details.

Chris.


From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On 
Behalf Of Jong Hahn (jonhahn)
Sent: Tuesday, July 18, 2017 3:12 AM
To: vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] TWS call scheduled for 7/18 8am PDT / 11am EDT / 5pm CEST

FYI.  Just resending as a reminder.

From: vpp-dev-boun...@lists.fd.io 
[mailto:vpp-dev-boun...@lists.fd.io] On Behalf Of Ed Warnicke
Sent: Wednesday, July 5, 2017 12:49 PM
To: Dave Barach (dbarach) >
Cc: vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] TWS call scheduled for 7/18 8am PDT / 11am EDT / 5pm CEST

TWS updated here: https://wiki.fd.io/view/TWS and also on the 
fd.io calendar:

https://calendar.google.com/calendar/embed?src=qpen2df76a954fieqdnc3avg0k%40group.calendar.google.com

Ed

On Wed, Jul 5, 2017 at 12:08 PM, Dave Barach (dbarach) 
> wrote:
Eric Ernst and Manohar Castelino will present their vpp integration with 
ClearContainer.

Dial-in info will be added to https://wiki.fd.io/view/VPP/Meeting shortly...

Thanks... Dave

___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] show trace bug in vpp stable 1707

[Luke, Chris]

Hi Andrew,

The trace raises more questions! :)

What is in your startup.conf and parameters on the VPP command line?

It says “out of memory” trying to format a string; I am wondering if you have 
an exceptionally small heap configured.

How long did it take before it crashed?

If you reduce the number of packets to capture the traces of, to something like 
5, does it still crash? Or just take longer to crash?

Thanks,
Chris.

From: Andrew Taylor [mailto:andrew2016tay...@gmail.com]
Sent: Saturday, July 15, 2017 2:38
To: Luke, Chris <chris_l...@cable.comcast.com>
Cc: vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] show trace bug in vpp stable 1707


This is a vpp config :

set int ip address GigabitEthernet0/4/0 
192.168.30.135/24<http://192.168.30.135/24>
set int state GigabitEthernet0/4/0 up
set int ip address GigabitEthernet0/5/0 
192.168.40.135/24<http://192.168.40.135/24>
set int state GigabitEthernet0/5/0 up



trace add dpdk-input 100
show trace

this is a bt output:


#0  0x76395c37 in __GI_raise (sig=sig@entry=6) at 
../nptl/sysdeps/unix/sysv/linux/raise.c:56
#1  0x76399028 in __GI_abort () at abort.c:89
#2  0x00406fd3 in os_panic () at 
/root/vpp-1707/build-data/../src/vpp/vnet/main.c:263
#3  0x76bae5bf in clib_mem_alloc_aligned_at_offset 
(os_out_of_memory_on_failure=1, align_offset=, align=4, 
size=699583872) at /root/vpp-1707/build-data/../src/vppinfra/mem.h:102
#4  vec_resize_allocate_memory (v=, 
length_increment=length_increment@entry=2, data_bytes=, 
header_bytes=, header_bytes@entry=0, 
data_align=data_align@entry=4) at 
/root/vpp-1707/build-data/../src/vppinfra/vec.c:84
#5  0x76b6724c in _vec_resize (data_align=0, header_bytes=0, 
data_bytes=, length_increment=2, v=) at 
/root/vpp-1707/build-data/../src/vppinfra/vec.h:142
#6  format_integer (s=, s@entry=0x7fffca8d1b4c '-' , " Start of thread 0 vpp_main ", '-' , "\nPacket 
1\n\n00:00:37:241764: dpdk-input\n  GigabitEthernet0/4/0 rx queue 0\n  buffer 
0x1ca7: current data 0, length 474, free-list 0, clo"..., number=, options=options@entry=0x7fffb65ce310) at 
/root/vpp-1707/build-data/../src/vppinfra/format.c:535
#7  0x76b67d26 in do_percent (va=0x7fffb65ce398, fmt=, 
_s=) at 
/root/vpp-1707/build-data/../src/vppinfra/format.c:314
#8  va_format (s=0x7fffca8d1b4c '-' , " Start of thread 0 
vpp_main ", '-' , "\nPacket 1\n\n00:00:37:241764: 
dpdk-input\n  GigabitEthernet0/4/0 rx queue 0\n  buffer 0x1ca7: current data 0, 
length 474, free-list 0, clo"..., fmt=, 
va=va@entry=0x7fffb65ce398) at 
/root/vpp-1707/build-data/../src/vppinfra/format.c:404
#9  0x76b67417 in format (s=, fmt=fmt@entry=0x49c67a 
"%02x") at /root/vpp-1707/build-data/../src/vppinfra/format.c:423
#10 0x0043ce7f in format_hex_bytes (s=, va=) at /root/vpp-1707/build-data/../src/vpp/api/api_format.c:4266
#11 0x76b67b63 in do_percent (va=0x7fffb65ce588, fmt=, 
_s=) at 
/root/vpp-1707/build-data/../src/vppinfra/format.c:373
#12 va_format (s=0x7fffb664aeb4 '0' ..., fmt=, va=va@entry=0x7fffb65ce588) at 
/root/vpp-1707/build-data/../src/vppinfra/format.c:404
#13 0x76b67417 in format (s=, 
fmt=fmt@entry=0x7766983e "%s(%d): %U\n") at 
/root/vpp-1707/build-data/../src/vppinfra/format.c:423
#14 0x77326c44 in format_generic_tlv (s=, va=) at /root/vpp-1707/build-data/../src/vnet/cdp/cdp_input.c:74
#15 0x76b67b63 in do_percent (va=0x7fffb65ce768, fmt=, 
_s=) at 
/root/vpp-1707/build-data/../src/vppinfra/format.c:373
#16 va_format (s=0x7fffb664aeb4 '0' ..., fmt=, va=va@entry=0x7fffb65ce768) at 
/root/vpp-1707/build-data/../src/vppinfra/format.c:404
#17 0x76b67417 in format (s=, 
fmt=fmt@entry=0x7769e08f "  %U") at 
/root/vpp-1707/build-data/../src/vppinfra/format.c:423
#18 0x7732987f in cdp_input_format_trace (s=, 
args=) at 
/root/vpp-1707/build-data/../src/vnet/cdp/cdp_input.c:492
#19 0x76b67b63 in do_percent (va=0x7fffb65ce948, fmt=, 
_s=) at 
/root/vpp-1707/build-data/../src/vppinfra/format.c:373
#20 va_format (s=0x7fffb665b9d8 '-' , " Start of thread 0 
vpp_main ", '-' , "\nPacket 1\n\n00:00:37:241764: 
dpdk-input\n  GigabitEthernet0/4/0 rx queue 0\n  buffer 0x1ca7: current data 0, 
length 474, free-list 0, clo"..., fmt=, 
va=va@entry=0x7fffb65ce948) at 
/root/vpp-1707/build-data/../src/vppinfra/format.c:404
#21 0x76b67417 in format (s=, 
fmt=fmt@entry=0x779a41c7 "\n  %U") at 
/root/vpp-1707/build-data/../src/vppinfra/format.c:423
#22 0x779895fb in format_vlib_trace (s=, va=) at /root/vpp-1707/build-data/../src/vlib/trace.c:162
#23 0x76b67b63 in do_percent (va=0x7fffb65ceb38, fmt=, 
_s=) at 
/root/vpp-1707/build-data/../src/vppinfra/format.c:373
#24 va_format (s=0x7fffb665d110 '-' , " Start of thread 0 
vpp_main ", '-' , "\nPacket 1\n\n00:00:37:", fmt=, va=va@entry=0x7fffb65ceb38) at 
/root/vpp-

Re: [vpp-dev] show trace bug in vpp stable 1707

[Luke, Chris]

Andrew,

Are you able to recreate it with a debug build running in the debugger, so we 
can get a backtrace?

Can you share details on how VPP is setup at the time of the crash?

Chris

From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On 
Behalf Of Andrew Taylor
Sent: Thursday, July 13, 2017 5:19
To: vpp-dev@lists.fd.io
Subject: [vpp-dev] show trace bug in vpp stable 1707


Hi,
by following commands in VPP Stable 1707, core dump accrued when packets 
received.

trace add dpdk-input 100
sh trace

Does it a bug or something changed in this version ?

Thanks.

___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] vpp installation without internet

[Luke, Chris]

You need you install the missing dependencies as you find them. ‘dkms’ is a 
standard Ubuntu packages to allow runtime compilation of kernel modules. You 
can grab it from any Ubuntu repo, or perhaps the apt cache of another Ubuntu 
machine.

I suggest however you invest in an HTTP proxy or a local APT repo or cache.

Chris.

From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On 
Behalf Of SAKTHIVEL ANAND S
Sent: Wednesday, July 12, 2017 5:44
To: vpp-dev@lists.fd.io
Subject: [vpp-dev] vpp installation without internet

Hi
I am new to vpp..
i am trying to install vpp on my testbed, and the testbed will not have 
internet and also there is no deveopment tool chain(tools like gcc,etc.).
I  have downloaded source to my dev-server and build the vpp in it. Finally i 
copied the *.deb files to my testbed and was tring to install those and getting 
the following error.

dpkg: dependency problems prevent configuration of vpp-dpdk-dkms:
 vpp-dpdk-dkms depends on dkms (>= 2.1.0.0); however:
  Package dkms is not installed.

dpkg: error processing package vpp-dpdk-dkms (--install):
 dependency problems - leaving unconfigured

Processing triggers for ureadahead (0.100.0-19) ...
Processing triggers for libc-bin (2.23-0ubuntu5) ...
Errors were encountered while processing:
 vpp-dpdk-dkms


Steps i did:
on my development m/c:
  git clone https://gerrit.fd.io/r/vpp
  cd vpp
  git checkout v16.06
  make install-dep
  make build-release
  make pkg-deb
  copied *.deb packages to testbed
on my testbed: i ran "dpkg -i *.deb"

p.s:vpp version - 16.06
dev os  - ubuntu server 16.04.2
testbed os  - ubuntu server 16.04.2

any help would be appreciated.
Basically I am looking at how to install & run VPP on a m/c that can't have 
internet (hence no apt-get) and no build tool chains.

--
Thanks
Sakthivel S OM
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] monitor function

[Luke, Chris]

The generated documentation has a handy link to the source. :)

https://docs.fd.io/vpp/17.07/clicmd_src_vlib.html#clicmd_show_runtime

Chris.

From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On 
Behalf Of Yuliang Li
Sent: Tuesday, July 11, 2017 21:32
To: Ni, Hongjun 
Cc: vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] monitor function

Thanks Hongjun. Do you know which piece of code shall I look at if I want to 
add my customized monitoring and expose them to vppctl?

On Tue, Jul 11, 2017 at 6:23 PM, Ni, Hongjun 
> wrote:
Hi Yuliang,

Please see below link for details:
https://wiki.fd.io/view/VPP/Command-line_Interface_(CLI)_Guide#CLI_features

-Hongjun

From: vpp-dev-boun...@lists.fd.io 
[mailto:vpp-dev-boun...@lists.fd.io] On 
Behalf Of Yuliang Li
Sent: Wednesday, July 12, 2017 9:19 AM
To: vpp-dev@lists.fd.io
Subject: [vpp-dev] monitor function

Hi,

I want to add more things to be monitored when using command "show run". How 
does the command in vppctl interact with vpp?

Thanks,
--
Yuliang Li
PhD student
Department of Computer Science
Yale University



--
Yuliang Li
PhD student
Department of Computer Science
Yale University
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] Building on Fedora 24

[Luke, Chris]

This should now be fixed in master; stable was not impacted.

I toyed with having the service startup scripts create the run dir, but in the 
end decided to move the existing code in the DPDK plugin that mkdir()’s 
/run/vpp into vlib and have both the console socket and DPDK code call it so 
that it gets created when VPP is run manually, eg for development. In the 
console socket case it only does so if the socket looks like it will be in that 
directory (ie, it’s prefixed with /run/vpp/).

Chris.

From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On 
Behalf Of Luke, Chris
Sent: Wednesday, June 28, 2017 9:29 AM
To: Tomas Brännström <tomas.a.brannst...@tieto.com>; Klement Sekera -X (ksekera 
- PANTHEON TECHNOLOGIES at Cisco) <ksek...@cisco.com>; Burt Silverman 
<bur...@gmail.com>
Cc: vpp-dev <vpp-dev@lists.fd.io>
Subject: Re: [vpp-dev] Building on Fedora 24

No, it’s an artifact of a recent merge that enables the console socket as a 
unix-domain socket by default. Will propose a patch to remedy this shortly.

From: vpp-dev-boun...@lists.fd.io<mailto:vpp-dev-boun...@lists.fd.io> 
[mailto:vpp-dev-boun...@lists.fd.io] On Behalf Of Tomas Brännström
Sent: Wednesday, June 28, 2017 8:19
To: Klement Sekera -X (ksekera - PANTHEON TECHNOLOGIES at Cisco) 
<ksek...@cisco.com<mailto:ksek...@cisco.com>>; Burt Silverman 
<bur...@gmail.com<mailto:bur...@gmail.com>>
Cc: vpp-dev <vpp-dev@lists.fd.io<mailto:vpp-dev@lists.fd.io>>
Subject: Re: [vpp-dev] Building on Fedora 24

Sorry for spamming, but using strace I noticed that vppctl tried to connect to 
a socket file in /run/vpp

This folder didn't exist, but when I created it, vpp could start successfully. 
There's no such folder in my Ubuntu install, so is this exclusive to RHEL based 
distros?

/Tomas

On 28 June 2017 at 13:21, Tomas Brännström 
<tomas.a.brannst...@tieto.com<mailto:tomas.a.brannst...@tieto.com>> wrote:
We targeted CentOS instead and there it works fine to build and install.

However, there's some other issue now. When I start the VPP service, it looks 
like it immediately dies:

$ sudo service vpp start
Redirecting to /bin/systemctl start  vpp.service
$ sudo service vpp status
Redirecting to /bin/systemctl status  vpp.service
● vpp.service - Vector Packet Processing Process
   Loaded: loaded (/usr/lib/systemd/system/vpp.service; disabled; vendor 
preset: disabled)
   Active: inactive (dead)

This error message is printed:
vpp[5859]: clib_socket_init: bind: No such file or directory

This is in a Virtualbox VM. Not sure how to proceed since usually a better 
error message is printed when it fails (for example missing drivers and 
whatnot).

/Tomas

On 27 June 2017 at 21:17, Klement Sekera -X (ksekera - PANTHEON TECHNOLOGIES at 
Cisco) <ksek...@cisco.com<mailto:ksek...@cisco.com>> wrote:
Unfortunately, I'm no rpm packaging expert, somebody else will have to
chime in...

Thanks,
Klement

Quoting Tomas Brännström (2017-06-27 17:18:40)
>I got the same error :-(
>make bootstrap and build works, but building rpg packages fail...
>/Tomas
>On 27 June 2017 at 16:25, Klement Sekera -X (ksekera - PANTHEON
>TECHNOLOGIES at Cisco) <[1]ksek...@cisco.com<mailto:ksek...@cisco.com>> 
> wrote:
>
>  Hi Tomas,
>
>  could you please take a look at the main Makefile:
>
>  57 ifeq ($(OS_ID)-$(OS_VERSION_ID),fedora-25)
>  58 RPM_DEPENDS += python2-virtualenv
>  59 RPM_DEPENDS_GROUPS = 'C Development Tools and Libraries'
>  60 else
>  61 RPM_DEPENDS += python-virtualenv
>  62 RPM_DEPENDS_GROUPS = 'Development Tools'
>  63 endif
>
>  see how the fedora-25 is the version which uses python2-virtualenv
>  while all others use python-virtualenv? Could you please change
>  fedora-25
>  to fedora-24 on line 57 and let us know if this smooths things out?
>  Maybe the fix is a simple one-liner...
>
>  Thanks,
>  Klement
>
>  Quoting Tomas Brännström (2017-06-27 16:08:31)
>  >Hello
>  >I'm having some troubles building VPP (latest master) from source
>  on
>  >Fedora 24.
>  >At first when doing `make bootstrap' it complained about not
>  finding
>  >python-virtualenv. I could get around this by changing changing the
>  >Makefile to look for "python2-virtualenv" which was the version
>  that got
>  >installed.
>  >But when doing `make pgk-rpm' I get the following errors:
>  >make[2]: Entering directory
>  '/home/fedora/git/vpp/extras/rpm/vpp-17.10'
>  >Please install missing RPMs: \npackage python-virtualenv is not
>  >installed\n
>  >by executing "ma

Re: [vpp-dev] 17.07 RC2 today

[Luke, Chris]

+1

Fairly important, IMO.

Chris.

From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On 
Behalf Of Billy McFall
Sent: Wednesday, July 05, 2017 9:27 AM
To: Neale Ranns (nranns) 
Cc: vpp-dev 
Subject: Re: [vpp-dev] 17.07 RC2 today

I just wrote VPP-900 and would like to get 
it into 17.07. The License field in the RPM specfile lists MIT as the license 
and I believe it should be ASL 2.0. Working on the patch now and should be 
available shortly if you are OK with this change?

Thanks,
Billy

On Wed, Jul 5, 2017 at 8:48 AM, Neale Ranns (nranns) 
> wrote:

Dear All,

Today is 17.07 RC2 day, hooray…

I will soon be laying the RC2 label. If there are any fixes you would like 
merged before that, please let me know AYEC.

Our patching process continues to remain the same until formal release – please 
commit fixes to the stable/1707 branch and then cherry-pick to master.

Thanks,
Neale


___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] Buffer allocation failure

[Luke, Chris]

The packet you receive, what do you do with it?

If you don’t forward it, you have two choices:


  *   You could deallocate its buffer.
  *   Or, better, recycle it and use that packets buffer for your outgoing 
packet. That way you avoid the expense of allocating a new one.

Chris.

From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On 
Behalf Of Alessio Silvestro
Sent: Friday, June 30, 2017 8:25
To: vpp-dev@lists.fd.io
Subject: [vpp-dev] Buffer allocation failure

Dear vvp-dev,

I developed a new vpp node that listen for UDP traffic on a specific port, 
then, for each received packet, create a new buffer and send an UDP packet to 
the source IP address.

The application is running fine, but when I send some thousands of packets, at 
some point vpp starts to give "buffer allocation failure" error.

Where do you think could be the problem.

Is the node not correctly de-allocating the buffer or there is some specific 
vpp and/or system configuration that can cause this problem?

Best regards,
Alessio
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] Building on Fedora 24

[Luke, Chris]

No, it’s an artifact of a recent merge that enables the console socket as a 
unix-domain socket by default. Will propose a patch to remedy this shortly.

From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On 
Behalf Of Tomas Brännström
Sent: Wednesday, June 28, 2017 8:19
To: Klement Sekera -X (ksekera - PANTHEON TECHNOLOGIES at Cisco) 
; Burt Silverman 
Cc: vpp-dev 
Subject: Re: [vpp-dev] Building on Fedora 24

Sorry for spamming, but using strace I noticed that vppctl tried to connect to 
a socket file in /run/vpp

This folder didn't exist, but when I created it, vpp could start successfully. 
There's no such folder in my Ubuntu install, so is this exclusive to RHEL based 
distros?

/Tomas

On 28 June 2017 at 13:21, Tomas Brännström 
> wrote:
We targeted CentOS instead and there it works fine to build and install.

However, there's some other issue now. When I start the VPP service, it looks 
like it immediately dies:

$ sudo service vpp start
Redirecting to /bin/systemctl start  vpp.service
$ sudo service vpp status
Redirecting to /bin/systemctl status  vpp.service
● vpp.service - Vector Packet Processing Process
   Loaded: loaded (/usr/lib/systemd/system/vpp.service; disabled; vendor 
preset: disabled)
   Active: inactive (dead)

This error message is printed:
vpp[5859]: clib_socket_init: bind: No such file or directory

This is in a Virtualbox VM. Not sure how to proceed since usually a better 
error message is printed when it fails (for example missing drivers and 
whatnot).

/Tomas

On 27 June 2017 at 21:17, Klement Sekera -X (ksekera - PANTHEON TECHNOLOGIES at 
Cisco) > wrote:
Unfortunately, I'm no rpm packaging expert, somebody else will have to
chime in...

Thanks,
Klement

Quoting Tomas Brännström (2017-06-27 17:18:40)
>I got the same error :-(
>make bootstrap and build works, but building rpg packages fail...
>/Tomas
>On 27 June 2017 at 16:25, Klement Sekera -X (ksekera - PANTHEON
>TECHNOLOGIES at Cisco) <[1]ksek...@cisco.com> 
> wrote:
>
>  Hi Tomas,
>
>  could you please take a look at the main Makefile:
>
>  57 ifeq ($(OS_ID)-$(OS_VERSION_ID),fedora-25)
>  58 RPM_DEPENDS += python2-virtualenv
>  59 RPM_DEPENDS_GROUPS = 'C Development Tools and Libraries'
>  60 else
>  61 RPM_DEPENDS += python-virtualenv
>  62 RPM_DEPENDS_GROUPS = 'Development Tools'
>  63 endif
>
>  see how the fedora-25 is the version which uses python2-virtualenv
>  while all others use python-virtualenv? Could you please change
>  fedora-25
>  to fedora-24 on line 57 and let us know if this smooths things out?
>  Maybe the fix is a simple one-liner...
>
>  Thanks,
>  Klement
>
>  Quoting Tomas Brännström (2017-06-27 16:08:31)
>  >Hello
>  >I'm having some troubles building VPP (latest master) from source
>  on
>  >Fedora 24.
>  >At first when doing `make bootstrap' it complained about not
>  finding
>  >python-virtualenv. I could get around this by changing changing the
>  >Makefile to look for "python2-virtualenv" which was the version
>  that got
>  >installed.
>  >But when doing `make pgk-rpm' I get the following errors:
>  >make[2]: Entering directory
>  '/home/fedora/git/vpp/extras/rpm/vpp-17.10'
>  >Please install missing RPMs: \npackage python-virtualenv is not
>  >installed\n
>  >by executing "make install-dep"\n
>  >Makefile:175: recipe for target
>  >
>  '/home/fedora/git/vpp/extras/rpm/vpp-17.10/build-root/.bootstrap.ok'
>  >failed
>  >make[2]: ***
>  >
>  [/home/fedora/git/vpp/extras/rpm/vpp-17.10/build-root/.bootstrap.ok]
>  Error
>  >1
>  >make[2]: Leaving directory
>  '/home/fedora/git/vpp/extras/rpm/vpp-17.10'
>  >error: Bad exit status from /var/tmp/rpm-tmp.qSFuzD (%build)
>  >RPM build errors:
>  >Macro %python2_minor_version defined but not used within scope
>  >Bad exit status from /var/tmp/rpm-tmp.qSFuzD (%build)
>  >Makefile:22: recipe for target 'all' failed
>  >make[1]: *** [all] Error 1
>  >make[1]: Leaving directory '/home/fedora/git/vpp/extras/rpm'
>  >Makefile:397: recipe for target 'pkg-rpm' failed
>  >make: *** [pkg-rpm] Error 2
>  >I tried changing to python2-virtualenv in that Makefile as well but
>  it
>  >seems to change back into python-virtualenv, and besides, there
>  seems to
>  > be other problems here as well.
>  >Is there a workaround for this or is  Fedora 24 simply not
>  supported?
>  >/Tomas
>
> References
>
>Visible links
>1. 

[vpp-dev] Jira still had version 17.04 open

[Luke, Chris]

Just FYI, if Jira just spammed you from me, it's because I noticed version 
"17.04" was still marked 'unreleased', which I just fixed. I also removed the 
erroneous "1704" version. :)

There were a bunch of outstanding issues, which it bumped to 17.10 I think. At 
some point we need to do some weeding.

Chris.
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] Help regarding af_packet worker thread assertion

[Luke, Chris]

Do you have the DPDK plugin loaded? It looks like “no”.

 

If not, it’s likely because the buffer allocator used when DPDK is not loaded 
is not yet thread-safe. I’ve done some early work on this but it’s not going to 
make it into the open for a while.

 

For now, don’t enable worker threads if DPDK plugin isn’t loaded.

 

Chris.

 

From:  on behalf of Sreejith Surendran Nair 

Date: Wednesday, June 21, 2017 at 02:33
To: vpp-dev 
Subject: [vpp-dev] Help regarding af_packet worker thread assertion

 

Hi All,

This regarding running worker threads with af_packet interface on VM ubuntu 
16.10. 

I have tried configuring the af_packet interface with cpu worker thread support 
but I am getting assertion fail not sure if it is due to worker thread getting 
scheduled on core 0.

Config :
---

startup config:
cpu {
  workers 1
}

DBGvpp# sh threads
ID NameTypeLWP Sched Policy (Priority)  lcore  
Core   Socket State 
0  vpp_main23372   other (0)0  
0  0  
1  vpp_wk_0workers 23376   other (0)1  
1  0  
2  stats   23377   other (0)0  
0  0  
DBGvpp# create host-interface name enp0s9 hw-addr 08:00:27:06:00:de
host-enp0s9
DBGvpp# sh int
  Name   Idx   State  Counter  
Count 
host-enp0s9   1down  
local00down  
DBGvpp# set int ip address host-enp0s9 192.168.56.104/24
DBGvpp# set int state host-enp0s9 up

GDB:
-

1: 
/home/sreejith/Downloads/sachin_odp4vpp/odp4vpp/build-data/../src/vlib/buffer_funcs.h:224
 (vlib_buffer_set_known_state) assertion `vlib_get_thread_index () == 0' fails
Failed to save post-mortem API trace to /tmp/api_post_mortem.23372

Thread 2 "vpp_wk_0" received signal SIGABRT, Aborted.
[Switching to Thread 0x7fff93493700 (LWP 23376)]
__GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:58
58../sysdeps/unix/sysv/linux/raise.c: No such file or directory.
(gdb) 
(gdb) bt
#0  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:58
#1  0x75e203ea in __GI_abort () at abort.c:89
#2  0xc29c in os_panic () at 
/home/sreejith/Downloads/sachin_odp4vpp/odp4vpp/build-data/../src/vpp/vnet/main.c:263
#3  0x76601959 in debugger () at 
/home/sreejith/Downloads/sachin_odp4vpp/odp4vpp/build-data/../src/vppinfra/error.c:84
#4  0x76601d61 in _clib_error (how_to_die=2, function_name=0x0, 
line_number=0, fmt=0x7797b000 "%s:%d (%s) assertion `%s' fails")
at 
/home/sreejith/Downloads/sachin_odp4vpp/odp4vpp/build-data/../src/vppinfra/error.c:143
#5  0x778b58d2 in vlib_buffer_set_known_state (vm=0x7fffb5f046f8, 
buffer_index=68, state=VLIB_BUFFER_KNOWN_FREE)
at 
/home/sreejith/Downloads/sachin_odp4vpp/odp4vpp/build-data/../src/vlib/buffer_funcs.h:224
#6  0x778b87e8 in fill_free_list (vm=0x7fffb5f046f8, fl=0x7fffb6072140, 
min_free_buffers=256)
at 
/home/sreejith/Downloads/sachin_odp4vpp/odp4vpp/build-data/../src/vlib/buffer.c:556
#7  0x778b8938 in alloc_from_free_list (vm=0x7fffb5f046f8, 
free_list=0x7fffb6072140, alloc_buffers=0x7fffb6483464, n_alloc_buffers=256)
at 
/home/sreejith/Downloads/sachin_odp4vpp/odp4vpp/build-data/../src/vlib/buffer.c:592
#8  0x778b8b7c in vlib_buffer_alloc_internal (vm=0x7fffb5f046f8, 
buffers=0x7fffb6483464, n_buffers=256)
at 
/home/sreejith/Downloads/sachin_odp4vpp/odp4vpp/build-data/../src/vlib/buffer.c:620
#9  0x773c15b4 in vlib_buffer_alloc (vm=0x7fffb5f046f8, 
buffers=0x7fffb6483464, n_buffers=256)
at 
/home/sreejith/Downloads/sachin_odp4vpp/odp4vpp/build-data/../src/vlib/buffer_funcs.h:251
#10 0x773c2be0 in af_packet_device_input_fn (vm=0x7fffb5f046f8, 
node=0x7fffb6079d9c, frame=0x0, apif=0x7fffb5495a80)
at 
/home/sreejith/Downloads/sachin_odp4vpp/odp4vpp/build-data/../src/vnet/devices/af_packet/node.c:141
#11 0x773c3337 in af_packet_input_fn (vm=0x7fffb5f046f8, 
node=0x7fffb6079d9c, frame=0x0)
at 
/home/sreejith/Downloads/sachin_odp4vpp/odp4vpp/build-data/../src/vnet/devices/af_packet/node.c:259
#12 0x778f2fe6 in dispatch_node (vm=0x7fffb5f046f8, 
node=0x7fffb6079d9c, type=VLIB_NODE_TYPE_INPUT, 
dispatch_state=VLIB_NODE_STATE_INTERRUPT, frame=0x0, 
last_time_stamp=237041860335868) at 
/home/sreejith/Downloads/sachin_odp4vpp/odp4vpp/build-data/../src/vlib/main.c:1016
#13 0x778f4f5f in vlib_main_or_worker_loop (vm=0x7fffb5f046f8, 
is_main=0) at 
/home/sreejith/Downloads/sachin_odp4vpp/odp4vpp/build-data/../src/vlib/main.c:1552
#14 0x778f570f in vlib_worker_loop (vm=0x7fffb5f046f8) at 
/home/sreejith/Downloads/sachin_odp4vpp/odp4vpp/build-data/../src/vlib/main.c:1650
#15 0x7793ef94 in 

Re: [vpp-dev] Bind / Unbind of ACL

[Luke, Chris]

+1

> -Original Message-
> From: Andrew  Yourtchenko [mailto:ayour...@gmail.com]
> Sent: Saturday, June 17, 2017 5:28
> To: Luke, Chris <chris_l...@cable.comcast.com>
> Cc: Marco Varlese <marco.varl...@suse.com>; vpp-dev@lists.fd.io
> Subject: Re: [vpp-dev] Bind / Unbind of ACL
> 
> Perfect, thanks a lot!
> 
> I've pushed the update https://gerrit.fd.io/r/#/c/6858/10 which codifies all 
> of
> our discussion.
> 
> With that change, both applying an inexistent ACL and deleting the ACL that
> is applied somewhere will be an error.
> 
> One can still create an ACL with no rules, in which case applying that ACL 
> will
> follow the lookup logic with the default-deny in the end of the vector of ACLs
> lookup.
> 
> --a
> 
> On 6/17/17, Luke, Chris <chris_l...@comcast.com> wrote:
> > That was going to be one of my queries, but forgot to ask. Do we allow
> > that currently? Probably shouldn't, as you say, for symmetry.
> >
> > Chris.
> >
> >> -Original Message-
> >> From: Andrew Yourtchenko [mailto:ayour...@gmail.com]
> >> Sent: Friday, June 16, 2017 17:51
> >> To: Luke, Chris <chris_l...@cable.comcast.com>
> >> Cc: Marco Varlese <marco.varl...@suse.com>; vpp-dev@lists.fd.io
> >> Subject: Re: [vpp-dev] Bind / Unbind of ACL
> >>
> >> Ok! So what do you think if then we were to also disallow applying
> >> the ACL that doesn't exist yet ?
> >>
> >> It feels like it would be a matching symmetric behavior "from the
> >> other side".
> >> ?
> >>
> >> --a
> >>
> >> On 16 Jun 2017, at 15:38, Luke, Chris <chris_l...@comcast.com> wrote:
> >>
> >> >> From: Marco Varlese [mailto:marco.varl...@suse.com]
> >> >> Sent: Friday, June 16, 2017 9:23
> >> >>> On Fri, 2017-06-16 at 15:12 +0200, Andrew   Yourtchenko wrote:
> >> >>>> On 6/16/17, Marco Varlese <marco.varl...@suse.com> wrote:
> >> >>>>
> >> >>>>> On Thu, 2017-06-15 at 14:22 +0200, Andrew   Yourtchenko wrote:
> >> >>>>>
> >> >>>>> After a bit more thinking - there is a way that should take
> >> >>>>> care of
> >> >>>>> both:
> >> >>>>>
> >> >>>>> 1) What Chris wrote: have consistent behaviour with
> >> >>>>> non-existent ACL as if the ACL matching fell off the end of the
> >> >>>>> ACL: if an empty ACL is referenced, treat it as if it had
> >> >>>>> entries but none of them had matched. Then we still hit the
> >> >>>>> "default deny" if none of the applied ACLs match, and drop the
> >> >>>>> packets - so it will be logical.
> >> >>>>>
> >> >>>>> 2) What Marco wrote: when deleting an already referenced ACL,
> >> >>>>> unapply it from all the places where it is applied.
> >> >>>>>
> >> >>>>> It's a change in the behaviour in that the current behaviour is
> >> >>>>> to have the empty ACL act as if it was "deny any any", and
> >> >>>>> block the matching even if there is another ACL after it - but
> >> >>>>> on the other hand this would take both viewpoints in mind...
> >> >>>> I think this approach would still leave the system in an
> >> >>>> inconsistent
> >> state:
> >> >>>> an
> >> >>>> interface is basically assigned an ACL which does not exist in
> >> >>>> the
> >> system.
> >> >>>> Also, the risk I see is if I later on create an ACL with the
> >> >>>> previously used index then an interface would see that ACL being
> >> >>>> applied automatically (since it's referenced). However, I may
> >> >>>> not want to have that ACL assigned to that particular interface.
> >> >>>> Correct?
> >> >>>>
> >> >>>> I think that the "deletion" of an ACL could see one of the two
> >> >>>> behaviours
> >> >>>> below:
> >> >>>> 1) the deletion of an ACL should be DENIED if that ACL is
> >> >>>> assigned to any interface (probably the easier and safer
> >> >>>> approach);
>

Re: [vpp-dev] Bind / Unbind of ACL

[Luke, Chris]

That was going to be one of my queries, but forgot to ask. Do we allow that 
currently? Probably shouldn't, as you say, for symmetry.

Chris.

> -Original Message-
> From: Andrew Yourtchenko [mailto:ayour...@gmail.com]
> Sent: Friday, June 16, 2017 17:51
> To: Luke, Chris <chris_l...@cable.comcast.com>
> Cc: Marco Varlese <marco.varl...@suse.com>; vpp-dev@lists.fd.io
> Subject: Re: [vpp-dev] Bind / Unbind of ACL
> 
> Ok! So what do you think if then we were to also disallow applying the ACL
> that doesn't exist yet ?
> 
> It feels like it would be a matching symmetric behavior "from the other side".
> ?
> 
> --a
> 
> On 16 Jun 2017, at 15:38, Luke, Chris <chris_l...@comcast.com> wrote:
> 
> >> From: Marco Varlese [mailto:marco.varl...@suse.com]
> >> Sent: Friday, June 16, 2017 9:23
> >>> On Fri, 2017-06-16 at 15:12 +0200, Andrew   Yourtchenko wrote:
> >>>> On 6/16/17, Marco Varlese <marco.varl...@suse.com> wrote:
> >>>>
> >>>>> On Thu, 2017-06-15 at 14:22 +0200, Andrew   Yourtchenko wrote:
> >>>>>
> >>>>> After a bit more thinking - there is a way that should take care of 
> >>>>> both:
> >>>>>
> >>>>> 1) What Chris wrote: have consistent behaviour with non-existent
> >>>>> ACL as if the ACL matching fell off the end of the ACL: if an
> >>>>> empty ACL is referenced, treat it as if it had entries but none of
> >>>>> them had matched. Then we still hit the "default deny" if none of
> >>>>> the applied ACLs match, and drop the packets - so it will be logical.
> >>>>>
> >>>>> 2) What Marco wrote: when deleting an already referenced ACL,
> >>>>> unapply it from all the places where it is applied.
> >>>>>
> >>>>> It's a change in the behaviour in that the current behaviour is to
> >>>>> have the empty ACL act as if it was "deny any any", and block the
> >>>>> matching even if there is another ACL after it - but on the other
> >>>>> hand this would take both viewpoints in mind...
> >>>> I think this approach would still leave the system in an inconsistent
> state:
> >>>> an
> >>>> interface is basically assigned an ACL which does not exist in the
> system.
> >>>> Also, the risk I see is if I later on create an ACL with the
> >>>> previously used index then an interface would see that ACL being
> >>>> applied automatically (since it's referenced). However, I may not
> >>>> want to have that ACL assigned to that particular interface.
> >>>> Correct?
> >>>>
> >>>> I think that the "deletion" of an ACL could see one of the two
> >>>> behaviours
> >>>> below:
> >>>> 1) the deletion of an ACL should be DENIED if that ACL is assigned
> >>>> to any interface (probably the easier and safer approach);
> >>>> 2) the deletion of an ACL should see a CASCADING effect onto the
> >>>> interfaces which would be "cleaned up" of any references to that
> >>>> ACL;
> >>>>
> >>>
> >>> Right, the (2) was what I was trying to suggest to do...
> >>>
> >>>>
> >>>> I think (1) is a very good way of solving the initial problem since
> >>>> it works nicely if you manage VPP directly (e.g. via command-line)
> >>>> and if you use a controller. In the latter, the controller can
> >>>> react on the "error" returned by the acl_del API because that ACL
> >>>> is assigned somewhere.
> >>>>
> >>>
> >>> ...but the (1) is another good option to me.
> >>>
> >>> So it seems we are converging on (1) ?
> >> I would go with (1)...
> >
> > I feel I have a slight preference for this (1) also; In general I don't 
> > like the
> implicit actions such as in (2).
> >
> > Chris
> >
> >>>
> >>> --a
> >>>
> >>>
> >>>
> >>>>
> >>>>
> >>>> Cheers,
> >>>> Marco
> >>>>
> >>>>>
> >>>>>
> >>>>> What do you think ?
> >>>>>
> >>>>> --a
> >>>>>
> >>>>>> On 6/9/17, Andrew   Your

Re: [vpp-dev] Bind / Unbind of ACL

[Luke, Chris]

> From: Marco Varlese [mailto:marco.varl...@suse.com]
> Sent: Friday, June 16, 2017 9:23
> On Fri, 2017-06-16 at 15:12 +0200, Andrew   Yourtchenko wrote:
> > On 6/16/17, Marco Varlese <marco.varl...@suse.com> wrote:
> > >
> > > On Thu, 2017-06-15 at 14:22 +0200, Andrew   Yourtchenko wrote:
> > > >
> > > > After a bit more thinking - there is a way that should take care of 
> > > > both:
> > > >
> > > > 1) What Chris wrote: have consistent behaviour with non-existent
> > > > ACL as if the ACL matching fell off the end of the ACL: if an
> > > > empty ACL is referenced, treat it as if it had entries but none of
> > > > them had matched. Then we still hit the "default deny" if none of
> > > > the applied ACLs match, and drop the packets - so it will be logical.
> > > >
> > > > 2) What Marco wrote: when deleting an already referenced ACL,
> > > > unapply it from all the places where it is applied.
> > > >
> > > > It's a change in the behaviour in that the current behaviour is to
> > > > have the empty ACL act as if it was "deny any any", and block the
> > > > matching even if there is another ACL after it - but on the other
> > > > hand this would take both viewpoints in mind...
> > > I think this approach would still leave the system in an inconsistent 
> > > state:
> > > an
> > > interface is basically assigned an ACL which does not exist in the system.
> > > Also, the risk I see is if I later on create an ACL with the
> > > previously used index then an interface would see that ACL being
> > > applied automatically (since it's referenced). However, I may not
> > > want to have that ACL assigned to that particular interface.
> > > Correct?
> > >
> > > I think that the "deletion" of an ACL could see one of the two
> > > behaviours
> > > below:
> > > 1) the deletion of an ACL should be DENIED if that ACL is assigned
> > > to any interface (probably the easier and safer approach);
> > > 2) the deletion of an ACL should see a CASCADING effect onto the
> > > interfaces which would be "cleaned up" of any references to that
> > > ACL;
> > >
> >
> > Right, the (2) was what I was trying to suggest to do...
> >
> > >
> > > I think (1) is a very good way of solving the initial problem since
> > > it works nicely if you manage VPP directly (e.g. via command-line)
> > > and if you use a controller. In the latter, the controller can react
> > > on the "error" returned by the acl_del API because that ACL is
> > > assigned somewhere.
> > >
> >
> > ...but the (1) is another good option to me.
> >
> > So it seems we are converging on (1) ?
> I would go with (1)...

I feel I have a slight preference for this (1) also; In general I don't like 
the implicit actions such as in (2).

Chris

> >
> > --a
> >
> >
> >
> > >
> > >
> > > Cheers,
> > > Marco
> > >
> > > >
> > > >
> > > > What do you think ?
> > > >
> > > > --a
> > > >
> > > > On 6/9/17, Andrew   Yourtchenko <ayour...@gmail.com> wrote:
> > > > >
> > > > >
> > > > > Assuming the only change is to effectively have
> > > > > "unbind_acl_from_everywhere; delete_acl" instead of
> > > > > "delete_acl", maybe it would be best to tackle that post-17.07
> > > > > with a separate API message acl_del_and_unbind or similar ?
> > > > >
> > > > > I feel a beet wary of adding more hidden state (even though the
> > > > > reflected sessions table does provide already plenty of it :)
> > > > >
> > > > > --a
> > > > >
> > > > > On 6/9/17, Luke, Chris <chris_l...@comcast.com> wrote:
> > > > > >
> > > > > >
> > > > > > Would it make sense to have a flag on the interface (or
> > > > > > globally), set when applying the ACL, that indicates the
> > > > > > desired behavior when the ACL is empty or non-existent? At the
> > > > > > moment to me it seems logical that this is the same behavior
> > > > > > as when matching falls off the end of the ACL.
> > > > > >
> > > > > > Chris.
> > >

Re: [vpp-dev] Bind / Unbind of ACL

[Luke, Chris]

I’m mostly agnostic with 2; an alternate behavior might be to refuse to delete 
an ACL if it is referenced anywhere. I’m more concerned with consistency with 
this sort of operation across VPP which I feel is more important, though no 
other examples spring to mind this early in the morning!

Chris.

On 6/15/17, 08:22, "Andrew   Yourtchenko" <ayour...@gmail.com> wrote:

After a bit more thinking - there is a way that should take care of both:

1) What Chris wrote: have consistent behaviour with non-existent ACL
as if the ACL matching fell off the end of the ACL: if an empty ACL is
referenced, treat it as if it had entries but none of them had
matched. Then we still hit the "default deny" if none of the applied
ACLs match, and drop the packets - so it will be logical.

2) What Marco wrote: when deleting an already referenced ACL, unapply
it from all the places where it is applied.

It's a change in the behaviour in that the current behaviour is to
have the empty ACL act as if it was "deny any any", and block the
matching even if there is another ACL after it - but on the other hand
this would take both viewpoints in mind...

What do you think ?

--a

On 6/9/17, Andrew   Yourtchenko <ayour...@gmail.com> wrote:
> Assuming the only change is to effectively have
> "unbind_acl_from_everywhere; delete_acl" instead of "delete_acl",
> maybe it would be best to tackle that post-17.07 with a separate API
> message acl_del_and_unbind or similar ?
>
> I feel a beet wary of adding more hidden state (even though the
> reflected sessions table does provide already plenty of it :)
>
> --a
>
> On 6/9/17, Luke, Chris <chris_l...@comcast.com> wrote:
>> Would it make sense to have a flag on the interface (or globally), set
>> when
>> applying the ACL, that indicates the desired behavior when the ACL is
>> empty
>> or non-existent? At the moment to me it seems logical that this is the
>> same
>> behavior as when matching falls off the end of the ACL.
>>
>> Chris.
>>
>>> -Original Message-
>>> From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io]
>>> On
>>> Behalf Of Andrew ?? Yourtchenko
>>> Sent: Friday, June 9, 2017 7:53
>>> To: Marco Varlese <marco.varl...@suse.com>
>>> Cc: vpp-dev@lists.fd.io
>>> Subject: Re: [vpp-dev] Bind / Unbind of ACL
>>>
>>> Hi Marco,
>>>
>>> Yes, this works as expected, assuming after deletion *all* the traffic
>>> is
>>> denied, rather than just the SSH traffic.
>>>
>>> If you apply to an interface the ACL# that does not exist, that is the
>>> same as if
>>> there was an ACL with just the "deny all" semantics, to avoid the
>>> perception
>>> that a given policy is enforced when it isn't - so I erred on the side
>>> of
>>> caution.
>>>
>>> The way to remove the ACL: you would ensure the ACL is not applied to
>>> the
>>> interface(s) first, then remove the ACL (or replace it with a different
>>> policy in-
>>> place).
>>>
>>> Alternatively, you can just replace the existing ACL in-place with
>>> "permit
>>> any"
>>> for IPv4 and IPv6 - this way you explicitly state that there is a policy
>>> to permit
>>> all the traffic.
>>>
>>> I've been bitten myself and seen several times in my career when an
>>> applied
>>> but non-existent ACL caused problems later on, in the worst possible
>>> moment. The current behaviour IMHO makes the config discrepancy clear -
>>> what do you think ?
>>>
>>> --a
>>>
>>> On 6/9/17, Marco Varlese <marco.varl...@suse.com> wrote:
>>> > Hi,
>>> >
>>> > I am trying the ACL functionality and I found a "strange" behaviour.
>>> >
>>> > The steps I follow to use an ACL are:
>>> > * I create an ACL to deny SSH traffic between VMs (via the
>>> 'acl_add_replace'
>>> > function)
>>> > * Set that ACL to the interfaces involved (via the
>>> > 'acl_interface_set_acl_list'
>>> > function)
>>> >
>>> > After performing the 

Re: [vpp-dev] Bind / Unbind of ACL

[Luke, Chris]

Would it make sense to have a flag on the interface (or globally), set when 
applying the ACL, that indicates the desired behavior when the ACL is empty or 
non-existent? At the moment to me it seems logical that this is the same 
behavior as when matching falls off the end of the ACL.

Chris.

> -Original Message-
> From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On
> Behalf Of Andrew ?? Yourtchenko
> Sent: Friday, June 9, 2017 7:53
> To: Marco Varlese 
> Cc: vpp-dev@lists.fd.io
> Subject: Re: [vpp-dev] Bind / Unbind of ACL
> 
> Hi Marco,
> 
> Yes, this works as expected, assuming after deletion *all* the traffic is
> denied, rather than just the SSH traffic.
> 
> If you apply to an interface the ACL# that does not exist, that is the same 
> as if
> there was an ACL with just the "deny all" semantics, to avoid the perception
> that a given policy is enforced when it isn't - so I erred on the side of 
> caution.
> 
> The way to remove the ACL: you would ensure the ACL is not applied to the
> interface(s) first, then remove the ACL (or replace it with a different 
> policy in-
> place).
> 
> Alternatively, you can just replace the existing ACL in-place with "permit 
> any"
> for IPv4 and IPv6 - this way you explicitly state that there is a policy to 
> permit
> all the traffic.
> 
> I've been bitten myself and seen several times in my career when an applied
> but non-existent ACL caused problems later on, in the worst possible
> moment. The current behaviour IMHO makes the config discrepancy clear -
> what do you think ?
> 
> --a
> 
> On 6/9/17, Marco Varlese  wrote:
> > Hi,
> >
> > I am trying the ACL functionality and I found a "strange" behaviour.
> >
> > The steps I follow to use an ACL are:
> > * I create an ACL to deny SSH traffic between VMs (via the
> 'acl_add_replace'
> > function)
> > * Set that ACL to the interfaces involved (via the
> > 'acl_interface_set_acl_list'
> > function)
> >
> > After performing the above steps the traffic was correctly being blocked.
> >
> > However, when I decided to enable the SSH traffic again, I simply
> > deleted the ACL (via the 'acl_del' function) with the consequence
> > though that the traffic was still being denied.
> >
> > Is this behaviour correct?
> > If so what would be the right way to unset hence disable a given ACL
> > from an interface (or multiple)?
> >
> >
> > Thanks,
> > Marco
> >
> > ___
> > vpp-dev mailing list
> > vpp-dev@lists.fd.io
> > https://lists.fd.io/mailman/listinfo/vpp-dev
> ___
> vpp-dev mailing list
> vpp-dev@lists.fd.io
> https://lists.fd.io/mailman/listinfo/vpp-dev

___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] VPP/How To Build The Sample Plugin

[Luke, Chris]

It should be possible to set the shm permissions such that vpp_api_test can be 
run as a non-privileged user; that being the case, don’t use the vppctl wrapper 
script, just invoke vat directly.

Note I’ve not tested this in a while; but we did make it possible last year 
iirc.

Chris.

From: Burt Silverman [mailto:bur...@gmail.com]
Sent: Friday, June 2, 2017 17:54
To: Damjan Marion (damarion) <damar...@cisco.com>; Dave Barach 
<d...@barachs.net>
Cc: Kinsella, Ray <ray.kinse...@intel.com>; Luke, Chris 
<chris_l...@cable.comcast.com>; Alessio Silvestro <ale.silver...@gmail.com>; 
vpp-dev <vpp-dev@lists.fd.io>
Subject: Re: [vpp-dev] VPP/How To Build The Sample Plugin

OK, I figured out how to patch code to add a vat_plugin_path option to 
/etc/vpp/startup.conf, but that was not the answer to the immediate issue, 
regarding my failure to get output from "show pci" under vppctl, when running 
from /home/burt/vpp/build-root/install-vpp-native/vpp/bin.
The issue is that vppctl wants to run a command in this directory as sudo. The 
command is not found because of sudo. There are two fixes in addition to 
building and installing packages:
1. Copy the program vpp_api_test from the aforementioned directory to /usr/bin.
The problem with this approach is that you have to know each time you build 
whether you have changed vpp_api_test and hence need to recopy it to /usr/bin.
2. Use sudoedit to add your bin directory (like 
/home/burt/vpp/build-root/install-vpp-native/vpp/bin) to the secure_path in the 
/etc/sudoers file.
Then  you are good for as long as you do not change the location of your 
tree.
Forgive me for hijacking this sample vpp-plugin thread for a slightly different 
discussion.
Perhaps someone can let me know if this appears usable, or close to usable, or 
far!

[burt@localhost ~/vpp/src/vpp]$git diff .
diff --git a/src/vpp/vnet/main.c b/src/vpp/vnet/main.c
index ade32aa..1bc190f 100644
--- a/src/vpp/vnet/main.c
+++ b/src/vpp/vnet/main.c
@@ -20,6 +20,7 @@
 #include 
 #include 
 #include 
+#include "vat/vat.h"


 static void
@@ -162,6 +163,11 @@ main (int argc, char *argv[])
  if (i < (argc - 1))
vlib_plugin_path = argv[++i];
}
+  else if (!strncmp (argv[i], "vat_plugin_path", 15))
+   {
+ if (i < (argc - 1))
+   vat_plugin_path = argv[++i];
+   }
   else if (!strncmp (argv[i], "heapsize", 8))
{
  sizep = (u8 *) argv[i + 1];
@@ -252,6 +258,16 @@ plugin_path_config (vlib_main_t * vm, unformat_input_t * in

 VLIB_CONFIG_FUNCTION (plugin_path_config, "plugin_path");

+static clib_error_t *
+vat_plugin_path_config (vlib_main_t * vm, unformat_input_t * input)
+{
+  clib_error_t *error;
+
+  error = plugin_path_config (vm, input);
+  return error;
+}
+VLIB_CONFIG_FUNCTION (vat_plugin_path_config, "vat_plugin_path");
+
 void vl_msg_api_post_mortem_dump (void);
 void elog_post_mortem_dump (void);

Burt


On Thu, Jun 1, 2017 at 1:43 PM, Burt Silverman 
<bur...@gmail.com<mailto:bur...@gmail.com>> wrote:
Oh, man, that (referring to my last post) is some tricky stuff. My reaction 
reminds me of one of my colleagues reaction years ago when I created some 
firmware that would only fit in flash by using an AIX C compiler optimization 
trick that discarded uncalled functions. After I told him the solution he 
required, he exclaimed loudly, "OH, I THINK IT STINKS." Now, one of my issues, 
not the primary question, but the "stinks" issue, is that there are at least 
two unique load_one_plugin functions that behave differently but both show up 
in the log as "load_one_plugin."
OK, the function in vlib/unix/plugin.c will not accept my vpp_api_test_plugins 
even though I have them in the plugin path I configured in 
/etc/vpp/startup.conf, because they do not have section 
vlib_plugin_registration in the ELF. I think there is a separate 
vat_plugin_path that is hard coded to /usr/lib/vpp_api_test_plugins in 
vpp/api/plugin.c. How can I configure this so that I can have these vat plugins 
in $TOP/build-root/install-vpp-native/vpp/lib64/vpp_api_test_plugins? As I have 
mentioned earlier, I am trying to come up with a developer work flow that does 
not require building and installing packages.
Burt

On Wed, May 31, 2017 at 3:56 PM, Burt Silverman 
<bur...@gmail.com<mailto:bur...@gmail.com>> wrote:
Damjan,
I have a related question, but it does not involve the sample-plugin. I wish to 
"make build-release" and then adjust my plugin path in /etc/vpp/startup.conf to 
use the plugin directories underneath 
TOP/build-root/install-vpp-native/vpp/lib64. Well it seems that the plugins in 
directory vpp_plugins are acceptable, but the ones in vpp_api_test_plugins are 
not. I end up with a result like:

[burt@localhost ~]$source ./vpp.sh
[sudo] password for burt:
vlib_plugin_early

Re: [vpp-dev] VPP Node Debug

[Luke, Chris]

printk() is typically a kernel thing, no? This isn’t kernel code. 

If you just want stuff on the console when running in a debugger, or 
interactively, clib_warning() may be what you are looking for.

Chris.


From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On 
Behalf Of Alessio Silvestro
Sent: Thursday, June 1, 2017 10:35
To: vpp-dev@lists.fd.io
Subject: [vpp-dev] VPP Node Debug

Hi all,

I am using this code "https://gerrit.fd.io/r/#/c/6721/; to in order to enable 
an external process to receive UDP packets.

I tried to use printk -- including module.h in the c file.

When I compile VPP with:

TOPDIR/vpp make build-release

I got the following error

fatal error: linux/module.h: No such file or directory
compilation terminated.

Do you have any idea why?

Is there a better way to debug the code of a node in VPP?

Thanks,
Alessio
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] VPP/How To Build The Sample Plugin

[Luke, Chris]

Wishes often come true when you turn them into patches. :)

Chris.

From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On 
Behalf Of Burt Silverman
Sent: Saturday, May 27, 2017 10:33
To: Kinsella, Ray 
Cc: Alessio Silvestro ; vpp-dev 
Subject: Re: [vpp-dev] VPP/How To Build The Sample Plugin

Thanks, Ray, this is exactly what I needed, by coincidence. I wish your item 2. 
was placed commented out and almost word for word into the standard 
$TOPDIR/src/vpp/conf/startup.conf -- that would make things self documenting.
Burt

On Sat, May 27, 2017 at 8:30 AM, Kinsella, Ray 
> wrote:
So there is an easier way

1. make -C build-root PLATFORM=vpp TAG=vpp sample-plugin-install

2. adjusting the plugin path depending on where the VPP src is, add the 
following to your startup.conf

plugins
{
path 
/root/src/vpp/build-root/install-vpp-native/sample-plugin/lib64/vpp_plugins/:/root/src/vpp/build-root/install-vpp_debug-native/vpp/lib64/vpp_plugins
}

Ray K


On 26/05/2017 12:53, Alessio Silvestro wrote:
Hi all,

I am trying to build the sample vpp-engine plug-in as explained here
(https://wiki.fd.io/view/VPP/How_To_Build_The_Sample_Plugin).

I already tested my vpp installation, for instance it works when I
created a Source NAT.

I downloaded the most updated version of the sample-plugin and run the
following commands:

   sudo sh
   cd /usr/share/doc/vpp/examples
   cd /tmp/sample-plugin
   libtoolize
   aclocal
   autoconf
   autoheader

ERROR 1:autoheader: error: AC_CONFIG_HEADERS not found in 
configure.ac
>

   automake --add-missing
   chmod +x configure
   vpp_plugin_configure

ERROR 2:vpp_plugin_configure: command not found


So, first I have an error from the command autoheader.

Second, I do not have the command vpp_plugin_configure.

Any hints?

Best regards,
Alessio


___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] Some error in L3VPN

[Luke, Chris]

That specific trace formatting error was fixed on master earlier today. Could 
you give it a try?

Chris.

From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On 
Behalf Of ???
Sent: Wednesday, May 24, 2017 22:03
To: vpp-dev@lists.fd.io
Subject: [vpp-dev] Some error in L3VPN


Hi guys,

There is a ping failed occured in L3vpn,and the trace had incorrect print 
information below:
DBGvpp# show trace
 CLIB unknown format `%#' x label 0 eos 1024
17:23:38:439098: lookup-mpls-dst
 fib-index:0 hdr:[1023:85:0:eos] load-balance:29
17:23:38:439159: ip4-mpls-label-disposition
  disp:0
17:23:38:439198: lookup-ip4-dst
 fib-index:1 addr:63.1.94.231 load-balance:9
17:23:38:439325: ip4-drop
IP6_HOP_BY_HOP_OPTIONS: 85.93.65.0 -> 63.1.94.231
  version 0, header length 0
  tos 0x3f, ttl 69, length 61781, checksum 0x0054 (should be 0x)
  fragment id 0x0002 offset 35320, flags CONGESTION
17:23:38:439391: error-drop
  ip4-input: ip4 adjacency drop

 What should I do to solve this?

 Thanks,
 xyxue

___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] Running VPP in a non-default network namespace

[Luke, Chris]

It may be extreme, but perhaps detect if any namespace is configured (whether 
we’re running in a namespace or in the default) and then fall back to the 
safest behavior (with a note in the startup output saying so).

Is it reasonable? Could add a flag that always binds every device found for 
people who explicitly want the current behavior.

I suppose if we’re in the default ns we could iterate every other ns to ignore 
ports mapped to them but it feels fragile somehow.

Chris.


On 5/24/17, 04:33, "Damjan Marion" <dmarion.li...@gmail.com> wrote:

Yeah, I’m aware of this issue but I don’t have any good idea how to address 
it.

We can disable unbind if we detect that we are running inside namespace, 
but that will not fix problem in opposite direction, when specific interface is 
mapped to namespace and vpp running in global.

any ideas?


> On 24 May 2017, at 05:14, Luke, Chris <chris_l...@comcast.com> wrote:
> 
> Ah, I see what you mean.
> 
> The issue being that inside the namespace it cannot query the state of 
the Linux-bound interface (whether up/down) since the namespace doesn't have 
the interface. The behavior falls-back to slurping up all ports Linux says 
doesn't exist; this is at least in part to make sure it captures ports already 
unbound from the kernel.
> 
> I'd agree this is not acting in the manner of least surprise. Damjan is 
the best person to comment on this and whether a more consistent behavior can 
be crafted. One simple approach might be to detect we're in a namespace and 
only bind detected-down interfaces and explicitly provided PCI ID's.
> 
> Chris.
> 
>> -Original Message-
>> From: Renato Westphal [mailto:ren...@opensourcerouting.org]
>> Sent: Tuesday, May 23, 2017 22:01
>> To: Luke, Chris <chris_l...@cable.comcast.com>
>> Cc: vpp-dev@lists.fd.io
>> Subject: Re: [vpp-dev] Running VPP in a non-default network namespace
>> 
>> Thank you Chris, disabling the DPDK plugin did the trick for me. My plan 
is to
>> use veth/AF_PACKET interfaces only.
>> 
>> I think I found a small problem in VPP though.
>> 
>> When you start VPP and the 'dpdk' section of the configuration file is 
empty,
>> DPDK snatches all physical interfaces that are administratively down.
>> 
>> This works ok when running VPP in the default netns. But when you run VPP
>> in a non-default netns, all physical interfaces are snatched regardless 
of their
>> administrative status.
>> 
>> Could you confirm if this is a bug? This inconsistent behavior was a 
source of
>> confusion to me.
>> 
>> Best Regards,
>> Renato.
>> 
>> On Tue, May 23, 2017 at 9:00 PM, Luke, Chris <chris_l...@comcast.com>
>> wrote:
>>> If you're using DPDK and all your physical interfaces are DPDK-capable, 
then
>> it's snatching the PCI device away from Linux. This has nothing to do 
with
>> Linux namespaces; ns can't prevent it from happening because it's 
working at
>> a different layer in the stack. The point of DPDK is to go straight to 
the
>> hardware.
>>> 
>>> The only time Linux namespace interactions come into play with VPP is
>>> with interfaces like 'tap' and 'host' (aka af_packet) which use
>>> syscalls to manipulate Linux network state (create ports, listen on a
>>> raw socket, etc) or anything else that uses Linux networking (console
>>> TCP connections, etc)
>>> 
>>> You can either limit which PCI devices VPP asks DPDK to bind to in the 
dpdk
>> section of the config:
>>> 
>>> dpdk {
>>>  dev 
>>>  ...
>>> }
>>> 
>>> or, if only inter-ns is what you want to do, just disable DPDK 
altogether:
>>> 
>>> plugins {
>>>  plugin dpdk_plugin.so { disable }
>>> }
>>> 
>>> Chris.
>>> 
>>> 
>>>> -Original Message-
>>>> From: vpp-dev-boun...@lists.fd.io
>>>> [mailto:vpp-dev-boun...@lists.fd.io] On Behalf Of Renato Westphal
>>>> Sent: Tuesday, May 23, 2017 19:38
>>>> To: vpp-dev@lists.fd.io
>>>> Subject: [vpp-dev] Running VPP in a non-default network namespace
>>>> 
>>>> Hi all,
>>>> 
>>>> For learning purposes, I'm trying to set up a test topology using
>>>> multiple instances of VPP running in differen

Re: [vpp-dev] Running VPP in a non-default network namespace

[Luke, Chris]

Ah, I see what you mean.

The issue being that inside the namespace it cannot query the state of the 
Linux-bound interface (whether up/down) since the namespace doesn't have the 
interface. The behavior falls-back to slurping up all ports Linux says doesn't 
exist; this is at least in part to make sure it captures ports already unbound 
from the kernel.

I'd agree this is not acting in the manner of least surprise. Damjan is the 
best person to comment on this and whether a more consistent behavior can be 
crafted. One simple approach might be to detect we're in a namespace and only 
bind detected-down interfaces and explicitly provided PCI ID's.

Chris.

> -Original Message-
> From: Renato Westphal [mailto:ren...@opensourcerouting.org]
> Sent: Tuesday, May 23, 2017 22:01
> To: Luke, Chris <chris_l...@cable.comcast.com>
> Cc: vpp-dev@lists.fd.io
> Subject: Re: [vpp-dev] Running VPP in a non-default network namespace
> 
> Thank you Chris, disabling the DPDK plugin did the trick for me. My plan is to
> use veth/AF_PACKET interfaces only.
> 
> I think I found a small problem in VPP though.
> 
> When you start VPP and the 'dpdk' section of the configuration file is empty,
> DPDK snatches all physical interfaces that are administratively down.
> 
> This works ok when running VPP in the default netns. But when you run VPP
> in a non-default netns, all physical interfaces are snatched regardless of 
> their
> administrative status.
> 
> Could you confirm if this is a bug? This inconsistent behavior was a source of
> confusion to me.
> 
> Best Regards,
> Renato.
> 
> On Tue, May 23, 2017 at 9:00 PM, Luke, Chris <chris_l...@comcast.com>
> wrote:
> > If you're using DPDK and all your physical interfaces are DPDK-capable, then
> it's snatching the PCI device away from Linux. This has nothing to do with
> Linux namespaces; ns can't prevent it from happening because it's working at
> a different layer in the stack. The point of DPDK is to go straight to the
> hardware.
> >
> > The only time Linux namespace interactions come into play with VPP is
> > with interfaces like 'tap' and 'host' (aka af_packet) which use
> > syscalls to manipulate Linux network state (create ports, listen on a
> > raw socket, etc) or anything else that uses Linux networking (console
> > TCP connections, etc)
> >
> > You can either limit which PCI devices VPP asks DPDK to bind to in the dpdk
> section of the config:
> >
> > dpdk {
> >   dev 
> >   ...
> > }
> >
> > or, if only inter-ns is what you want to do, just disable DPDK altogether:
> >
> > plugins {
> >   plugin dpdk_plugin.so { disable }
> > }
> >
> > Chris.
> >
> >
> >> -Original Message-
> >> From: vpp-dev-boun...@lists.fd.io
> >> [mailto:vpp-dev-boun...@lists.fd.io] On Behalf Of Renato Westphal
> >> Sent: Tuesday, May 23, 2017 19:38
> >> To: vpp-dev@lists.fd.io
> >> Subject: [vpp-dev] Running VPP in a non-default network namespace
> >>
> >> Hi all,
> >>
> >> For learning purposes, I'm trying to set up a test topology using
> >> multiple instances of VPP running in different network namespaces.
> >>
> >> I see that there's documentation showing how to use VPP as a router
> >> between namespaces, but in all examples I found VPP is always running
> >> in the default network namespace.
> >>
> >> If I try to run VPP in a non-default network namespace, something
> >> weird
> >> happens: all interfaces from the default netns disappear!
> >>
> >> Does anyone know what might be the cause of this?
> >>
> >> I'm using the official vagrant VM (Ubuntu 16.04) and VPP v17.04.1,
> >> and I can see that the same problem occurs on master and on older
> releases as well.
> >>
> >> More details about the issue below.
> >>
> >> 1 - My VPP config:
> >> # cat /etc/vpp/startup.conf
> >> unix {
> >>   nodaemon
> >>   log /tmp/vpp.log
> >>   full-coredump
> >> }
> >>
> >> api-trace {
> >>   on
> >> }
> >>
> >> api-segment {
> >>   gid vpp
> >> }
> >>
> >> 2 - VPP running ok in the default netns:
> >> # vpp -c /etc/vpp/startup.conf
> >> vlib_plugin_early_init:356: plugin path /usr/lib/vpp_plugins
> >> load_one_plugin:184: Loaded plugin: acl_plugin.so (Access Control
> >> Lists)
> >> load_one_plugin:184: Loaded plugin: dpdk_plugin.so (Data Plane
> >> Development Kit (DPDK))
> >> l

Re: [vpp-dev] Running VPP in a non-default network namespace

[Luke, Chris]

If you're using DPDK and all your physical interfaces are DPDK-capable, then 
it's snatching the PCI device away from Linux. This has nothing to do with 
Linux namespaces; ns can't prevent it from happening because it's working at a 
different layer in the stack. The point of DPDK is to go straight to the 
hardware.

The only time Linux namespace interactions come into play with VPP is with 
interfaces like 'tap' and 'host' (aka af_packet) which use syscalls to 
manipulate Linux network state (create ports, listen on a raw socket, etc) or 
anything else that uses Linux networking (console TCP connections, etc)

You can either limit which PCI devices VPP asks DPDK to bind to in the dpdk 
section of the config:

dpdk {
  dev 
  ...
}

or, if only inter-ns is what you want to do, just disable DPDK altogether:

plugins {
  plugin dpdk_plugin.so { disable }
}

Chris.


> -Original Message-
> From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On
> Behalf Of Renato Westphal
> Sent: Tuesday, May 23, 2017 19:38
> To: vpp-dev@lists.fd.io
> Subject: [vpp-dev] Running VPP in a non-default network namespace
> 
> Hi all,
> 
> For learning purposes, I'm trying to set up a test topology using multiple
> instances of VPP running in different network namespaces.
> 
> I see that there's documentation showing how to use VPP as a router
> between namespaces, but in all examples I found VPP is always running in
> the default network namespace.
> 
> If I try to run VPP in a non-default network namespace, something weird
> happens: all interfaces from the default netns disappear!
> 
> Does anyone know what might be the cause of this?
> 
> I'm using the official vagrant VM (Ubuntu 16.04) and VPP v17.04.1, and I can
> see that the same problem occurs on master and on older releases as well.
> 
> More details about the issue below.
> 
> 1 - My VPP config:
> # cat /etc/vpp/startup.conf
> unix {
>   nodaemon
>   log /tmp/vpp.log
>   full-coredump
> }
> 
> api-trace {
>   on
> }
> 
> api-segment {
>   gid vpp
> }
> 
> 2 - VPP running ok in the default netns:
> # vpp -c /etc/vpp/startup.conf
> vlib_plugin_early_init:356: plugin path /usr/lib/vpp_plugins
> load_one_plugin:184: Loaded plugin: acl_plugin.so (Access Control Lists)
> load_one_plugin:184: Loaded plugin: dpdk_plugin.so (Data Plane
> Development Kit (DPDK))
> load_one_plugin:184: Loaded plugin: flowperpkt_plugin.so (Flow per Packet)
> load_one_plugin:184: Loaded plugin: gtpu_plugin.so (GTPv1-U)
> load_one_plugin:184: Loaded plugin: ila_plugin.so (Identifier-locator
> addressing for IPv6)
> load_one_plugin:184: Loaded plugin: ioam_plugin.so (Inbound OAM)
> load_one_plugin:114: Plugin disabled (default): ixge_plugin.so
> load_one_plugin:184: Loaded plugin: lb_plugin.so (Load Balancer)
> load_one_plugin:184: Loaded plugin: libsixrd_plugin.so (IPv6 Rapid
> Deployment on IPv4 Infrastructure (RFC5969))
> load_one_plugin:184: Loaded plugin: memif_plugin.so (Packet Memory
> Interface (experimetal))
> load_one_plugin:184: Loaded plugin: snat_plugin.so (Network Address
> Translation)
> load_one_plugin:63: Loaded plugin:
> /usr/lib/vpp_api_test_plugins/dpdk_test_plugin.so
> load_one_plugin:63: Loaded plugin:
> /usr/lib/vpp_api_test_plugins/snat_test_plugin.so
> load_one_plugin:63: Loaded plugin:
> /usr/lib/vpp_api_test_plugins/lb_test_plugin.so
> load_one_plugin:63: Loaded plugin:
> /usr/lib/vpp_api_test_plugins/flowperpkt_test_plugin.so
> load_one_plugin:63: Loaded plugin:
> /usr/lib/vpp_api_test_plugins/udp_ping_test_plugin.so
> load_one_plugin:63: Loaded plugin:
> /usr/lib/vpp_api_test_plugins/acl_test_plugin.so
> load_one_plugin:63: Loaded plugin:
> /usr/lib/vpp_api_test_plugins/ioam_export_test_plugin.so
> load_one_plugin:63: Loaded plugin:
> /usr/lib/vpp_api_test_plugins/ioam_trace_test_plugin.so
> load_one_plugin:63: Loaded plugin:
> /usr/lib/vpp_api_test_plugins/vxlan_gpe_ioam_export_test_plugin.so
> load_one_plugin:63: Loaded plugin:
> /usr/lib/vpp_api_test_plugins/gtpu_test_plugin.so
> load_one_plugin:63: Loaded plugin:
> /usr/lib/vpp_api_test_plugins/ioam_vxlan_gpe_test_plugin.so
> load_one_plugin:63: Loaded plugin:
> /usr/lib/vpp_api_test_plugins/ioam_pot_test_plugin.so
> vlib_pci_bind_to_uio: Skipping PCI device :00:03.0 as host interface
> enp0s3 is up
> vlib_pci_bind_to_uio: Skipping PCI device :00:08.0 as host interface
> enp0s8 is up
> vlib_pci_bind_to_uio: Skipping PCI device :00:09.0 as host interface
> enp0s9 is up
> vpp[1180]: dpdk_ipsec_process:239: not enough Cryptodevs, default to
> OpenSSL IPsec
> vpp[1180]: dpdk_lib_init:182: DPDK drivers found no ports...
> vpp[1180]: dpdk_lib_init:186: DPDK drivers found 0 ports...
> vpp[1180]: received signal SIGINT, PC 0x7fad6a98ea37 DPDK physical memory
> layout:
> Segment 0: phys:0x3400, len:8388608, virt:0x7facdbc0, socket_id:0,
> hugepage_sz:2097152, nchannel:0, nrank:0 Segment 1: phys:0x7080,
> len:2097152, virt:0x7facdb80, socket_id:0, hugepage_sz:2097152,
> 

Re: [vpp-dev] The Case Of the Missing API Definition

[Luke, Chris]

It's disappointing that no heads-up was posted to the list. That's the bare 
minimum needed so that downstream consumers are aware of a material change 
before it bites them, especially if they track master.

I'm the last person to suggest we need rules; I hope simple courtesy can 
prevent this in future. :)

Chris.


> -Original Message-
> From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On
> Behalf Of Jon Loeliger
> Sent: Tuesday, May 23, 2017 13:20
> To: vpp-dev 
> Subject: [vpp-dev] The Case Of the Missing API Definition
> 
> Folks,
> 
> I was causally walking down Update VPP Master Lane when I was suddenly
> attacked from behind by a case of the missing API call!
> I read vpp-dev mail daily, and I watch the Gerrit fervently, so I was pretty
> sure I wouldn't be blind-sided by this sort of Silent Gotcha.
> 
> But there was no mistaking it:  My API call bridge_domain_sw_if_details was
> gone.  And only two days ago too!  I was shocked.  Horrified, even.
> I knew the next build my code would fail.  There would be no updating to
> Top-Of-Tree VPP today.
> 
> What would I tell my boss?  *My* code was broken?  Surely you wouldn't
> expect me to fall on the "I'm sorry.  My code is broken." sword.  My own
> code!  Surely I could blame someone else?  I mean, what if there were some
> email from the developers?  A little heads-up that the API was on The Out
> and would soon go the way of Sonny Bono.  But no, no, there wasn't even a
> hint.
> 
> I was going to have to admit I failed to see this coming in the Gerrit 
> reviews.
> 
> And now, without even lunch, I would have to deduce what data used to be
> in that API call, and how it was cached in my VPP interface library, and yes, 
> I'd
> have to scurry to find where that data was located now.
> 
> But how?  How could this be?  I lamented still.  I just knew last time *I*
> wanted an API interface change, I spent a week discussing it on the list, and,
> after deliberation a-plenty, a new API was needed, and then later, in fact
> after a complete release cycle, we could begin to discuss how the old API call
> might be deprecated and finally removed.  I longed for the day that we
> would finally make progress, content in the knowledge that we had not, in
> fact, blind-sided anyone with our API deprecation plan.
> 
> But those days are behind us now, and the future comes at us plenty fast.
> Commits are committed, and progress is progressed.  My scars are healing,
> and after all this water under and through the bridge, I have learned now to
> just laugh at these situations.
> 
> Ah, to be young again, and not have wasted my youth on backward
> compatibility and cheap Scotch.
> 
> jdl
> ___
> vpp-dev mailing list
> vpp-dev@lists.fd.io
> https://lists.fd.io/mailman/listinfo/vpp-dev

___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev