[vpp-dev] device job voting?

Long story short, a VPP change [0] has broken CSIT and needs a fix [1]. If the devicetest job was voting, it would [2] vote -1, preventing the breakage. Vratko. [0] https://gerrit.fd.io/r/18352 [1] https://gerrit.fd.io/r/19636 [2] https://jenkins.fd.io/job/vpp-csit-verify-device-master-1n-skx/8

Re: [vpp-dev] device job voting?

Hi Paul. > "cli_inband" commands There are other ways how CSIT can be broken by an innocent looking VPP change. CSIT currenlty does use: - VAT console commands - vppctl commands - cli_inband via PAPI - in-house serialization-deserialization for using PAPI remotely [1] Other VPP interfaces which

Re: [vpp-dev] device job voting?

I forgot to add, that technical details of this kind are usually being discussed in great detail on fd.io slack, channel csit-papi. Vratko. From: Vratko Polak -X (vrpolak - PANTHEON TECHNOLOGIES at Cisco) Sent: Friday, 2019-May-24 18:14 To: 'Paul Vinciguerra' ; vpp-dev@lists.fd.io Subject: RE: [vp

Re: [vpp-dev] Plugin Versions

SemVer says: > Patch version Z (x.y.Z | x > 0) MUST be incremented if only backwards > compatible bug fixes are introduced. > A bug fix is defined as an internal change that fixes incorrect behavior. That means API version should be bumped even if the change only affects the implementation (and n

Re: [vpp-dev] Plugin Versions

dev] Plugin Versions On 27 May 2019, at 13:54, Vratko Polak -X (vrpolak - PANTHEON TECHNOLOGIES at Cisco) via Lists.Fd.Io mailto:vrpolak=cisco@lists.fd.io>> wrote: SemVer says: > Patch version Z (x.y.Z | x > 0) MUST be incremented if only backwards > compatible bug fixes a

Re: [vpp-dev] what is alternative for l2fib_add_fwd_entry in vpp stable/1810?

Seems to be removed here [0], l2fib_add_entry being the replacement. And of course, use stable/1904 or later. Vratko. [0] https://gerrit.fd.io/r/c/14699/4/src/vnet/l2/l2_fib.h From: vpp-dev@lists.fd.io On Behalf Of Mostafa Salari Sent: Sunday, 2019-June-16 10:00 To: vpp-dev@lists.fd.io Subject:

[vpp-dev] FW: [tsc] RESPONSE NEEDED: LFN Staff Survey of the Community

I associate communities with mailing lists, so forwarding (from TSC list) to the two lists I engage with the most. Vratko. From: t...@lists.fd.io On Behalf Of Brandon Wick Sent: Wednesday, 2019-June-26 04:37 Subject: [tsc] RESPONSE NEEDED: LFN Staff Survey of the Community LFN Community, In or

[vpp-dev] new make target

I have opened a Jira task [0] for a new improvement request. Its description also hints at current plans for implementation API CRC job, documented in [1]. Vratko. [0] https://jira.fd.io/browse/VPP-1715 [1] https://gerrit.fd.io/r/18356 -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages se

Re: [vpp-dev] VPP api python scripts in packages for out-of-tree VPP plugins.

Adding vpp-dev, as I am not sure who reads vpp-api-dev. Here [0] is my attempt at a simple solution. Vratko. [0] https://gerrit.fd.io/r/20595 From: vpp-api-...@lists.fd.io On Behalf Of Luca Muscariello via Lists.Fd.Io Sent: Tuesday, 2019-July-09 15:56 To: vpp-api-...@lists.fd.io; hicn-...@lis

[vpp-dev] Ubuntu1604 merge job is broken

Paul has already commented [0] on this, hopefully my subject draws more attention. Basically, packagecould does not like the look of ubuntu1604 VOM package, leading not only to missing VOM package, but also other packages unlucky enough to come after VOM in upload order. This includes packages s

[vpp-dev] flag day to enable API flag day process

The main API flag document: [0]. I have most of implementation ready, see [1] and comments there. The missing parts is e-mail alerting and postponing main vpp verify jobs until API check passes (older stable/ VPP branches are tricky to support in that way). Please review, I would like to merge

Re: [vpp-dev] [discuss] FD.io Maintenance: 2019-07-30 @ 1700 UTC (10:00am PDT) - 2100 UTC (2:00pm PDT)

> If you experience any issues please open a ticket at > support.linuxfoundation.org. Executors for ci-management jjb jobs are not available, opened [3]. [3] https://jira.linuxfoundation.org/servicedesk/customer/portal/2/IT-17012 From: disc...@lists.fd.io On Behalf Of Vanessa Valderrama Sent:

Re: [vpp-dev] flag day to enable API flag day process

[0] is merged, but [1] is stuck due to [2]. Vratko. [2] https://lists.fd.io/g/vpp-dev/message/13627 From: Vratko Polak -X (vrpolak - PANTHEON TECHNOLOGIES at Cisco) Sent: Monday, July 22, 2019 7:14 PM To: vpp-api-...@lists.fd.io; vpp-dev@lists.fd.io; csit-dev Cc: Dave Wallace (dwallac...@gmail.

Re: [vpp-dev] FD.io - Gerrit 2.16 Changes

Hi Klement. Using %private avoids triggering verify jobs, and you can use UI to set the desired state after that. Based on my testing [0], "Unmark private" action triggers verify jobs if and only if "fd.io JJB" is in reviewers list (same as with "recheck" comment). From what I can see, Jenkins a

Re: [vpp-dev] flag day to enable API flag day process

[1] is now merged, job is created, and I see [3] it passing. Vratko. [3] https://jenkins.fd.io/job/vpp-csit-verify-api-crc-master/2/console From: Vratko Polak -X (vrpolak - PANTHEON TECHNOLOGIES at Cisco) Sent: Wednesday, July 31, 2019 10:41 AM To: 'vpp-api-...@lists.fd.io' ; 'vpp-dev@lists.fd.io

[vpp-dev] troubles with centos7 packages

Continuing from #vpp-dev slack channel: How can I figure out the correct package names for centos? The previous way does not work for recent builds. > 13:01:27 No package vpp-19.08-rc0~794_g7520e17~b7546 available. https://logs.fd.io/production/vex-yul-rot-jenkins-1/csit-vpp-functional-master-c

Re: [vpp-dev] flag day to enable API flag day process

> job is created … but it quickly turned to non-voting, because a recent merge [4] changed CRCs. It has been reverted [5] since then, but verifying everything is fixed [6] on CSIT side is delayed [7]. Vratko. [4] https://gerrit.fd.io/r/c/vpp/+/20946 [5] https://gerrit.fd.io/r/c/vpp/+/20997 [6]

Re: [vpp-dev] 19.08 RC1 Milestone (stable branch pull) is next Wed 7 Aug 2019!

> Commit first to the release throttle, then "git cherry-pick" into master Next release, next reminder why [1] I think the order should be reversed. Vratko. [1] https://lists.fd.io/g/vpp-dev/message/12786 -Original Message- From: vpp-dev@lists.fd.io On Behalf Of Andrew Yourtchenko Sent

Re: [vpp-dev] flag day to enable API flag day process

Yesterday I forgot to notify that the job [8] is fixed [9] now. It will be kept non-voting for a week or so to make sure no CRC surprises are about to get merged just before the voting is enabled again. Vratko. [8] https://jenkins.fd.io/job/vpp-csit-verify-api-crc-master/ [9] https://gerr

Re: [vpp-dev] Reminder: 19.08 RC1 is TODAY starting 18:00 UTC

The job [1] is non-voting, so if needed the queued runs can be cancelled, which unblocks gerrit without affecting the overall vote. Several people (including me) have Jenkins rights to do that. It looks like the required executor stopped being available. I hear the appropriate people have been not

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

>> uDPI > microDPI Universal Deep Packet Inspection is the new project here. Would it make sense to use UDPI as its abbreviation (e.g. capital U, to distinguish from "micro")? Vratko. From: t...@lists.fd.io on behalf of Ni, Hongjun Sent: Tuesday, August

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

> UDPI will be easily misunderstood as UDP+I. > uniDPI is ok? +1 to uniDPI. Vratko. From: 李幸福(Xingfu Li) Sent: Tuesday, August 13, 2019 12:45 To: Vratko Polak -X (vrpolak - PANTHEON TECHNOLOGIES at Cisco); Ni, Hongjun; Alexey; t...@lists.fd.io Cc: vpp-dev@l

[vpp-dev] API change on master

VPP API change [0] has been merged. For open VPP changes that means the next rechecks or uploads (without rebasing) will fail the CRC check job. Vratko. [0] https://gerrit.fd.io/r/c/vpp/+/18361 -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#1

Re: [vpp-dev] ValueError: Fieldname 'async' is a python keyword and is not accessible via the python API

If next version of Python adds a new reserved keyword, it will "break" clients using PAPI in that version (for calls using that keyword as argument name) anyway. The main downside is that our current checks only look at locally installed Python. So [3] got +1 just because verify jobs use Pyth

Re: [vpp-dev] how VAT work with Socket IP Address

>> See ssh -R / -L for example. > Is this way not feasible? It is feasible. In CSIT we use this (ssh -L) way, although it took me some time to tune the ssh command (so the tunnel is closed either on-demand or by timeout). Here [0] is a part of the code composing the command, in case you are

Re: [vpp-dev] VPP API sometimes hangs on ip_route_details response #vppcapi #vpp_stability #vpp #binapi

Looks like VPP-1753 to me. I do not have much to add, heisenbugs are hard to figure out. Vratko. From: vpp-dev@lists.fd.io on behalf of sylvain.cadil...@jaguar-network.com Sent: Wednesday, September 4, 2019 01:36 To: vpp

[vpp-dev] Temporary CRC failures

[0] has been merged, [1] has been postponed. The VPP API CRC jobs should be reliable from now on again. Vratko. [0] https://gerrit.fd.io/r/c/vpp/+/21508 [1] https://gerrit.fd.io/r/c/vpp/+/21706 -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#1

Re: [vpp-dev] VAT to PAPI issue with policer

VAT classify_add_del_session contains "skip_n 1", but PAPI classify_add_del_session does not contain "skip_n_vectors" argument, (so the default 0 is used). Not sure whether that is causing the different behavior, but there may be other differences. Vratko. From: csit-...@lists.fd.io On Behalf O

[vpp-dev] CRC job reliable again

Yesterday, we did a risky thing of merging two [0] VPP [1] changes affecting APIs. Without verifying CSIT really is ready for the end result. Fixed [2] only now. From the process point of view, we have some possible improvements planned, but until we are able to implement them, we will be stickin

Re: [vpp-dev] [csit-dev] API check failure

Fixed. Short report: https://lists.fd.io/g/vpp-api-dev/message/34 Longer discussion on how to prevent similar things from happening in future: #csit-dev channel on FD.io slack. We will update the flag day document when we conclude the discussion. Vratko. -Original Message- From: Dave Bara

Re: [vpp-dev] VAT can support define a macro? #vapi

Macros are currently not supported in .api files. > define MAX_NUM (12) The "define" keyword defines API messages, not macros. The C preprocessor is one possibility to add support for macros, but not sure whether it would play well with .api syntax. You can try to add that (or a similar featu

[vpp-dev] surprising performance on denverton

Hello everyone. I am working on automating "git bisect" process for locating mainly performance regressions and progressions, (also usable for locating breakages and fixes). Of course, the process works correctly only if the performance results are stable enough. And we know from the per-patch p

[vpp-dev] API and plugins

Questions: If an API message handler is moved into a different plugin, does it constitute a (backward incompatible) API change? If yes, should we use similar checks and processes as for CRC changes? Example (not merged yet): sw_interface_ip6nd_ra_config is being moved from vnet [0] to plugins/ip6

Re: [vpp-dev] API and plugins

fig that experiences problems look like ? --a On 8 Nov 2019, at 14:47, Vratko Polak -X (vrpolak - PANTHEON TECHNOLOGIES at Cisco) via Lists.Fd.Io mailto:vrpolak=cisco@lists.fd.io>> wrote:  Questions: If an API message handler is moved into a different plugin, does it constitute a

Re: [vpp-dev] Multiple patch validation failures: yamllint AWOL

> Makefile by testing for JENKINS_URL? Inputs to the program make should be understandable by human. When I want to predict locally what would the checkstyle job vote, I prefer something like: make checkstyle-all rather than: JENKINS_URL=jenkins.fd.io make checkstyle Or did you mean a differe

Re: [vpp-dev] Requirements for DPDK pmd/feature testing in CSIT vpp-device-test jobs

> a +2 triggers a pre-commit gate where VOM and the dist builds and the > extended tests are run. > If everything passes, the change is merged, if not, the +2 is removed. +1 to that, but I highly doubt Gerrit supports such a workflow. Additional features we would like to have: + Manual trigger t

Re: [vpp-dev] Change to Gerrit

> implementing something like [0] +1, but... > skip the jobs and set verify label after the codestyle checks if no files > were changed ... how do you imagine this being implemented in ci-management? Currently, the other jobs are triggered by checkstyle_success Gerrit comment, but how would th

Re: [vpp-dev] vpp19.08 ipsec vpp_papi

> This situation does not happen when I use CLI like this I think the difference is that CLI is restricted, it can only accept printable characters on input. Therefore it assumes it gets "hexlified" value, and applies "unhexlify" on its input. Contrary to that, PAPI (hopefully) can handle arbitra

Re: [vpp-dev] CSIT - performance tests failing on Taishan

>> the attached patch Converted to Gerrit: [1]. Vratko. [1] https://gerrit.fd.io/r/c/vpp/+/23849 -Original Message- From: vpp-dev@lists.fd.io On Behalf Of Juraj Linkeš Sent: Thursday, December 5, 2019 11:11 AM To: Lijian Zhang (Arm Technology China) ; Peter Mikus -X (pmikus - PANTHEON

Re: [csit-dev] [vpp-dev] Spurious API CRC failures

> Unfortunately when I pushed the patch [2], it failed to pass the crc check Added explanations to gerrit: [3], [4]. Vratko. [3] https://gerrit.fd.io/r/c/csit/+/23926/1/resources/api/vpp/supported_crcs.yaml#34 [4] https://gerrit.fd.io/r/c/csit/+/23926/1/resources/api/vpp/supported_crcs.yaml#27

Re: [csit-dev] [vpp-dev] Spurious API CRC failures

> automating_vpp_api_flag_day.rst Reading that, I see various improvements I wanted to add, but never found time to do it. So, here [5] is a quick edit, with more details on the CSIT side of the process, and with links to existing changes as examples. Vratko. [5] https://gerrit.fd.io/r/c/csit/+/

Re: [vpp-dev] merge jobs failing..

> No its not clear to me why it verified… Because the verification run happened before [2] was merged (in other words, 23913 should have been rebased after that). I think this kind of merge error still happens infrequently enough, and any "remove +1 from affected open changes" ideas would be vote

Re: [vpp-dev] python api over tcp?

CSIT uses VPP API via socket (tunneled over SSH) for most interactions. We also read stats for just one (I think) purpose, reading runtime stats (/sys/node). The way we do that is historical and convoluted, for the result see INFO line at [1]. Looking at the result, the appropriate API way would

Re: [vpp-dev] python api over tcp?

:00 PM Ole Troan mailto:otr...@employees.org>> wrote: On 9 Jan 2020, at 16:50, Paul Vinciguerra mailto:pvi...@vinciconsulting.com>> wrote:  Is there any objection to adding a tls listener and an instance to the stats client to vpp_papi? Use grpc as transport? Cheers, Ole

Re: [vpp-dev] python api over tcp?

> This should be done as an intermediate agent. I have a hypothetical question. (I am not trying to be cheeky. I feel there may be a difference, I just do not see it.) Imagine a world where VPP supports (CLI via vppctl and) binary API only over shared memory. No support for binary API over Unix D

Re: [vpp-dev] Arm verify job broken

> accidentally separated two scripts that had to stay together. My fault, I had no idea this kind of coupling existed. Adding comments [1] to prevent similar errors in future. Vratko. [1] https://gerrit.fd.io/r/c/ci-management/+/24348 From: vpp-dev@lists.fd.io On Behalf Of Christian Hopps Sent

Re: [vpp-dev] Gerrit 25463 fails API CRC check for no obvious reason...

From: vpp-dev@lists.fd.io On Behalf Of Dave Barach via Lists.Fd.Io Sent: Wednesday, February 26, 2020 4:10 PM To: Maciek Konstantynowicz (mkonstan) Cc: vpp-dev@lists.fd.io Subject: Re: [vpp-dev] Gerrit 25463 fails API CRC check for no obvious reason... Thanks... Dave From: Maciek Konstantyno

Re: [vpp-dev] Gerrit 25463 fails API CRC check for no obvious reason...

This [0] change got merged. It got wrong Verified+1 due to naginator retrying one job (and Gerrit forgetting about other ones). Basically the same as these [1] two [2] older failures. Not sure whether is better to revert the change or wait for CSIT to catch up. Vratko. [0] https://gerrit.fd.io/r

Re: [vpp-dev] Can I submit some API changes for 19.08, et al. release branches?

> as soon as the CRC of any existing messages does not change, a patch is okay > to include into 19.08 Does that mean we want an api-crc job also for 1908 stream? We currently have api-crc job only for master, because other branches were not expected to edit .api files. Vratko. From: vpp-dev@li

Re: [vpp-dev] Gerrit 25463 fails API CRC check for no obvious reason...

) Cc: Dave Barach (dbarach) ; Maciek Konstantynowicz (mkonstan) ; vpp-dev ; Jakub Grajciar -X (jgrajcia - PANTHEON TECH SRO at Cisco) Subject: Re: [vpp-dev] Gerrit 25463 fails API CRC check for no obvious reason... > On 26 Feb 2020, at 16:36, Vratko Polak -X (vrpolak - PANTHEON TECHNOLOGI

Re: [vpp-dev] Can I submit some API changes for 19.08, et al. release branches?

> Adding a new API into an existing file will still change the CRC on the > plugin/module Looking into a .api.json file, I see "crc" only for messages, but the whole file also ends with a "vl_api_version" value. > if we are aiming for binary compatibility Crc values guard against backward-incom

Re: [vpp-dev] Can I submit some API changes for 19.08, et al. release branches?

io On Behalf Of Vratko Polak -X (vrpolak - PANTHEON TECHNOLOGIES at Cisco) via Lists.Fd.Io Sent: Thursday, 2020-February-27 14:56 To: Andrew Yourtchenko Cc: vpp-dev@lists.fd.io Subject: Re: [vpp-dev] Can I submit some API changes for 19.08, et al. release branches? > Adding a new API into an exis

Re: [vpp-dev] Increase MTU from ethernet packets

> 65535 bytes with ETHERNET_MAX_PACKET_BYTES I take it as a query on how easy it is for VPP to support super jumbo frames [0]. > most networks use approximately 9000 In theory, VPP could allow higher values to be set on demand, while making sure the default MTU values remain small enough. Even

[vpp-dev] Regression in SRv6

Trending has detected a performance regression in our SRv6 tests. I summarized my current findings here [5]. Vratko [5] https://gerrit.fd.io/r/c/vpp/+/25647#message-7d415999_6a0ba69f -Original Message- From: csit-rep...@lists.fd.io On Behalf Of nore...@jenkins.fd.io Sent: Wednesday, 20

Re: [vpp-dev] [csit-report] Regressions as of 2020-04-03 14:00:14 UTC #email

> 100ge2p1cx556a-rdma No VPP code change. Up to now, RDMA tests were suffering from "duration stretching". That is a phenomenon where TRex takes longer to send the required number of packets, so device under tests experiences smaller offered load and MRR value is inflated. We have suppressed the p

[vpp-dev] faster processing slower rate

Hello VPP experts. I have encountered an unexpected pattern in performance results. So I wonder, is there a bug somewhere (VPP or CSIT), or is there a subtle reason why the performance pattern should be expected? Usually, the more processing VPP in a particular test has to do, the smaller forwar

Re: [vpp-dev] [csit-report] Regressions as of 2020-04-15 02:00:17 UTC #email

> 3n-hsw This turned out to be a bug on CSIT side, breaking numa detection, affecting every NIC on numa 1. The bug was introduced in [0] and fixed in [1] and [2]. Vratko. [0] https://gerrit.fd.io/r/c/csit/+/25363 [1] https://gerrit.fd.io/r/c/csit/+/26569 [2] https://gerrit.fd.io/r/c/csit/+/26572

Re: [vpp-dev] [csit-report] Progressions as of 2020-04-19 02:00:13 UTC #email

> 3n-hsw Progressions showing the fixes described in [4] do restore the previous performance. Vratko. [4] https://lists.fd.io/g/csit-report/message/2488 -Original Message- From: csit-rep...@lists.fd.io On Behalf Of nore...@jenkins.fd.io Sent: Sunday, 2020-April-19 06:07 To: Fdio+Csit-

Re: [vpp-dev] [csit-report] Regressions as of 2020-04-18 14:00:15 UTC #email

> -rnd-mrr This is a consequence of [0], fixing an old bug in CSIT code. Previously, the traffic was not random enough. Vratko. [0] https://gerrit.fd.io/r/c/csit/+/26456 -Original Message- From: csit-rep...@lists.fd.io On Behalf Of nore...@jenkins.fd.io Sent: Saturday, 2020-April-18 1

Re: [vpp-dev] [csit-report] Regressions as of 2020-04-03 14:00:14 UTC #email

> 3n-hsw Around 2nd of April there happened a regression in eth-l2bdscale1mmaclrn test, visible here [0]. Trending needed multiple runs to identify it is there, and alerting is configured not to report "old" regressions (so it did not report this one). Anyway, the closer look shows previously the

[vpp-dev] Faster PAPI

Hello people interested in PAPI (VPP's Python API client library). In CSIT, our tests are using PAPI to interact with VPP. We are using socket transport (instead of shared memory transport), as VPP is running on machines separate from machines running the tests. We use SSH to forward the socket b

[vpp-dev] VPP-1876

Just a notification for people not monitoring VPP Jira. I have just opened https://jira.fd.io/browse/VPP-1876 "Worse performance with DPDK driver when MTU is set to 2022 or less" I may update the value to 2023 depending on result of a scheduled run. As explained in the Description, this is an old

Re: [vpp-dev] ikev2 API & new API change process

I think there are two issues. One issue is with APIs that were not intended to be Production yet. For ikev2 that basically means the version has been set [5] above 0.x.y only by mistake. As downgrading versions is always risky, marking messages as "In-Progress" instead is better. The other issue

[vpp-dev] new anomaly detection

By now, you should be familiar with Continuous Performance Trending page [0] leading to various graphs and tables tracking performance changes of VPP code. We are planning to replace the old ways of how do Trendline Graphs look. There are still few things missing, but the basic functionality is t

Re: [vpp-dev] new anomaly detection

The standalone logic (not related to PAL internals) is now available on PyPI [2], meaning you can do "pip install jumpavg". Currently there is zero documentation on how to actually use the library (unless you are willing to read comments in the code itself). I will add something when I make PAL u

Re: [vpp-dev] new anomaly detection

> we are planning to replace the old graphs by new graphs > (and delete [1]) some time next week, > depending on the feedback we get. The feedback was non-negative, so we are going ahead. Expect the new content to appear on the old URL [0] around one hour from now. Vratko. From: Vratko Polak -X

Re: [WARNING : MESSAGE ENCRYPTED] [vpp-dev] [VPP]Questions about VPP behavior of over performance limit

> VPP rx/tx counter is 0 Last time I have seen this behavior, it was caused by insufficient value of mem-mbufs [1] parameter. The symptom is large amount of mbuf allocation errors in statistics. See this [0] thread for more context. Vratko. [0] https://lists.fd.io/g/csit-dev/topic/csit_ip4_tes

Re: [vpp-dev] Revert of gerrit 13408 / "vppinfra: AVX2 blend" in progress..

> Not sure what exactly happened It went like this: 0. Patch set 2 is uploaded. 1. Both clang and virl jobs (among others) are triggered. 2. Both jobs fail (virl on the usual NFS mount symptom). 3. Virl job has naginator, so its result is reported as NOT_BUILT. 4. Clang is reported as FAILURE, so

Re: [vpp-dev] [csit-dev] The environment variable PATH is changed after "Setup Framework"

> I wonder why the PATH is changed in CSIT. I do not think CSIT is changing the PATH. I think you see diferent values, because you are logging in in an different way. See the technical summary [0] from bash documentation, or somewhat older and more colourful page [1]. [0] https://www.gnu.org/sof

Re: [vpp-dev] CSIT - sw_interface_set_flags admin-up link-up failing

> VPP is not crashing so no core dump are available. I tried to use "gcore" command to create a core dump from running VPP. So far I got this [0] archive, compressed to around 25 MB, but the core file inside is around 160 GB big. Not sure how to make it smaller, even with small numbers in startup

Re: [vpp-dev] CSIT - sw_interface_set_flags admin-up link-up failing

sage- From: vpp-dev@lists.fd.io On Behalf Of Vratko Polak -X (vrpolak - PANTHEON TECHNOLOGIES at Cisco) via Lists.Fd.Io Sent: Wednesday, 2018-August-01 18:13 To: Peter Mikus -X (pmikus - PANTHEON TECHNOLOGIES at Cisco) ; Ray Kinsella ; vpp-dev@lists.fd.io Cc: vpp-dev@lists.fd.io Subject: Re:

[vpp-dev] make wipe

At the root of local VPP git repository (current master), this is what "make help" has to say about the "wipe" target: wipe- wipe all products of debug build But currently (I think) "all" does not include dpdk/. I believe "make -C dpdk clean" should be inserted somewhere, but I am

Re: [vpp-dev] CSIT - sw_interface_set_flags admin-up link-up failing

> then this issue was fixed It was not fixed, we have just listed VPP-1361 as a known issue [2] and performed more job runs to compensate for failures. Vratko. [2] https://docs.fd.io/csit/rls1807/report/vpp_performance_tests/csit_release_notes.html -Original Message- From: vpp-dev@lis

Re: [vpp-dev] IRC SPAM

Following up on discussion from TCS meeting. It seems the registration part works, assuming you follow the e-mail instruction by issuing /msg NickServ VERIFY REGISTER But the actual login instructions are not helpful, especially the /connect command is not the way for the web client. > on th

Re: [vpp-dev] num-mbufs

> I cannot update wiki, it tells me that I'm trying to do suspicious login :) My workaround it to attempt the login from less deep wiki page, e.g. [1]. Vratko. [1] https://wiki.fd.io/view/Main_Page From: vpp-dev@lists.fd.io On Behalf Of Damjan Marion via Lists.Fd.Io Sent: Tuesday, 2018-August

Re: [vpp-dev] Suspicious login on fd.io wiki

> suggest a workaround? Navigate to https://wiki.fd.io/view/Main_Page before logging in. Vratko. -Original Message- From: vpp-dev@lists.fd.io On Behalf Of Marco Varlese Sent: Wednesday, 2018-September-05 15:31 To: Vanessa Valderrama via RT Cc: vpp-dev@lists.fd.io; infra-steer...@lists.fd

[vpp-dev] new per-patch job

Hello VPP devs. There is a new way of testing performance impact of a VPP Change before merging it. When you add Gerrit comment "perftest" a job will start (different from the previously available one). It will compile both the code in the Change and in its parent, run few tests against both bui

Re: [vpp-dev] new per-patch job

d on directories edited. The hard part is creating a mapping from directories to test tags. Vratko. From: vpp-dev@lists.fd.io On Behalf Of Vratko Polak -X (vrpolak - PANTHEON TECHNOLOGIES at Cisco) via Lists.Fd.Io Sent: Friday, 2018-September-07 15:04 To: vpp-dev@lists.fd.io Cc: vpp-dev@lists.fd.

Re: [vpp-dev] new per-patch job

tko. From: vpp-dev@lists.fd.io<mailto:vpp-dev@lists.fd.io> mailto:vpp-dev@lists.fd.io>> On Behalf Of Vratko Polak -X (vrpolak - PANTHEON TECHNOLOGIES at Cisco) via Lists.Fd.Io Sent: Friday, 2018-September-07 15:04 To: vpp-dev@lists.fd.io<mailto:vpp-dev@lists.fd.io> Cc: vpp-dev@l

[vpp-dev] anomaly detection changes

Hello people watching the trending pages [0]. We have just merged a Change [1] which affects how MRR tests work. Instead of single trial of 10 second duration, the test is now executing 10 trials of 1 second. PAL is told to aggregate the results, so in theory nothing should change, but in practi

Re: [vpp-dev] anomaly detection changes

Quick update, we are stuck. > the test is now executing 10 trials of 1 second > so in theory nothing should change No big changes were visible, so we have kept this change. > to take standard deviations into account > to detect smaller regressions and progressions. But we are not going ahead

Re: [vpp-dev] Master branch l2bd test perf dop

> Is that drop visible in CSIT trending graphs? Mostly not, apparently it depends (at least) on NIC (x520 is not affected) and on number of CPU cores for workers (visible for 4). The biggest drop I see is here [0]. Vratko. [0] https://docs.fd.io/csit/master/trending/trending/l2-3n-hsw-xl710-64

Re: [vpp-dev] auto-abandon

> https://gerrit-review.googlesource.com/Documentation/user-change-cleanup.html Pros are worth it. Contributors can still Restore (and rebase) manually if needed, when they receive an e-mail about the auto-abandon hitting their Change. > Should we enable that? +1. Vratko. From: vpp-dev@lists.

Re: [vpp-dev] auto-abandon

> difficult to find I decided to test that, on a change that is actually abandoned (because 9336 is not, yet). This [0] simple search link finds two changes, one [1] of them is abandoned. Vratko. [0] https://gerrit.fd.io/r/#/q/%22igmp+proxy%22 [1] https://gerrit.fd.io/r/12561 From: vpp-dev@lis

Re: [vpp-dev] [csit-dev] new per-patch job

[0] https://gerrit.fd.io/r/15826 [1] https://gerrit.fd.io/r/15347 From: csit-...@lists.fd.io On Behalf Of Vratko Polak -X (vrpolak - PANTHEON TECHNOLOGIES at Cisco) via Lists.Fd.Io Sent: Friday, 2018-September-07 17:20 To: vpp-dev@lists.fd.io Cc: csit-...@lists.fd.io Subject: Re: [csit-dev] new per-patch

Re: [vpp-dev] API changes to trigger email

> email = f...@project1.io > email = f...@project2.io I think it would be easier to sent only one e-mail to a fd.io mailing list created specifically for announcing VPP api changes. Similarly to how we created csit-report [0] for announcing perform

Re: [vpp-dev] ip4-load-balance

> Any clues as to what might causing the delta? >> using FD.io VPP 18.07 If you are still using that, the performance might depend on the NUMA node used. There was a placement bug, and the fix [1] has been merged just before 18.10. Vratko. [1] https://gerrit.fd.io/r/15483 -Original Message-

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

Just letting you know I am deleting this from (the bottom of) my TODO. Everything should have been solved by everyone using packagecloud now. Vratko. From: vpp-dev@lists.fd.io On Behalf Of Tina Tsou Sent: Thursday, 2018-April-19 19:16 To: Ed Kern (ejk) Cc: Peter Mikus -X (pmikus - PANTHEON TEC

Re: [vpp-dev] [csit-dev] new per-patch job

o/r/16120 From: vpp-dev@lists.fd.io On Behalf Of Vratko Polak -X (vrpolak - PANTHEON TECHNOLOGIES at Cisco) via Lists.Fd.Io Sent: Monday, 2018-November-12 13:40 To: vpp-dev@lists.fd.io Cc: vpp-dev@lists.fd.io Subject: Re: [vpp-dev] [csit-dev] new per-patch job Hello VPP devs. Now that CSIT testbed

Re: [vpp-dev] question related to VPP statistics

There is "stat segment" [0] way of publishing counters. But it was added somewhat recently, so ipsec code probably does not support it (yet). Vratko. [0] https://github.com/FDio/vpp/blob/master/src/vpp/stats/stats.md From: vpp-dev@lists.fd.io On Behalf Of Kevin Yan Sent: Friday, 2018-November-0

Re: [vpp-dev] [csit-dev] anomaly detection changes

hile keeping the sensitivity high. (But I am not the one examining each possible regression.) Vratko. [2] https://lists.fd.io/g/csit-dev/message/3247 [3] https://docs.fd.io/csit/master/trending/new/index.html From: csit-...@lists.fd.io On Behalf Of Vratko Polak -X (vrpolak - PANTHEON TECHNOLOGI

[vpp-dev] naginator on verify

Hello. I have encountered a false Verified+1 (again) caused by a naginated retry effectively removing non-naginated failure. The mechanism is basically the same as the one described in this [0] older e-mail. Consensus then was that VIRL tests are unreliable, but false +1 is caused by inconsiste

[vpp-dev] graph node placement on workers

Hi developers. When examining some performance test results, I started seeing patterns, so I now have multiple questions. I have noticed that (with hyper-threading on) l2-input-vtr graph node is present only on half of VPP workers. (At least for the dot1q test below.) In CSIT, the node is always

Re: [vpp-dev] graph node placement on workers

Polak -X (vrpolak - PANTHEON TECHNOLOGIES at Cisco) via Lists.Fd.Io Sent: Thursday, 2019-January-03 18:13 To: vpp-dev@lists.fd.io Cc: vpp-dev@lists.fd.io Subject: [vpp-dev] graph node placement on workers Hi developers. When examining some performance test results, I started seeing patterns, so I

[vpp-dev] more per-patch vpp performance jobs

Current "perftest" job only runs on 2n-skx testbed. People were asking for a job running on other testbeds as well. So, I have prepared a solution. CSIT part: [1], ci-management part: [2]. It will take few hours for Sandbox runs to get a testbed and finish. The downside is that I have not figure

Re: [vpp-dev] more per-patch vpp performance jobs

> and to let people know that simple "perftest" trigger > will stop working if the solution is merged as is. It has been merged, around 85 minutes ago. Vratko. From: Vratko Polak -X (vrpolak - PANTHEON TECHNOLOGIES at Cisco) Sent: Monday, 2019-February-18 17:26 To: vpp-dev@lists.fd.io Cc: csit-

Re: [vpp-dev] VPP plugins development in Go

> cgo might just about work > it cost around 300 clock cycles to cross the c <---> golang boundary Aside of cgo [1], there is also gccgo [2]. But I imagine the performance would still be not good enough. Vratko. [1] https://golang.org/cmd/cgo/ [2] https://golang.org/doc/install/gccgo From: vpp-

Re: Re： [vpp-dev] is sw_interface_dump api bug?

>> 4) sw_interface_dump return loop10's info instead of loop1 > predictable behavior Probably it would be sufficient to just improve the current [1] documentation. Vratko. [1] https://github.com/FDio/vpp/blob/f49ba0e81e0cb9b9f8075cb4ce051b5bacde8ad3/src/vnet/interface.api#L206 From: vpp-dev@l

Re: Re： [vpp-dev] is sw_interface_dump api bug?

> Hope this can help: https://gerrit.fd.io/r/#/c/18302/ I prefer https://gerrit.fd.io/r/18299 Vratko. -Original Message- From: Yohan Pipereau (ypiperea) Sent: Thursday, 2019-March-14 18:33 To: Vratko Polak -X (vrpolak - PANTHEON TECHNOLOGIES at Cisco) ; Dave Barach (dbarach) ; "Zhou Y

[vpp-dev] release commit rule

One sentence from miletone e-mails caught my attention: > Commit first to the release throttle, > then "git cherry-pick" into master I have tried searching for context. I have found this [0] wiki edit, with just > Here are a few common-sense suggestions: as an explanation. When I was working on O

  1   2   >