Re: [EXTERNAL] [vpp-dev] Coverity errors nag-o-gram

And in case it’s not obvious, the scanning tool had a holiday hiatus, but I got it back on its feet a week or so ago. Chris. From: vpp-dev@lists.fd.io on behalf of Ole Troan Date: Tuesday, January 18, 2022 at 06:16 To: Neale Ranns , Pablo Camarillo (pcamaril) , Radu Nicolau , Steven Luong (

Re: [EXTERNAL] Re: [vpp-dev] Multi-threading locks and synchronization

Really depends on what you need it to do, which I may have missed. Why do you need any synchronization at all? Chris From: vpp-dev@lists.fd.io on behalf of satish amara Date: Monday, July 12, 2021 at 23:59 To: vpp-dev@lists.fd.io Subject: Re: [EXTERNAL] Re: [vpp-dev] Multi-threading locks a

Re: [EXTERNAL] Re: [vpp-dev] Multi-threading locks and synchronization

Grossly simplified explanation: Because of how VPP works, all packets are processed to completion on every vector (there may be exceptions, but it’s not typical, VPP really does not want to hang on to packets across cycles). Once a vector has been completed, there’s a barrier lock to allow main

Re: [EXTERNAL] [vpp-dev] Source File Paths present in VPP shared library folders

These are likely debugging symbols. Run “file” on the file to see if it says something similar to “with debug_info, not stripped” on the end. If you intend to be building packages for distribution you can always locally amend the build process to “strip” the object files before packaging, if thi

Re: [EXTERNAL] Re: [vpp-dev] VPP Emacs Lisp evolution to P4

Hi Hemant, Do you plan to open source and maintain this code generator? Chris. From: vpp-dev@lists.fd.io On Behalf Of hemant via lists.fd.io Sent: Wednesday, May 5, 2021 12:09 To: hem...@mnkcg.com; vpp-dev@lists.fd.io Subject: [EXTERNAL] Re: [vpp-dev] VPP Emacs Lisp evolution to P4 I don't k

Re: [EXTERNAL] Re: [vpp-dev] vpp hang on

As Andrew says, vppctl is not ideal for this purpose. Your GDB trace looks like it was vppctl itself, and it's stuck waiting on connect() - which means the far end, VPP, did not accept() the connection. My immediate reaction would be to check netstat to see if there's lots of old unix sockets s

Re: [EXTERNAL] [vpp-dev] New Committer Proposal

+1 -Original Message- From: vpp-dev@lists.fd.io On Behalf Of Damjan Marion via lists.fd.io Sent: Wednesday, March 31, 2021 13:58 To: vpp-dev Cc: Zhang, Roy Fan Subject: [EXTERNAL] [vpp-dev] New Committer Proposal Dear VPP Committers, I would like to propose Roy Fan Zhang from Intel

Re: [EXTERNAL] Re: [vpp-dev] Issue with cloning repo on VM

Rajesh, It looks like a local system issue, nothing to do with git or gerrit per se. Your system is tell you it’s not letting you create that file. You should investigate that. I believe it’s out of scope for this list I’m afraid. Chris. From: vpp-dev@lists.fd.io On Behalf Of Rajesh Dawadi vi

Re: [EXTERNAL] [vpp-dev] RFC: Enabling Gerrit Auto-Abandon job on VPP master

+1 I used to do this manually, in effect, though I’ve been less active the past while which probably accounts for the growth! FWIW, I usually performed it on an approximate 60 day nudge and 90 day abandon, about once a month, schedule. I did similar with JIRA but less frequently. I felt the wa

Re: [EXTERNAL] [vpp-dev] Check running status of vpp

It is odd that the filesystem entry for the CLI socket would exist but it says “connection refused”. Any log messages from VPP complaining about not being able to create the socket? I wonder if the filesystem entry is a remnant from a previous session that was not cleaned up. Chris. From: vpp

Re: [EXTERNAL] Re: [vpp-dev] vppctl fails from within the application (system cmd returns 256)

On this line in the trace: [pid 2536742] socket(AF_UNIX, SOCK_STREAM, 0) = 0 It says it’s returning file descriptor 0 for the socket. Similarly other file opens and subsequent closes are using descriptor 0. 0 is normally stdin. Are stdin & out closed? That could cause all kinds of strange issue

Re: [EXTERNAL] [vpp-dev] vppctl fails from within the application (system cmd returns 256)

Is vppctl in the system path? Otherwise fully specify the path to the vppctl binary in those system calls. Chris. From: vpp-dev@lists.fd.io On Behalf Of Aniket Pugaonkar Sent: Monday, November 16, 2020 12:41 To: vpp-dev@lists.fd.io Subject: [EXTERNAL] [vpp-dev] vppctl fails from within the appl

Re: [vpp-dev] Can I submit commit to vpp GitHub repo instead of gerrit?

Like Damjan said, we use Gerrit. Those GitHub PR’s won’t be reviewed. I thought it used to say it was only a mirror, but doesn’t now. GitHub I think now allows us remove the option to create PR’s, perhaps we should make that so. If you want to submit patches for review, details at https://wiki.

Re: [vpp-committers] [vpp-dev] VPP committers: VPP PTL vote

Is it too late to change my vote? :) (kidding) Chris. -Original Message- From: vpp-committ...@lists.fd.io On Behalf Of Damjan Marion via lists.fd.io Sent: Monday, September 28, 2020 07:48 To: Benoit Ganne (bganne) Cc: Dave Barach (dbarach) ; vpp-committ...@lists.fd.io; vpp-dev@lists.

Re: [vpp-dev] [EXTERNAL] [vpp-committers] VPP committers: VPP PTL vote

+1 From: vpp-committ...@lists.fd.io On Behalf Of Dave Barach via lists.fd.io Sent: Friday, September 25, 2020 15:14 To: vpp-committ...@lists.fd.io Cc: vpp-dev@lists.fd.io Subject: [EXTERNAL] [vpp-committers] VPP committers: VPP PTL vote Folks, The self-nomination period closed yesterday. We ha

Re: [EXTERNAL] Re: [vpp-dev] Please look at coverity defects in preparation for VPP 20.09 before Monday

I’m dusting off dim recollection.. and it’s further complicated by the scan service (which is the free Coverity for open source projects that we use) being slightly different from the commercial offering. At the time, I feel I concluded that Coverity models could override macro definitions but t

Re: [EXTERNAL] Re: [vpp-dev] Please look at coverity defects in preparation for VPP 20.09 before Monday

Nathan, Just a caveat; those Coverity comments do not always work – at least didn’t when we started using Coverity. They have plausibly improved things in the analyzer since but I have not seen that; I would be interested to see if it is effective once patches are merged and my twice daily subm

Re: [vpp-dev] How to see coverity logs

, but at a guess if the email address you used for signing up on Coverity does not match one in your github profile I could imagine it being confused. I would suggest not signing in with GitHub, personally. Chris. From: vpp-dev@lists.fd.io On Behalf Of Chris Luke Sent: Wednesday, September 2

Re: [vpp-dev] How to see coverity logs

The correct URL is https://scan.coverity.com/projects/fd-io-vpp (you missed a trailing p) but I am not sure how you would add it "to your github". It's just a web page. I also note that you're listed as a contributor, so you should have access to see the defects. Chris. From: vpp-dev@lists.fd

Re: [vpp-dev] VPP 20.05.1 tomorrow 15th July 2020

To clarify, committers are the only ones who can approve and merge changes, to any of the maintained branches. Any contributor can propose changes to any open branch, and a cherry-pick is just a proposed change that happens to be a (rebased) copy of another change. Chris. -Original Message

Re: [vpp-dev] Replacing master/slave nomenclature

It is subjective and contextualized. But in this case, if making the effort to correct a wrong, why stop half way? Chris. -Original Message- From: vpp-dev@lists.fd.io On Behalf Of Jerome Tollet via lists.fd.io Sent: Tuesday, July 14, 2020 12:37 To: Steven Luong (sluong) ; Dave Barach (

Re: [EXTERNAL] [vpp-dev] why define an unused var

With strict static analysis it should complain when return values go ignored. The canonical way to flag that this is intentional and avoid the warning is to cast the result to (void) however any optimizing compiler will correctly omit any storage of the result of an ((unused)) variable, so no bi

Re: [EXTERNAL] [vpp-dev] VPP release 20.05 is complete!

Brilliant, good job! -Original Message- From: vpp-dev@lists.fd.io On Behalf Of Andrew Yourtchenko Sent: Wednesday, May 27, 2020 17:28 To: vpp-dev Subject: [EXTERNAL] [vpp-dev] VPP release 20.05 is complete! Dear all, I am happy to announce that the release 20.05 is available on package

Re: [EXTERNAL] Re: [vpp-dev] VPP sequential policy command execution giving error

ts.fd.io<mailto:vpp-dev@lists.fd.io> mailto:vpp-dev@lists.fd.io>> On Behalf Of Chris Luke Sent: Tuesday, May 26, 2020 09:40 To: Chinmaya Aggarwal mailto:chinmaya.agar...@hsc.com>>; vpp-dev@lists.fd.io<mailto:vpp-dev@lists.fd.io> Subject: Re: [EXTERNAL] Re: [vpp-dev] VPP

Re: [EXTERNAL] Re: [vpp-dev] VPP sequential policy command execution giving error

the script you run stall for a second? Chris. From: vpp-dev@lists.fd.io On Behalf Of Chris Luke Sent: Tuesday, May 26, 2020 09:40 To: Chinmaya Aggarwal ; vpp-dev@lists.fd.io Subject: Re: [EXTERNAL] Re: [vpp-dev] VPP sequential policy command execution giving error You’ll get the banner if it

Re: [EXTERNAL] Re: [vpp-dev] VPP sequential policy command execution giving error

You’ll get the banner if it thinks it’s an interactive session. Roughly vppctl does this (I am paraphrasing): is_interactive = isatty(STDIN); … if (is_interactive) TERM = “vppctl”; … open telnet session to the CLI socket; pass the terminal information Then in VPP: is_interactive = (strcmp(TERM,

Re: [vpp-dev] Help with creating patch

Govind, Did you create a branch locally before making a commit? It looks like you tried to push to master which won't work. A typical workflow involves creating a local branch, making some changes and commits and then pushing to Gerrit. Also, I changed the email subject; you should really have

Re: [vpp-dev] vpp project committer nomination: Benoit Ganne

+1 -Original Message- From: vpp-dev@lists.fd.io On Behalf Of Dave Barach via lists.fd.io Sent: Tuesday, April 21, 2020 07:40 To: vpp-dev@lists.fd.io Subject: [EXTERNAL] [vpp-dev] vpp project committer nomination: Benoit Ganne Vpp project committers: please vote +1, 0, -1 on the mailto:v

Re: [EXTERNAL] Re: [vpp-dev] APPROVED: add Matt Smith as a vpp committer, subject to TSC approval this Thursday

Congratulations, and welcome! Chris From: vpp-dev@lists.fd.io On Behalf Of Matthew Smith via Lists.Fd.Io Sent: Monday, March 2, 2020 4:11 PM To: Dave Barach (dbarach) Cc: vpp-dev@lists.fd.io Subject: [EXTERNAL] Re: [vpp-dev] APPROVED: add Matt Smith as a vpp committer, subject to TSC approva

Re: [EXTERNAL] [vpp-dev] vpp project committers: formal vote to add Matt Smith as a vpp committer

+1 From: vpp-dev@lists.fd.io On Behalf Of d...@barachs.net Sent: Monday, March 2, 2020 9:16 AM To: vpp-dev@lists.fd.io Subject: [EXTERNAL] [vpp-dev] vpp project committers: formal vote to add Matt Smith as a vpp committer VPP committers, please vote +1, 0, -1 on adding Matt Smith (mgsm...@netg

Re: [EXTERNAL] Re: [vpp-dev] Wanted to use socket transport as VAT API ( not svm i.e shared memory default)

Vppctl uses a unix socket, yes, but it’s exactly the same as the TCP socket version of the CLI – it runs the TELNET protocol and does terminal-like IO with unstructured intended-for-humans content. There’s nothing special about it. Chris. From: vpp-dev@lists.fd.io On Behalf Of sastry.si...@gm

Re: [EXTERNAL] Re: [vpp-dev] Need info on memory-tracer

Satish, Tangential to the thread, but I maintain the CLI infrastructure. You had a crash disabling the CLI history? First command after starting VPP? Did you keep the backtrace from it? Any startup commands configured? It does not do that for me, so I am curious what corner case you have manage

Re: [EXTERNAL] [vpp-dev] Change to Gerrit

+1 From: vpp-dev@lists.fd.io On Behalf Of Paul Vinciguerra Sent: Wednesday, November 20, 2019 1:33 PM To: vpp-dev@lists.fd.io Subject: [EXTERNAL] [vpp-dev] Change to Gerrit How would the group feel about implementing something like [0], so that changes to the commit message don't trigger rebuil

Re: [EXTERNAL] [vpp-dev] Coverity run FAILED as of 2019-11-11 14:01:19 UTC

Looks like we were overdue for Coverity stalling, which it did a week or so ago. I've prodded it, but it may be a Coverity issue. Chris. -Original Message- From: vpp-dev@lists.fd.io On Behalf Of Noreply Jenkins Sent: Monday, November 11, 2019 9:01 AM To: vpp-dev@lists.fd.io; e...@cisco.

Re: [vpp-dev] Coverity run FAILED as of 2019-10-22 14:00:19 UTC

You'll be glad to hear that it did, indeed, clear Coverity up. :) Chris -Original Message- From: Benoit Ganne (bganne) Sent: Tuesday, October 22, 2019 12:32 To: Luke, Chris ; Damjan Marion Cc: vpp-dev@lists.fd.io Subject: [EXTERNAL] RE: [vpp-dev] Coverity run FAILED as of 2019-10-22 14:

Re: [vpp-dev] Coverity run FAILED as of 2019-10-22 14:00:19 UTC

Redefine the macro for the Coverity case, so Coverity doesn't complain. It just needs to be representative of the execution you expect to happen. -Original Message- From: vpp-dev@lists.fd.io On Behalf Of Benoit Ganne (bganne) via Lists.Fd.Io Sent: Tuesday, October 22, 2019 11:46 AM To:

Re: [EXTERNAL] [vpp-dev] [review-request] vlib: cli support ctrl-w to erase left word #vpp

Hi Hiroki, Review comments posted. Thanks for this. I’m shocked that I managed to miss adding ^W when I added command line editing! Chris. From: on behalf of Hiroki Shirokura Date: Sunday, August 25, 2019 at 2:42 AM To: "vpp-dev@lists.fd.io" Subject: [EXTERNAL] [vpp-dev] [review-request] vl

Re: [EXTERNAL] Re: [vpp-dev] vppctl makes VPP hang-up occasionally

His output is from the stdio console; it's the vppctl session that causes a trigger to be loaded. Chris. -Original Message- From: vpp-dev@lists.fd.io On Behalf Of Ray Kinsella Sent: Thursday, July 11, 2019 06:42 To: dbar...@cisco.com; Yusuke Tatsumi ; vpp-dev@lists.fd.io Subject: [EXTE

Re: [vpp-dev] vppctl makes VPP hang-up occasionally

Sure, and in 99.99% of cases nobody would ever notice, too. For the curious, the most straightforward way to tickle this particular feature is something like “socat /run/vpp/cli.sock stdio” to get a CLI connection without any TELNET negotiation; there’s a ~1s pause while VPP waits for the negoti

Re: [vpp-dev] vppctl makes VPP hang-up occasionally

For the archives, https://gerrit.fd.io/r/#/c/20573/ was merged earlier to resolve this issue. We are hoping Tatsumi is able to confirm this, but since it is a better approach regardless. Chris. From: vpp-dev@lists.fd.io On Behalf Of Dave Barach via Lists.Fd.Io Sent: Tuesday, July 9, 2019 08:0

Re: [EXTERNAL] Re: [vpp-dev] VPP Router Plugin or alternatives

TCP-MD5 may technically be obsolete, but it’s used widely for protecting BGP sessions in the real world. Noting the comments in https://tools.ietf.org/html/rfc5925#page-35 that any AO implementation SHOULD support MD5, I would suggest starting with an RFC 2385 TCP-MD5 implementation. It may be

Re: [EXTERNAL] [vpp-dev] VPP OOM crash in CLI

e- > From: vpp-dev@lists.fd.io On Behalf Of Chris Luke > Sent: Thursday, May 16, 2019 6:42 > To: Andreas Schultz > Cc: vpp-dev@lists.fd.io > Subject: Re: [EXTERNAL] [vpp-dev] VPP OOM crash in CLI > > > -Original Message- > > From: Andrea

Re: [EXTERNAL] [vpp-dev] VPP OOM crash in CLI

> -Original Message- > From: Andreas Schultz > Am Mi., 15. Mai 2019 um 19:31 Uhr schrieb Luke, Chris > : > > > > The pager in the CLI retains output up to a certain amount but then gives > up and switches to pass-through after a certain number of lines (default is > 10). If the output

Re: [EXTERNAL] [vpp-dev] VPP OOM crash in CLI

The pager in the CLI retains output up to a certain amount but then gives up and switches to pass-through after a certain number of lines (default is 10). If the output doesn't have newlines, or that default has been altered, then it will try to use more memory. In this case it appears to d

Re: [vpp-dev] New vpp project committer nomination: Paul Vinciguerra

+1 From: vpp-dev@lists.fd.io On Behalf Of Dave Barach via Lists.Fd.Io Sent: Wednesday, February 27, 2019 7:38 AM To: vpp-dev@lists.fd.io Cc: vpp-dev@lists.fd.io Subject: [EXTERNAL] [vpp-dev] New vpp project committer nomination: Paul Vinciguerra In view of significant code contributions to the

Re: [EXTERNAL] [vpp-dev] New Committer Nomination: Andrew Yourtchenko

+1 On 11/8/18, 07:17, "vpp-dev@lists.fd.io on behalf of Dave Barach via Lists.Fd.Io" wrote: In view of significant code contributions to the vpp project - see below - I'm pleased to nominate Andrew Yourtchenko as a vpp project committer. I have high confidence that he'll be a major asse

Re: [EXTERNAL] [vpp-dev] Pager Buffer limit

. From: vpp-dev@lists.fd.io [mailto:vpp-dev@lists.fd.io] On Behalf Of Chris Luke Sent: Thursday, September 06, 2018 9:18 AM To: siddarth rai ; vpp-dev@lists.fd.io Subject: Re: [EXTERNAL] [vpp-dev] Pager Buffer limit Siddarth, A quick Google reveals these resources in the first three responses that may

Re: [EXTERNAL] [vpp-dev] Pager Buffer limit

Siddarth, A quick Google reveals these resources in the first three responses that may answer your question: · https://docs.fd.io/vpp/16.12/clicmd_vlib_vlib_unix_cli_c.html#clicmd_set_terminal_pager · https://wiki.fd.io/view/VPP/Command-line_Arguments#.22unix.22_parameters ·

Re: [vpp-dev] git.fd.io expired certificate error

FWIW, this is why Coverity scans have stopped, too. Chris (back from PTO) From: vpp-dev@lists.fd.io On Behalf Of Dave Barach via Lists.Fd.Io Sent: Monday, August 6, 2018 11:21 To: helpd...@fd.io Cc: vpp-dev@lists.fd.io Subject: [EXTERNAL] [vpp-dev] git.fd.io expired certificate error Please fi

Re: [EXTERNAL] Re: [vpp-dev] 18.07 RC1: stable/1807 branch pulled, master reopened

I do not recall a discussion about this. From: vpp-dev@lists.fd.io [mailto:vpp-dev@lists.fd.io] On Behalf Of Damjan Marion via Lists.Fd.Io Sent: Wednesday, July 18, 2018 7:19 AM To: Edward Warnicke Cc: vpp-dev@lists.fd.io Subject: [EXTERNAL] Re: [vpp-dev] 18.07 RC1: stable/1807 branch pulled, ma

Re: [EXTERNAL] Re: [vpp-dev] (nten-vedge-ml 357) Re: [vpp] VXLAN arp response packet is dropped

Satomi, Please consider using services like pastebin or gist for posting text files. Attachments like zip files, and especially password protected ones, don't really belong on mailing lists. Not least because my security people get excited and delete such messages on sight (antivirus can't sc

Re: [EXTERNAL] [vpp-dev] Using Ncurses library in VPP CLI

@lists.fd.io On Behalf Of Chris Luke Sent: Wednesday, July 4, 2018 9:07 To: david.leitch@gmail.com; vpp-dev@lists.fd.io Subject: Re: [EXTERNAL] [vpp-dev] Using Ncurses library in VPP CLI David, Ncurses will never work for socket connections since it makes assumptions about having a tty device and

Re: [EXTERNAL] [vpp-dev] Using Ncurses library in VPP CLI

David, Ncurses will never work for socket connections since it makes assumptions about having a tty device and only uses stdin/stdout. It also does not allow more than one ncurses instance at the same time; all its state is global, so it will never work for multiple CLI sessions. The CLI code

Re: [EXTERNAL] Re: [vpp-dev] VPP ARM Build/Installation

My best guess, not knowing your environment, is that you don’t have ca-certificates installed. From: Jit Mehta Sent: Monday, July 2, 2018 16:50 To: Luke, Chris Cc: Brian Brooks ; vpp-dev@lists.fd.io Subject: [EXTERNAL] Re: [vpp-dev] VPP ARM Build/Installation All, I see the below error when r

Re: [vpp-dev] VPP ARM Build/Installation

Ubuntu aarch64 packages use the same recipe as amd64; https://wiki.fd.io/view/VPP/Installing_VPP_binaries_from_packages#Ubuntu.2FDebian Chris From: vpp-dev@lists.fd.io [mailto:vpp-dev@lists.fd.io] On Behalf Of Brian Brooks Sent: Monday, July 02, 2018 12:56 PM To: Jit Mehta ; vpp-dev@lists.fd.io

Re: [EXTERNAL] [vpp-dev] How to disable assert in VPP

You can provide your own ASSERT mechanism in vppinfra/error_bootstrap.h As is typical, we do not compile ASSERTs for non-debug builds. They add a measurable overhead and peak forwarding performance will be impacted. Chris. From: vpp-dev@lists.fd.io On Behalf Of chetan bhasin Sent: Friday, June

Re: [EXTERNAL] [vpp-dev] VPP & CPU

Since those are all Intel platforms and you propose building on an Intel platform, just build and use it as-is. If you're not modifying anything just use the packages we produce. Most of the performance critical places that make use of CPU optimizations do some magic to build more than one vers

Re: [EXTERNAL] [vpp-dev] Missing functions?

FWIW, it builds for me, top of tree. Chris. From: vpp-dev@lists.fd.io [mailto:vpp-dev@lists.fd.io] On Behalf Of Jon Loeliger Sent: Wednesday, June 13, 2018 1:24 PM To: vpp-dev Subject: [EXTERNAL] [vpp-dev] Missing functions? Hi! With the current VPP top-of-tree here: commit c7d50970d4ed8a488

Re: [EXTERNAL] [vpp-dev] VPP 17.04 Bridge

Ewan, There is no such issue that I am aware of. Have you tried your setup by building from the master branch? Or an older version? Did you search our Jira? https://jira.fd.io/browse/VPP Otherwise, in general, more details will be required; if you do not find an existing issue, please open a n

Re: [EXTERNAL] Re: RE: [vpp-dev] vpp input '\b' problem

Give the patch in https://gerrit.fd.io/r/12969 a go which should fix this issue. It caused surgery all over the CLI command line editor with a few interesting corner cases so I’ve marked it -2 for now until I can beat on it a bit. I would appreciate it if you could test it too. Thanks, Chris.

Re: [vpp-dev] vpp input '\b' problem

Hmm, that looks like a terminal interaction I somehow missed when I wrote that code[1]. Not impossible to solve, but it may not be soon. If you could, please add a jira ticket for it https://jira.fd.io in the VPP project and assign it to me. Thanks, Chris. [1] Sending backspace to the terminal

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

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 updatin

Re: [EXTERNAL] Re: Re: [csit-dev] [vpp-dev] A 404 error occurred in the process of sudo apt-get update. How to solve it?

ial contrib deb http://download.virtualbox.org/virtualbox/debian xenial contrib deb http://download.virtualbox.org/virtualbox/debian xenial contrib deb http://download.virtualbox.org/virtualbox/debian xenial contrib nwnj...@fiberhome.com<mailto:nwnj...@fiberhome

Re: [vpp-dev] A 404 error occurred in the process of sudo apt-get update. How to solve it?

‘fd.io.ubuntu..main’ is not a valid URL – spot the double-dot. It’s missing the word ‘xenial’. Chris. From: vpp-dev@lists.fd.io On Behalf Of ?? Sent: Tuesday, May 1, 2018 22:41 To: vpp-dev Cc: csit-dev Subject: [EXTERNAL] [vpp-dev] A 404 error occurred in the process of sudo apt-get update.

Re: [vpp-dev] router plugin ISIS

IS-IS is not an IP protocol, it’s a layer 2 protocol, meaning it has its own Ethertype. Chris. From: vpp-dev@lists.fd.io [mailto:vpp-dev@lists.fd.io] On Behalf Of Gulakh Sent: Monday, April 30, 2018 9:42 AM To: vpp-dev@lists.fd.io Subject: [vpp-dev] router plugin ISIS Hi, i want to extend route

[vpp-dev] VPP 18.04 has been released! Artifacts are available on nexus.fd.io

All, I am happy to announce that VPP 18.04 has been released! The release notes can be found at https://docs.fd.io/vpp/18.04/release_notes_1804.html. The various release artifacts have made their way to the right places on nexus.fd.io. Packaging for Centos 7 (Intel), openSUSE Leap 42.3 (Intel)

[vpp-dev] Notice: Branch stable/1804 closed for changes

All, Today is VPP 18.04 release day; to help the release go smoothly we close the branch to changes during the release process. From this point, any changes submitted for review will go ignored until after the release is complete. Committers, Please avoid merging any changes into stable/1804 u

[vpp-dev] VPP 18.04 release day is tomorrow!

All, Release day is upon us. The tentative plan is that tomorrow morning, around 07:00 US Eastern time I'll declare the stable branch closed to new patches. If you have critical fixes for stable, that is your deadline to get them in for the release. Thanks, Chris.

[vpp-dev] Draft VPP 18.04 release notes

All, A first pass at the release notes for VPP 18.04 are available for review in https://gerrit.fd.io/r/#/c/12038/ . I have not yet walked the commit history looking for juicy key features to include in the list, I'll do that tomorrow. Suggestions are, of course, welcome! A preview can be seen

[vpp-dev] Reminder: stable/1804 will release on Wednesday!

All, A reminder that VPP 18.04 will be released this Wednesday, April 25th. We're still accepting critical bug fixes, but at this point I expect few patches between now and then. That said, feedback on the stability of the branch is always welcome. Cheers, Chris.

Re: [csit-dev] [vpp-dev] ARM vpp-dpdk-dkms nexus artifacts - CSIT

Given 18.04 is just one week away I would suggest the path of least disturbance at least until after the release. I abhor complications. :) Chris. From: csit-...@lists.fd.io [mailto:csit-...@lists.fd.io] On Behalf Of Ed Kern Sent: Wednesday, April 18, 2018 11:10 AM To: Peter Mikus -X (pmikus -

Re: [vpp-dev] IP Reassembly does not work at 18.04

Yes please, ideally with a Jira ref in the title :) Chris > -Original Message- > From: Klement Sekera -X (ksekera - PANTHEON TECHNOLOGIES at Cisco) > [mailto:ksek...@cisco.com] > Sent: Tuesday, April 17, 2018 12:01 PM > To: Luke, Chris ; > wangchuan...@163.com; vpp-dev > Subject: RE: [vp

Re: [vpp-dev] IP Reassembly does not work at 18.04

Does this impact stable/1804 also? Chris. > -Original Message- > From: vpp-dev@lists.fd.io [mailto:vpp-dev@lists.fd.io] On Behalf Of Klement > Sekera > Sent: Tuesday, April 17, 2018 11:50 AM > To: wangchuan...@163.com; vpp-dev > Subject: Re: [vpp-dev] IP Reassembly does not work at 18.04

Re: [vpp-dev] VPP VCL Lib error #vpp

Dave, Let me know if you can reproduce this and you think this is severe enough to postpone the 18.04 release, which is currently set for Wednesday of next week. Chris. From: vpp-dev@lists.fd.io [mailto:vpp-dev@lists.fd.io] On Behalf Of Dave Wallace Sent: Tuesday, April 17, 2018 9:54 AM To: duc

[vpp-dev] Note: Verify jobs failing

All, Some verify jobs are failing because of an issue with the pypi/pythonhosted repositories. In particular, the Centos containers happened to rebuild during the current outage of the remote repository and it wasn't caught, meaning that the Centos based verify jobs don't have a working Python

Re: [vpp-dev] Build error with my_plugin.api.h file.

I’d recommend working from master, personally. :) Though that DPDK version should work fine; there was a period not long ago in which DPDK broke their packages and invalidated the checksums we had, but I thought that was evident only on master and only briefly, not 18.01*. Chris. From: Sara G

Re: [vpp-dev] Build error with my_plugin.api.h file.

Bit of a long-shot, but it is plausible that autotools didn’t rebuild completely after you added your plugin files I suppose. It’s sometimes worth cleaning the tree to force it. “make wipe” or to be doubly sure “git clean -fxd” (making sure you have your local files added to git etc) Chris Fro

Re: [vpp-dev] Build error with my_plugin.api.h file.

Do you list the .api files in the variable API_FILES in your plugin .am file? Chris From: vpp-dev@lists.fd.io [mailto:vpp-dev@lists.fd.io] On Behalf Of Sara Gittlin Sent: Monday, April 16, 2018 11:08 AM To: vpp-dev@lists.fd.io Subject: Re: [vpp-dev] Build error with my_plugin.api.h file. I see t

Re: [vpp-dev] vec_new() vs. vec_validate()

Vec_new always allocates storage, vec_validate ensures that an existing allocation is at least a certain size, or create a new one if the pointer is NULL. The latter is typically used when the storage will be used as an array and you want to make sure it's large enough to store element N. See

Re: [vpp-dev] [csit-dev] VPP 18.04-RC2 release milestone

rking to produce an initial set of performance results graphs for 18.04 that can be reviewed at next Tuesday's VPP meeting. Thanks, -daw- On 04/11/2018 05:36 PM, Chris Luke wrote: All, I have created the v18.04-rc2 tag on the HEAD of VPP branch stable/1804 and verified that the build

[vpp-dev] VPP 18.04-RC2 release milestone

All, I have created the v18.04-rc2 tag on the HEAD of VPP branch stable/1804 and verified that the build artifacts arrived on nexus.fd.io[1][2]. This completes the RC2 release milestone for VPP 18.04. As a reminder, per the release plan

Re: [vpp-dev] 18.04 RC2 this Wednesday!

/memclnt.api:0:1: Old Style VLA: u8 data[0]; No idea if it is anywhere critical or if someone has created reports for this in the past. Jan Hugo On 04/09/2018 08:43 PM, Chris Luke wrote: All, Gentle reminder that 18.04 RC2 will be posted on Wednesday. Note: After Wednesday's RC2 Mile

Re: [vpp-dev] 18.04 RC2 this Wednesday!

work with them building a set of routers, and having them in the stable branche would mean that the chance of some patches breaking this functionality would be a lot smaller. Cheers, Jan Hugo Prins On 04/09/2018 08:43 PM, Chris Luke wrote: All, Gentle reminder that 18.04 RC2 will be posted on W

[vpp-dev] 18.04 RC2 this Wednesday!

All, Gentle reminder that 18.04 RC2 will be posted on Wednesday. Note: After Wednesday's RC2 Milestone, only critical bug fixes will be merged into branch stable/1804. Please review open anomalies for candidates to be fixed this week. Also, please remember to open a Jira ticket for all patches

Re: [vpp-dev] Build failure on 18.04

That looks like you have a connectivity issue to one of the download sites for DPDK, nasm, and/or aeslib. Check you can reach http://fast.dpdk.org, http://www.nasm.us and http://github.com and that they give non-zero length responses. It occurs to me that perhaps the Makefile should display wha

Re: [vpp-dev] Patches for 18.04

You can cherry pick them to the stable branch, though preferably with a Jira ID in the first line (you can amend the commit message after you cherry pick it). Chris. From: vpp-dev@lists.fd.io On Behalf Of Thomas F Herbert Sent: Friday, April 6, 2018 14:38 To: vpp-dev@lists.fd.io Cc: vpp-dev ; B

Re: [vpp-dev] 18.04 RC1 is cut, master and stable/1804 are open

nt, Dave Wallace for his excellent rework of the guide, Vanessa and Ed Warnicke for their infrastructure support. Cheers, Chris From: vpp-dev@lists.fd.io On Behalf Of Chris Luke Sent: Wednesday, April 4, 2018 22:40 To: vpp-dev@lists.fd.io Subject: [vpp-dev] 18.04 RC1 is cut, master is open aga

[vpp-dev] 18.04 RC1 is cut, master is open again

All, The stable/1804 branch was created earlier; master is now open again for general patches. I'm not ready to accept fixes on the new stable branch. This is pending determining why packagecloud hasn't received any packages yet and giving the artifacts a test, but should have news on this tom

[vpp-dev] RC1 branch on Wednesday!

All, A reminder that the RC1 branch is this week on Wednesday! We’re still accepting low-risk patches on master ahead of the branch. Milestone Date Deliverables RC1 2018-04-04 (F0+14) Code complete, pull first release throttle branch, only bug fixes accepted on throttle train. After pull:

Re: [vpp-dev] Auto script invocation after VPP init completed

The VPP config file (/etc/vpp/startup.conf) allows an "exec" command which loads a file and runs it like the lines are input to the CLI. https://wiki.fd.io/view/VPP/Command-line_Arguments#.22unix.22_parameters see "exec" which is closely related to the CLI command of the same name: https://doc

Re: [vpp-dev] Semantics of field 'link_speed' in 'sw_interface_details' API.

That only really leaves us one order of magnitude of growth…! :) Chris From: on behalf of Damjan Marion Date: Thursday, March 29, 2018 at 12:53 To: "vpp-dev@lists.fd.io" Cc: "vpp-dev@lists.fd.io" Subject: Re: [vpp-dev] Semantics of field 'link_speed' in 'sw_interface_details' API. Yes, but

[vpp-dev] RC1 branch in one week!

All, A reminder that the RC1 branch is in one week! We’re still accepting low-risk patches on master ahead of the branch. Milestone Date Deliverables RC1 2018-04-04 (F0+14) Code complete, pull first release throttle branch, only bug fixes accepted on throttle train. After pull: main branch

[vpp-dev] API freeze today

All, Per https://wiki.fd.io/view/Projects/vpp/Release_Plans/Release_Plan_18.04, Milestone Date Deliverables F0 2018-03-21 APIs frozen. Only low-risk changes accepted on main branch. VPP 18.04 is now at milestone F0. This means no more API changes will be considered in master by committers

Re: [vpp-dev] Coverity Scan seems to be back

ecause they don't automatically transfer you to https://scan.coverity.com. I guess they must be paranoid after the recent break in. Burt On Fri, Mar 16, 2018 at 5:36 PM, Chris Luke mailto:chris_l...@comcast.com>> wrote: Coverity’s Scan service appears to be back. They should have e

[vpp-dev] Coverity Scan seems to be back

Coverity's Scan service appears to be back. They should have emailed registered users about resetting their passwords. I've also kicked off a build to test it and get things going again. Hopefully we have time to knock out some fixes for static analysis issues before the branch in a few weeks!

[vpp-dev] Reminder: 18.04 API freeze is next Wednesday!

API freeze next week; get your API-related patches in soon! https://wiki.fd.io/view/Projects/vpp/Release_Plans/Release_Plan_18.04 Milestone Date Deliverables F0 2018-03-21 APIs frozen. Only low-risk changes accepted on main branch. Cheers, Chris.

Re: [vpp-dev] vppsb's librtnl is broken with top of VPP tree

Oh, doh, it's vppsb that has the issue. I'll go back to sleep. :) Chris

Re: [vpp-dev] vppsb's librtnl is broken with top of VPP tree

…but… how did that get in there in the first place if the compiler whines about it?! Chris. From: vpp-dev@lists.fd.io On Behalf Of Wang Sent: Tuesday, March 13, 2018 18:37 To: vpp-dev@lists.fd.io Cc: vpp-dev@lists.fd.io Subject: Re: [vpp-dev] vppsb's librtnl is broken with top of VPP tree I ju

[vpp-dev] 18.04 API freeze in two weeks

A friendly early warning folks: API freeze for the 18.04 release is in two weeks! Milestone Date Deliverables F0 2018-03-21 APIs frozen. Only low-risk changes accepted on main branch. Cheers, Chris

[vpp-dev] Coverity Scan currently unavailable

In case I don't make it to the end of the dev call, just wanted to comment that I am aware that Coverity Scan is unavailable. It seems some upgrade work they did about Feb 20th didn't go so well. They do plan to restore the service, but no news on when. I have no other details than this. Chri

  1   2   >