Re: [vpp-dev] Regarding DPDK's rte_timer api's usage with VPP

2023-03-27 Thread Dave Barach
How about replacing this part of rte_timer_subsystem_init(): 

mz = rte_memzone_lookup(mz_name);
if (mz == NULL) {
mz = rte_memzone_reserve_aligned(mz_name, mem_size,
SOCKET_ID_ANY, 0, RTE_CACHE_LINE_SIZE);
if (mz == NULL) {
rte_mcfg_timer_unlock();
return -ENOMEM;
}
do_full_init = true;
} else
do_full_init = false;

with either a call to clib_mem_alloc_aligned() or clib_pmalloc_alloc_aligned() 
depending on mem_size? There appears to be one
call to rte_memzone_free() which would also need an adjustment.

FWIW... Dave

-Original Message-
From: vpp-dev@lists.fd.io  On Behalf Of Prashant Upadhyaya
Sent: Monday, March 27, 2023 1:07 AM
To: vpp-dev 
Subject: [vpp-dev] Regarding DPDK's rte_timer api's usage with VPP

Hi,

I am bringing in some legacy code which worked with DPDK standalone, and 
converting it into a VPP plugin (VPP 22.10) The legacy code uses the DPDK 
rte_timer api's Now as soon as my VPP plugin calls the DPDK API 
rte_timer_subsystem_init, I get the following error from EAL of DPDK

EAL: memzone_reserve_aligned_thread_unsafe(): Number of requested memzone 
segments exceeds RTE_MAX_MEMZONE

Of course I can uproot the entire timer implementation in legacy code and 
replace it with various other alternatives, but if I can get over the issue I 
have reported above somehow that would be great.

If anybody has resolved a similar issue, please do advise.

Regards
-Prashant


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#22771): https://lists.fd.io/g/vpp-dev/message/22771
Mute This Topic: https://lists.fd.io/mt/97876096/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [vpp-dev] How to check stack size of process node

2023-03-25 Thread Dave Barach
Find the current process index: vlib_node_main_t *nm = >node_main; 
current_process_index = nm->current_process_index;

 

Find the process object:   vlib_process_t *p = vec_elt (nm->processes, 
current_process_index);

 

Find the stack base: p->stack

 

Take the address of a local variable in a function at what you think is the 
maximum stack depth, and subtract. That’s the instantaneous stack depth. 

 

You can sprinkle “stack_depth_now = p->stack -  if (stack_depth_now > 
max_stack_depth) max = now” cookies in various places.

 

HTH...

 

From: vpp-dev@lists.fd.io  On Behalf Of chetan bhasin
Sent: Friday, March 24, 2023 9:24 AM
To: vpp-dev 
Subject: Re: [vpp-dev] How to check stack size of process node

 

Hi,

 

Please share any thoughts on this.

 

Thanks,

 

On Sat, Mar 18, 2023, 13:18 chetan bhasin via lists.fd.io   
mailto:gmail@lists.fd.io> > wrote:

Hi vpp-team,

 

 

Could you please provide a way via which a process node stack size can be 
calculated. We are creating a process node, how to figure out the value of 
process_log2_n_stack_bytes??

 

Thanks,

 






-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#22764): https://lists.fd.io/g/vpp-dev/message/22764
Mute This Topic: https://lists.fd.io/mt/97689882/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [vpp-dev] Race condition between bihash deletion and searching - misuse or bug?

2023-03-16 Thread Dave Barach
Please see https://gerrit.fd.io/r/c/vpp/+/38507 

 

-Original Message-

From: vpp-dev@lists.fd.io <mailto:vpp-dev@lists.fd.io>  mailto:vpp-dev@lists.fd.io> > On Behalf Of Hao Tian

Sent: Wednesday, March 15, 2023 10:14 PM

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

Subject: Re: [vpp-dev] Race condition between bihash deletion and searching - 
misuse or bug?

 

Hi Dave,

 

Thanks for your work. I am ready to test whenever needed.

 

Best regards,

Hao Tian

 



From: vpp-dev@lists.fd.io <mailto:vpp-dev@lists.fd.io>  mailto:vpp-dev@lists.fd.io> > on behalf of Dave Barach mailto:v...@barachs.net> >

Sent: Thursday, March 16, 2023 7:02 AM

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

Subject: Re: [vpp-dev] Race condition between bihash deletion and searching - 
misuse or bug?

 

I'm doing a bit of work to straighten out the template, hopefully without 
causing a measurable performance regression.

 

Hao's test code is a bit of a corner-case: there is exactly one record in the 
database which the code thrashes as hard as possible.

 

D.

 

-Original Message-

From: vpp-dev@lists.fd.io <mailto:vpp-dev@lists.fd.io>  mailto:vpp-dev@lists.fd.io> > On Behalf Of Andrew Yourtchenko

Sent: Wednesday, March 15, 2023 12:33 PM

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

Subject: Re: [vpp-dev] Race condition between bihash deletion and searching - 
misuse or bug?

 

Hao,

 

I noticed the same behavior when stress-testing the multi thread session 
handling for the ACL plugin a while ago. I thought this trade off is there to 
avoid having to do the hard locks in bihash code, rather than it being a bug.

 

As you say - the special value comes only if the deletion is in progress, and 
it is always the same. So I just treated that case in my code same as “not 
found”.

 

My logic was: if an entry is just in process of being deleted, there is very 
little use for its old value anyway.

 

--a

 

> On 15 Mar 2023, at 14:45, Hao Tian  <mailto:tianhao...@outlook.com> > wrote:

> 

> Hi,

> 

> I tried but could not come up with any way that is able to ensure the kvp 
> being valid upon return without using the full bucket lock.

> 

> Maybe we can make a copy of the value before returning, validate the copy and 
> return that copy instead. Critical section can be shrinked to cover only the 
> copying process, which seems to perform better, but I'm not sure if this is 
> the best approach.

> 

> Could you please shed some light here? Thanks!

> 

> Regards,

> Hao Tian

> 

 

 


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#22714): https://lists.fd.io/g/vpp-dev/message/22714
Mute This Topic: https://lists.fd.io/mt/97599770/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [vpp-dev] Race condition between bihash deletion and searching - misuse or bug?

2023-03-15 Thread Dave Barach
I'm doing a bit of work to straighten out the template, hopefully without 
causing a measurable performance regression.

Hao's test code is a bit of a corner-case: there is exactly one record in the 
database which the code thrashes as hard as possible.

D.

-Original Message-
From: vpp-dev@lists.fd.io  On Behalf Of Andrew Yourtchenko
Sent: Wednesday, March 15, 2023 12:33 PM
To: vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] Race condition between bihash deletion and searching - 
misuse or bug?

Hao,

I noticed the same behavior when stress-testing the multi thread session 
handling for the ACL plugin a while ago. I thought this trade off is there to 
avoid having to do the hard locks in bihash code, rather than it being a bug.

As you say - the special value comes only if the deletion is in progress, and 
it is always the same. So I just treated that case in my code same as “not 
found”.

My logic was: if an entry is just in process of being deleted, there is very 
little use for its old value anyway.

--a

> On 15 Mar 2023, at 14:45, Hao Tian  wrote:
> 
> Hi,
> 
> I tried but could not come up with any way that is able to ensure the kvp 
> being valid upon return without using the full bucket lock.
> 
> Maybe we can make a copy of the value before returning, validate the copy and 
> return that copy instead. Critical section can be shrinked to cover only the 
> copying process, which seems to perform better, but I'm not sure if this is 
> the best approach.
> 
> Could you please shed some light here? Thanks!
> 
> Regards,
> Hao Tian
> 


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#22711): https://lists.fd.io/g/vpp-dev/message/22711
Mute This Topic: https://lists.fd.io/mt/97599770/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [vpp-dev] Race condition between bihash deletion and searching - misuse or bug?

2023-03-15 Thread Dave Barach
Doubling the number of atomic ops was expected to cause a severe performance
regression. This hack demonstrates that the test code wasn't responsible. A
bit of extra suspicion in clib_bihash_search_inline_2_with_hash() will
likely solve the problem without the huge performance regression. 

D.  

-Original Message-
From: vpp-dev@lists.fd.io  On Behalf Of Hao Tian
Sent: Tuesday, March 14, 2023 9:47 PM
To: vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] Race condition between bihash deletion and searching
- misuse or bug?

Hi,

I've done the change you asked, and the "suspicious value" warnings are all
gone. Here is the diff:

diff --git a/src/vppinfra/bihash_template.h b/src/vppinfra/bihash_template.h
index c4e120e4a..b9f658db3 100644
--- a/src/vppinfra/bihash_template.h
+++ b/src/vppinfra/bihash_template.h
@@ -532,12 +532,7 @@ static inline int BV
(clib_bihash_search_inline_2_with_hash)
   if (PREDICT_FALSE (BV (clib_bihash_bucket_is_empty) (b)))
 return -1;
 
-  if (PREDICT_FALSE (b->lock))
-{
-  volatile BVT (clib_bihash_bucket) * bv = b;
-  while (bv->lock)
-   CLIB_PAUSE ();
-}
+  BV (clib_bihash_lock_bucket) (b);
 
   v = BV (clib_bihash_get_value) (h, b->offset);
 
@@ -557,9 +552,11 @@ static inline int BV
(clib_bihash_search_inline_2_with_hash)
   if (BV (clib_bihash_key_compare) (v->kvp[i].key, search_key->key))
{
  *valuep = v->kvp[i];
+ BV (clib_bihash_unlock_bucket) (b);
  return 0;
}
 }
+  BV (clib_bihash_unlock_bucket) (b);
   return -1;
 }
 

Some questions regarding the change:

1. There is similar logic in clib_bihash_search_inline_with_hash. I suppose
that this change needs to be applied there as well. Am I right?

2. This patch does eliminate the race condition, but appears to introduce a
huge performance regression. The clocks in `show runtime` will double after
the change (with the 10-ops limit removed, so the test node runs
indefinitely).

Regards,
Hao Tian


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#22708): https://lists.fd.io/g/vpp-dev/message/22708
Mute This Topic: https://lists.fd.io/mt/97599770/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [vpp-dev] Race condition between bihash deletion and searching - misuse or bug?

2023-03-14 Thread Dave Barach
Quick experiment: in
src/vppinfra/bihash_template.h:clib_bihash_search_inline_2_with_hash(),
replace this:

  if (PREDICT_FALSE (b->lock))
{
  volatile BVT (clib_bihash_bucket) * bv = b;
  while (bv->lock)
CLIB_PAUSE ();
}

With:

BV(clib_bihash_lock_bucket(b));

and make sure to BV(clib_bihash_unlock_bucket(b)); just prior to return 0
and return -1 in that function.

Please let me know what happens. 

Thanks... Dave

-Original Message-
From: vpp-dev@lists.fd.io  On Behalf Of Hao Tian
Sent: Tuesday, March 14, 2023 4:13 AM
To: vpp-dev@lists.fd.io
Subject: [vpp-dev] Race condition between bihash deletion and searching -
misuse or bug?

Hi all,

I found that bihash might return zero'ed value (0xff's) if deletion and
searching were performed in parallel on different threads. This is
reproducible by only ~100 lines of code, from 21.06 all the way up to git
master, and on multiple machines from Coffee Lake to Tiger Lake.

The code (a plugin) and test command is shown below. Given how easy it is to
reproduce the problem, I'm not sure whether this is a bug or something
missing on my end. Any advice is welcomed. Thanks!

 bihash_race.c 

#include 
#include 
#include 

static volatile int br_run;
static clib_bihash_8_8_t br_bihash_8_8;
static int test_run_cnt[2];

static void
bihash_race_set (u64 key)
{
  clib_bihash_kv_8_8_t kv = { .key = key, .value = 1 };

  clib_bihash_add_del_8_8 (_bihash_8_8, , BIHASH_ADD); }

static void
bihash_race_del (u64 key)
{
  clib_bihash_kv_8_8_t kv = { .key = key, .value = 1 };

  clib_bihash_add_del_8_8 (_bihash_8_8, , BIHASH_DEL); }

static void
bihash_race_get (u64 key)
{
  clib_bihash_kv_8_8_t kv = { .key = key, .value = 1 };
  clib_bihash_kv_8_8_t value;

  if (!clib_bihash_search_8_8 (_bihash_8_8, , ))
    {
  if (value.value != 1)
    {
  clib_warning ("suspicious value: 0x%lx\n", value.value);
    }
    }
}

static clib_error_t *
bihash_race_init (vlib_main_t *vm)
{
  clib_bihash_init_8_8 (_bihash_8_8, "bihash_race hash", 4096, 4096 *
256);

  return 0;
}

VLIB_NODE_FN (br_test_node)
(vlib_main_t *vm, vlib_node_runtime_t *node, vlib_frame_t *frame) {
  u64 k = 0x01010101UL;

  if (!br_run || vm->thread_index == 0)
    {
  return 0;
    }

  // perform bihash set and delete for 5 times each in thread 1
  if (vm->thread_index == 1 && test_run_cnt[0] < 10)
    {
  if (test_run_cnt[1] & 1)
    bihash_race_del (k);
  else
    bihash_race_set (k);
  test_run_cnt[0]++;
  return 0;
    }

  // perform bihash lookup for 10 times in thread 2
  if (vm->thread_index == 2 && test_run_cnt[1] < 10)
    {
  bihash_race_get (k);
  test_run_cnt[1]++;
  return 0;
    }
  return 0;
}

void
bihash_race_test_reset ()
{
  memset (test_run_cnt, 0, sizeof (test_run_cnt));
  clib_warning ("== test reset =="); }

static clib_error_t *
bihash_race_test_command_fn (vlib_main_t *vm, unformat_input_t *input,
 vlib_cli_command_t *cmd) {
  u8 state = ~0;

  while (unformat_check_input (input) != UNFORMAT_END_OF_INPUT)
    {
  if (unformat (input, "on"))
    state = 1;
  else if (unformat (input, "off"))
    state = 0;
  else
    return clib_error_return (0, "invalid input");
    }

  if (state)
    {
  br_run = 1;
    }
  else
    {
  br_run = 0;
  bihash_race_test_reset ();
  vlib_cli_output (vm, "== test reset ==");
    }

  return 0;
}

VLIB_CLI_COMMAND (bihash_race_test_command, static) = {
  .path = "set bihash-race-test",
  .short_help = "set bihash-race-test |",
  .function = bihash_race_test_command_fn, };

VLIB_REGISTER_NODE (br_test_node) = {
  .name = "bihash-race-test",
  .type = VLIB_NODE_TYPE_INPUT,
  .state = VLIB_NODE_STATE_POLLING,
};

VLIB_INIT_FUNCTION (bihash_race_init);

VLIB_PLUGIN_REGISTER () = {
  .version = VPP_BUILD_VER,
  .description = "bihash race test",
};

= CMakeLists.txt =

add_vpp_plugin(bihash_race
  SOURCES
  bihash_race.c
)

= startup.conf =

unix {
  nodaemon
  full-coredump
  cli-listen /run/vpp/cli.sock
  gid 1000
  interactive
}

cpu {
  workers 3
  main-core 1
}

dpdk {
  no-pci
}

= test command =

terminal1 # vpp -c startup.conf
terminal2 # while true; do vppctl set bihash-race-test on; sleep 1; vppctl
set bihash-race-test off; done

VPP will spit out a lot of "suspicious value: 0x" in
terminal1, while the code above never saves such value into bihash - the
value comes from the !is_add branch in clib_bihash_add_del_inline_with_hash.
Changing the memset value (and clib_bihash_is_free_* obviously) in this
branch will lead to this new value being returned.

Regards,
Hao Tian


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all 

Re: [vpp-dev] process node suspended indefinitely

2023-03-10 Thread Dave Barach
I should have had the sense to ask this earlier: which version of vpp are you 
using? 

 

The line number in your debug snippet is more than 100 lines off from 
master/latest. The timer wheel code has been relatively untouched, but there 
have been several important fixes over the years...

 

D.

 

diff --git a/src/vlib/main.c b/src/vlib/main.c
index af0fcd1cb..55c231d8b 100644
--- a/src/vlib/main.c
+++ b/src/vlib/main.c
@@ -1490,6 +1490,9 @@ dispatch_suspended_process (vlib_main_t * vm,
 }
   else
 {
+   if (strcmp((char *)node->name, "rtb-vpp-epoll-process") == 0) {
+   ASSERT(0);
+   }

 

From: vpp-dev@lists.fd.io  On Behalf Of Sudhir CR via 
lists.fd.io
Sent: Thursday, March 9, 2023 4:00 AM
To: vpp-dev@lists.fd.io
Cc: rtbrick@lists.fd.io
Subject: Re: [vpp-dev] process node suspended indefinitely

 

Hi Dave,

Please excuse my delayed response. It took some time to recreate this issue.

I made changes to our process node as per your suggestion. now our process node 
code looks like this

 

while (1) {

vlib_process_wait_for_event_or_clock (vm, 
RTB_VPP_EPOLL_PROCESS_NODE_TIMER);
event_type = vlib_process_get_events (vm, _data);
vec_reset_length(event_data);

switch (event_type) {
case ~0: /* handle timer expirations */
rtb_event_loop_run_once ();
break;

default: /* bug! */
ASSERT (0);
}
}

After these changes we didn't observe any assertions but we hit the process 
node suspend issue. with this it is clear other than time out we are not 
getting any other events.

 

In the issue state I have collected vlib_process node (rtb_vpp_epoll_process) 
flags value and it seems to be correct (flags = 11).

 

Please find the vlib_process_t and vlib_node_t data structure values collected 
in the issue state below.

 

vlib_process_t:



$38 = {
  cacheline0 = 0x7f9b2da50380 "\200~\274+\233\177", 
  node_runtime = {
cacheline0 = 0x7f9b2da50380 "\200~\274+\233\177", 
function = 0x7f9b2bbc7e80 , 
errors = 0x7f9b3076a560, 
clocks_since_last_overflow = 0, 
max_clock = 3785970526, 
max_clock_n = 0, 
calls_since_last_overflow = 0, 
vectors_since_last_overflow = 0, 
next_frame_index = 1668, 
node_index = 437, 
input_main_loops_per_call = 0, 
main_loop_count_last_dispatch = 4147405645, 
main_loop_vector_stats = {0, 0}, 
flags = 0, 
state = 0, 
n_next_nodes = 0, 
cached_next_index = 0, 
thread_index = 0, 
runtime_data = 0x7f9b2da503c6 ""
  }, 
  return_longjmp = {
regs = {94502584873984, 140304430422064, 140306731463680, 94502584874048, 
94502640552512, 0, 140304430422032, 140306703608766}
  }, 
  resume_longjmp = {
regs = {94502584873984, 140304161734368, 140306731463680, 94502584874048, 
94502640552512, 0, 140304161734272, 140304430441787}
  }, 
  flags = 11, 
  log2_n_stack_bytes = 16, 
  suspended_process_frame_index = 0, 
  n_suspends = 0, 
  pending_event_data_by_type_index = 0x7f9b307b8310, 
  non_empty_event_type_bitmap = 0x7f9b307b8390, 
  one_time_event_type_bitmap = 0x0, 
  event_type_index_by_type_opaque = 0x7f9b2dab8bd8, 
  event_type_pool = 0x7f9b2dcb5978, 
  resume_clock_interval = 1000, 
  stop_timer_handle = 3098, 
  output_function = 0x0, 
  output_function_arg = 0, 
  stack = 0x7f9b1bb78000
}

 

vlib_node_t

=

 (gdb) p *n

$17 = {
  function = 0x7f9b2bbc7e80 , 
  name = 0x7f9b3076a3f0 "rtb-vpp-epoll-process", 
  name_elog_string = 11783, 
  stats_total = {
calls = 0, 
vectors = 0, 
clocks = 1971244932732, 
suspends = 6847366, 
max_clock = 3785970526, 
max_clock_n = 0
  }, 
  stats_last_clear = {
calls = 0, 
vectors = 0, 
clocks = 0, 
suspends = 0, 
max_clock = 0, 
max_clock_n = 0
  }, 
  type = VLIB_NODE_TYPE_PROCESS, 
  index = 437, 
  runtime_index = 40, 
  runtime_data = 0x0, 
  flags = 0, 
  state = 0 '\000', 
  runtime_data_bytes = 0 '\000', 
  protocol_hint = 0 '\000', 
  n_errors = 0, 
  scalar_size = 0, 
  vector_size = 0, 
  error_heap_handle = 0, 
  error_heap_index = 0, 
  error_counters = 0x0, 
  next_node_names = 0x7f9b3076a530, 
  next_nodes = 0x0, 
  sibling_of = 0x0, 
  sibling_bitmap = 0x0, 
  n_vectors_by_next_node = 0x0, 
  next_slot_by_node = 0x0, 
  prev_node_bitmap = 0x0, 
  owner_node_index = 4294967295, 
  owner_next_index = 4294967295, 
  format_buffer = 0x0, 
  unformat_buffer = 0x0, 
  format_trace = 0x0, 
  validate_frame = 0x0, 
  state_string = 0x0, 
  node_fn_registrations = 0x0
}

 

I added an assert statement before clearing VLIB_PROCESS_IS_RUNNING flag in 
dispatch_suspended_process function.

But this assert statement is not hitting.

 

diff --git a/src/vlib/main.c b/src/vlib/main.c
index af0fcd1cb..55c231d8b 100644
--- a/src/vlib/main.c
+++ b/src/vlib/main.c
@@ -1490,6 +1490,9 @@ dispatc

Re: [vpp-dev] failure while building VPP v23.02 in centos 7 VM

2023-03-09 Thread Dave Wallace

Hi Sandeep,

The VPP community no longer supports building on CentOS-7.  The build 
infrastructure for centos/redhat/rocky OS distros was left in place 
after support ended, but there are no active maintainers for this build 
infra nor are there any CI jobs to ensure that it still works.


You may get lucky and a community member may chime in, but for the most 
part you are on your own wrt. getting currently supported VPP releases 
to build on CentOS-7.


Thanks,
-daw-

On 3/9/2023 11:56 AM, SANDEEP KUMAR wrote:

Hi All,

I am trying to build VPP v23.02 but getting an issue while performing 
the *make install-ext-deps* step in centos 7 VM, so please look at the 
following issue and help me to resolve it.


*Prerequisites:*
sudo yum groupinstall "Development Tools"
sudo yum install -y numactl-devel libarchive-devel bzip2-devel  
libpcap-devel libhugetlbfs-utils pciutils pkgconfig libtool ethtool

sudo yum -y install libibverbs
sudo yum -y groupinstall "Infiniband Support"
sudo yum install -y numactl-devel librdmacm-devel libmnl-devel libatomic

#Download and install nasm
wget https://www.nasm.us/pub/nasm/releasebuilds/2.15/nasm-2.15.tar.gz
tar -xzvf nasm-2.15.tar.gz
cd nasm-2.15/
sh autogen.sh
sh configure --prefix=/usr/local/
make
sudo make install
sudo ldconfig

#Download and install the latest libpcap
git clone https://github.com/the-tcpdump-group/libpcap.git
cd libpcap
git checkout libpcap-1.10.0
./autogen.sh
./configure
make
make install
sudo ldconfig

#Download and build clang with 10.x version
git clone -b llvmorg-10.0.1  --depth 1 
https://github.com/llvm/llvm-project.git

cd llvm-project
mkdir build && cd build
cmake -G "Unix Makefiles" 
-DLLVM_ENABLE_PROJECTS="clang;clang-tools-extra" 
-DCMAKE_INSTALL_PREFIX=/usr/local -DCMAKE_BUILD_TYPE=Release ../llvm

make -j 8
sudo make install
sudo ldconfig

To download the pre-compiled cmake v3.23
wget 
https://github.com/Kitware/CMake/releases/download/v3.23.0-rc4/cmake-3.23.0-rc4-linux-x86_64.tar.gz 


tar -xzvf cmake-3.23.0-rc4-linux-x86_64.tar.gz
cd cmake-3.23.0-rc4-linux-x86_64
cp -v ./bin/cmake /usr/local/bin
cp -r ./share/cmake-3.23 /usr/local/share
sudo ldconfig

*Using gcc version 9.3.x while build VPP v23.02*
sudo yum install -y centos-release-scl
sudo yum install -y devtoolset-9
scl enable devtoolset-9 bash
[root@localhost vpp]# gcc --version
gcc (GCC) 9.3.1 20200408 (Red Hat 9.3.1-2)
Copyright (C) 2019 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR 
PURPOSE.


*Using centos 7 and kernel used*
[root@localhost vpp]#*cat /etc/os-release*
NAME="CentOS Linux"
VERSION="7 (Core)"
ID="centos"
ID_LIKE="rhel fedora"
VERSION_ID="7"
PRETTY_NAME="CentOS Linux 7 (Core)"
ANSI_COLOR="0;31"
CPE_NAME="cpe:/o:centos:centos:7"
HOME_URL="https://www.centos.org/;
BUG_REPORT_URL="https://bugs.centos.org/;

CENTOS_MANTISBT_PROJECT="CentOS-7"
CENTOS_MANTISBT_PROJECT_VERSION="7"
REDHAT_SUPPORT_PRODUCT="centos"
REDHAT_SUPPORT_PRODUCT_VERSION="7"

[root@localhost vpp]# *uname -r*
3.10.0-1160.71.1.el7.x86_64


*Git clone VPP and build VPP v23.02*
git clone https://gerrit.fd.io/r/vpp
cd vpp
git tag
git checkout v23.02
make install-deps

Following issue coming while performing make install-ext-deps step
*make install-ext-deps*
*...*
*...*
*..*
Installing 
/home/centos/download_vpp/vpp/build/external/rpm/tmp/build-dpdk/meson-private/libdpdk.pc 
to 
/home/centos/download_vpp/vpp/build/external/rpm/BUILDROOT/vpp-ext-deps-23.02-8.

x86_64/opt/vpp/external/x86_64/lib/pkgconfig
Running custom install script '/bin/sh 
/home/centos/download_vpp/vpp/build/external/rpm/tmp/src-dpdk/config/../buildtools/symlink-drivers-solibs.sh 
lib dpdk/pmds-22.2'
--- installing quicly 0.1.4-vpp - log: 
/home/centos/download_vpp/vpp/build/external/rpm/tmp/quicly.install.log

mkdir -p downloads
Downloading 
https://github.com/xdp-project/xdp-tools/releases/download/v1.2.9/xdp-tools-1.2.9.tar.gz
  % Total    % Received % Xferd  Average Speed   Time    Time     Time 
 Current
                                 Dload  Upload   Total   Spent    Left 
 Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- 
--:--:--     0
100 1177k  100 1177k    0     0   271k      0  0:00:04  0:00:04 
--:--:--  468k

--- validating xdp-tools 1.2.9 checksum
--- extracting xdp-tools 1.2.9
--- patching xdp-tools 1.2.9
Applying patch: 0001-libxdp-add-fPIC-with-static-lib-build.patch
patching file lib/libxdp/Makefile
Applying patch: 0002-libxdp-fix-asm-types.h-file-not-found-issue.patch
patching file lib/defines.mk 
Applying patch: 0003-libxdp-fix-maybe-uninitialized-compiler-warning.patch
patching file lib/common.mk 
--- configuring xdp-tools 1.2.9 - log: 
/home/centos/download_vpp/vpp/build/external/rpm/tmp/xdp-tools.config.log
--- building xdp-tools 1.2.9 - log: 

[vpp-dev] RFC: VPP Build Artifact Retention Policy

2023-03-06 Thread Dave Wallace

Folks,

As discussed in the last 2 VPP Community meetings, I have created a 
draft build artifact policy for the VPP project [0].


Please review and provide comments to this email thread.

Thanks,
-daw-

[0] https://wiki.fd.io/view/VPP/BuildArtifactRetentionPolicy

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#22669): https://lists.fd.io/g/vpp-dev/message/22669
Mute This Topic: https://lists.fd.io/mt/97437987/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [vpp-dev] FW: Bug: DHCP Client not sending DHCP REQUEST using VPP v22.02

2023-03-02 Thread Dave Barach
The dhcp client has a number of “show error” counters. Do you see any of the error counters increasing? The packet trace I’d like to see would be from “trace add  1000” … “show trace max 1000” or similar. The pcap trace implies that the dhcp offer packets are dropped, but we need to work out why… D.  From: vpp-dev@lists.fd.io  on behalf of hemant via lists.fdio Date: Thursday, March 2, 2023 at 7:13 PMTo: vpp-dev@lists.fd.io Subject: Re: [vpp-dev] FW: Bug: DHCP Client not sending DHCP REQUEST using VPP v22.02There is something in the DHCP OFFER the client does not like and moves back to new DHCP session. Or the DHCP OFFER never made it to the client. Hemant  From: vpp-dev@lists.fd.io  On Behalf Of Thakur, AnaghaSent: Thursday, March 02, 2023 4:02 PMTo: vpp-dev@lists.fd.ioSubject: Re: [vpp-dev] FW: Bug: DHCP Client not sending DHCP REQUEST using VPP v22.02 I do see DHCP Offer in the packet tracer from the Server which I have set up on the other side.But VPP does not send any DHCP Request out, instead I always see that VPP continuously keeps sending DHCP Discovery. I have attached tx and rx pcap trace in my prevous email. Best Regards,Anagha From: vpp-dev@lists.fd.io <vpp-dev@lists.fd.io> on behalf of Dave Barach via lists.fd.io <vpp=barachs@lists.fd.io>Sent: Thursday, 2 March 2023, 19:15To: vpp-dev@lists.fd.io <vpp-dev@lists.fd.io>Subject: Re: [vpp-dev] FW: Bug: DHCP Client not sending DHCP REQUEST using VPP v22.02Do you see a response to the DHCP Discover packets?   What does the vpp packet tracer show?Thanks... Dave On Mar 2, 2023, at 7:03 AM, Thakur, Anagha <anagha.tha...@siemens.com> wrote:  Hello, I am testing DHCP client feature from VPP stack (v22.02) onto our system. My setup is: I run k8s cluster on x86 system in which I have a pod which uses VPP stack and it accesses physical NIC interface using DPDK and SR-IOV. There are two physical interfaces which we use in VPP, one of them is with static IP (eno2) and other one with as DHCP client (eno1). I expect this interface shall act as a DHCP Client and we run a DHCP server on the other end of the system. But unfortunately, the VPP does not send any DHCP REQUEST. It keeps sending DHCP DISCOVERY every interval. It receives a DHCP Offer.But VPP does not send further DHCP REQUEST to the DHCP server. I do not expect that it is a problem from lower layer and it should be an issue from VPP side. Please let me know if I need to enable any extra plugin other than the ones in the attached file.I attached pcap file recorded vpp trace of tx and rx.  Our versions are currently as follows:-> DPDK 22.03-> VPP 22.02-> VPP library 22.02 Version Information attached. plugins{  path /opt /vpp/lib/vpp_plugins  plugin default { disable }  plugin dpdk_plugin.so { enable }  plugin memif_plugin.so { enable }  plugin ping_plugin.so { enable }  plugin router_plugin.so { enable }  plugin upffp_plugin.so { enable }  plugin dhcp_plugin.so { enable }}  Commands used:set intfc VPP-N6-0 state upset int mac address eno1 00:11:22:33:44:66set dhcp client intfc eno1sh dhcp client verbose[0] VPP-N6-0 state DHCP_DISCOVER installed 0 no addresslease: lifetime:0 renewal-interval:0 expires:0.00 (now:2412.35)  retry-count:346, next-xmt:2416.87broadcast adjacency:20sh log2023/02/27 16:11:03:986 notice dhcp/client    sm active session 02023/02/27 16:11:03:986 notice dhcp/client    send: type:discover bcast:1 [0] VPP-N6-0 state DHCP_DISCOVER installed 0 no addresslease: lifetime:0 renewal-interval:0 expires:0.00 (now:255827.12)retry-count:439, next-xmt:255827.12broadcast adjacency:112023/02/27 16:11:08:986 notice dhcp/client    sm active session 02023/02/27 16:11:08:986 notice dhcp/client    send: type:discover bcast:1 [0] VPP-N6-0 state DHCP_DISCOVER installed 0 no addresslease: lifetime:0 renewal-interval:0 expires:0.00 (now:255832.12)retry-count:440, next-xmt:255832.12broadcast adjacency:112023/02/27 16:11:13:986 notice dhcp/client    sm active session 02023/02/27 16:11:13:986 notice dhcp/client    send: type:discover bcast:1 [0] VPP-N6-0 state DHCP_DISCOVER installed 0 no address  lease: lifetime:0 renewal-interval:0 expires:0.00 (now:255837.12)  retry-count:441, next-xmt:255837.12broadcast adjacency:112023/02/27 16:11:18:986 notice dhcp/client    sm active session 02023/02/27 16:11:18:986 notice dhcp/client    send: type:discover bcast:1 [0] VPP-N6-0 state DHCP_DISCOVER installed 0 no addresslease: lifetime:0 renewal-interval:0 expires:0.00 (now:255842.12)retry-count:442, next-xmt:255842.12  broadcast adjacency:11show interface addresseno2 (up):   L3 172.31.254.17/29eno1 (up):host-vpp1out (up):   L3 128.0.129.144/24local0 (dn):memif0/502 (up):  Thank you in advance. Best Regards,Anagha

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#22657): https://lists.fd.io/g/vpp-dev/message/22657
Mute This Topic

Re: [vpp-dev] FW: Bug: DHCP Client not sending DHCP REQUEST using VPP v22.02

2023-03-02 Thread Dave Barach
Do you see a response to the DHCP Discover packets? 

What does the vpp packet tracer show?

Thanks... Dave

> On Mar 2, 2023, at 7:03 AM, Thakur, Anagha  wrote:
> 
> 
>  
> Hello,
>  
> I am testing DHCP client feature from VPP stack (v22.02) onto our system.
>  
> My setup is: I run k8s cluster on x86 system in which I have a pod which uses 
> VPP stack and it accesses physical NIC interface using DPDK and SR-IOV. There 
> are two physical interfaces which we use in VPP, one of them is with static 
> IP (eno2) and other one with as DHCP client (eno1).
>  
> I expect this interface shall act as a DHCP Client and we run a DHCP server 
> on the other end of the system. But unfortunately, the VPP does not send any 
> DHCP REQUEST. It keeps sending DHCP DISCOVERY every interval. It receives a 
> DHCP Offer.
> But VPP does not send further DHCP REQUEST to the DHCP server. I do not 
> expect that it is a problem from lower layer and it should be an issue from 
> VPP side. Please let me know if I need to enable any extra plugin other than 
> the ones in the attached file.
> I attached pcap file recorded vpp trace of tx and rx.
>  
>  
> Our versions are currently as follows:
> -> DPDK 22.03
> -> VPP 22.02
> -> VPP library 22.02
>  
> Version Information attached.
>  
> plugins
> {
>   path /opt /vpp/lib/vpp_plugins
>   plugin default { disable }
>   plugin dpdk_plugin.so { enable }
>   plugin memif_plugin.so { enable }
>   plugin ping_plugin.so { enable }
>   plugin router_plugin.so { enable }
>   plugin upffp_plugin.so { enable }
>   plugin dhcp_plugin.so { enable }
> }
>  
>  
> Commands used:
> set intfc VPP-N6-0 state up
> set int mac address eno1 00:11:22:33:44:66
> set dhcp client intfc eno1
> sh dhcp client verbose
> [0] VPP-N6-0 state DHCP_DISCOVER installed 0 no address
> lease: lifetime:0 renewal-interval:0 expires:0.00 (now:2412.35)
>   retry-count:346, next-xmt:2416.87
> broadcast adjacency:20
> sh log
> 2023/02/27 16:11:03:986 notice dhcp/clientsm active session 0
> 2023/02/27 16:11:03:986 notice dhcp/clientsend: type:discover bcast:1 
> [0] VPP-N6-0 state DHCP_DISCOVER installed 0 no address
> lease: lifetime:0 renewal-interval:0 expires:0.00 (now:255827.12)
> retry-count:439, next-xmt:255827.12
> broadcast adjacency:11
> 2023/02/27 16:11:08:986 notice dhcp/clientsm active session 0
> 2023/02/27 16:11:08:986 notice dhcp/clientsend: type:discover bcast:1 
> [0] VPP-N6-0 state DHCP_DISCOVER installed 0 no address
> lease: lifetime:0 renewal-interval:0 expires:0.00 (now:255832.12)
> retry-count:440, next-xmt:255832.12
> broadcast adjacency:11
> 2023/02/27 16:11:13:986 notice dhcp/clientsm active session 0
> 2023/02/27 16:11:13:986 notice dhcp/clientsend: type:discover bcast:1 
> [0] VPP-N6-0 state DHCP_DISCOVER installed 0 no address
>   lease: lifetime:0 renewal-interval:0 expires:0.00 
> (now:255837.12)
>   retry-count:441, next-xmt:255837.12
> broadcast adjacency:11
> 2023/02/27 16:11:18:986 notice dhcp/clientsm active session 0
> 2023/02/27 16:11:18:986 notice dhcp/clientsend: type:discover bcast:1 
> [0] VPP-N6-0 state DHCP_DISCOVER installed 0 no address
> lease: lifetime:0 renewal-interval:0 expires:0.00 (now:255842.12)
> retry-count:442, next-xmt:255842.12
>   broadcast adjacency:11
> show interface address
> eno2 (up):
>L3 172.31.254.17/29
> eno1 (up):
> host-vpp1out (up):
>L3 128.0.129.144/24
> local0 (dn):
> memif0/502 (up):
>  
>  
> Thank you in advance.
>  
> Best Regards,
> Anagha
>  
>  
> 
> 
> 
> 
> 

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#22652): https://lists.fd.io/g/vpp-dev/message/22652
Mute This Topic: https://lists.fd.io/mt/97336867/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [vpp-dev] docker pkg-deb?

2023-02-28 Thread Dave Wallace

Hemant,

VPP build infrastructure does not currently support building docker 
images containing the VPP pkg-deb.  You'll have to create your own 
Dockerfile to do so.


Thanks,
-daw-

On 2/28/2023 3:09 PM, hemant via lists.fd.io wrote:


Folks,

I use “sudo make pkg-deb” to build.

How to I build a docker image for pkg-deb?

Hemant





-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#22638): https://lists.fd.io/g/vpp-dev/message/22638
Mute This Topic: https://lists.fd.io/mt/97298934/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [vpp-dev] [vpp-build] VPP build error on Ubuntu 22.04

2023-02-27 Thread Dave Wallace

Thanks for letting us know.
-daw-

On 2/26/2023 8:49 AM, Jens Rösiger via lists.fd.io wrote:

Hi Dave,

i have apply the patch and the build process has no more errors. All 
.deb packages are created.

Thank you very much.

--
Jens




-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#22628): https://lists.fd.io/g/vpp-dev/message/22628
Mute This Topic: https://lists.fd.io/mt/97192445/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



[vpp-dev] [vpp-build] VPP build error on Ubuntu 22.04

2023-02-23 Thread Dave Wallace

Jens,

Forwarding to vpp-dev@lists.fd.io where VPP contributors answer these 
types of questions.


The srtp plugin is not built in the CI [0] and ubuntu-22.04 includes 
version 2.4.2 of libsrtp2 [1].  The ekt field was deprecated in 2.4.0 
since it was never fully implemented and the draft changed [2].


I pinged Florin Coras who maintains the srtp_plugin which is 
experimental and verified that it has been intentionally left out of the 
CI.  I have pushed a fix for the build failure [3], but Florin will need 
to test it before it can be merged.


Please apply the patch and let us know if you run into any more issues.

Thanks,
-daw-

[0] 
https://s3-logs.fd.io/vex-yul-rot-jenkins-1/vpp-verify-master-ubuntu2204-x86_64/1178/console-timestamp.log.gz
    (search for libsrtp2.a -> "17:54:54  -- -- libsrtp2.a library not 
found - srtp plugin disabled"

[1] https://pkgs.org/search/?q=libsrtp2
[2] https://github.com/cisco/libsrtp/releases/tag/v2.4.0
[3] https://gerrit.fd.io/r/c/vpp/+/38345

 Forwarded Message 
Subject:[vpp-build] VPP build error on Ubuntu 22.04
Date:   Thu, 23 Feb 2023 03:26:25 -0800
From:   Jens Rösiger via lists.fd.io 
Reply-To:   vpp-bu...@lists.fd.io
To: vpp-bu...@lists.fd.io



Dear VPP Build Team,

i have a problem to build VPP on Ubuntu 22.04(LTS).

 * no errror on "make install-deps"
 * no errors on "make install-ext-deps"
 * but "make build-release"  give this error:

make[1]: Entering directory '/opt/buildpackage/src/vpp/vpp/build-root'
 Arch for platform 'vpp' is native 
 Finding source for external 
 Makefile fragment found in 
/opt/buildpackage/src/vpp/vpp/build-data/packages/external.mk 

 Source found in /opt/buildpackage/src/vpp/vpp/build 
 Arch for platform 'vpp' is native 
 Finding source for vpp 
 Makefile fragment found in 
/opt/buildpackage/src/vpp/vpp/build-data/packages/vpp.mk 

 Source found in /opt/buildpackage/src/vpp/vpp/src 
 Configuring external in 
/opt/buildpackage/src/vpp/vpp/build-root/build-vpp-native/external 
 Building external in 
/opt/buildpackage/src/vpp/vpp/build-root/build-vpp-native/external 

 Installing external 
make[2]: Entering directory '/opt/buildpackage/src/vpp/vpp/build/external'
make check-deb
make[3]: Entering directory '/opt/buildpackage/src/vpp/vpp/build/external'
make[3]: Nothing to be done for 'check-deb'.
make[3]: Leaving directory '/opt/buildpackage/src/vpp/vpp/build/external'
make[2]: Nothing to be done for 'ebuild-install'.
make[2]: Leaving directory '/opt/buildpackage/src/vpp/vpp/build/external'
 Configuring vpp in 
/opt/buildpackage/src/vpp/vpp/build-root/build-vpp-native/vpp 

-- The C compiler identification is Clang 14.0.0
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: /usr/lib/ccache/clang - skipped
-- Detecting C compile features
-- Detecting C compile features - done
-- Performing Test compiler_flag_march_haswell
-- Performing Test compiler_flag_march_haswell - Success
-- Performing Test compiler_flag_mtune_haswell
-- Performing Test compiler_flag_mtune_haswell - Success
-- Performing Test compiler_flag_march_tremont
-- Performing Test compiler_flag_march_tremont - Success
-- Performing Test compiler_flag_mtune_tremont
-- Performing Test compiler_flag_mtune_tremont - Success
-- Performing Test compiler_flag_march_skylake_avx512
-- Performing Test compiler_flag_march_skylake_avx512 - Success
-- Performing Test compiler_flag_mtune_skylake_avx512
-- Performing Test compiler_flag_mtune_skylake_avx512 - Success
-- Performing Test compiler_flag_mprefer_vector_width_256
-- Performing Test compiler_flag_mprefer_vector_width_256 - Success
-- Performing Test compiler_flag_march_icelake_client
-- Performing Test compiler_flag_march_icelake_client - Success
-- Performing Test compiler_flag_mtune_icelake_client
-- Performing Test compiler_flag_mtune_icelake_client - Success
-- Performing Test compiler_flag_mprefer_vector_width_512
-- Performing Test compiler_flag_mprefer_vector_width_512 - Success
-- Looking for ccache
-- Looking for ccache - found
-- Performing Test compiler_flag_no_address_of_packed_member
-- Performing Test compiler_flag_no_address_of_packed_member - Success
-- Performing Test compiler_flag_no_stringop_overflow
-- Performing Test compiler_flag_no_stringop_overflow - Failed
-- Looking for pthread.h
-- Looking for pthread.h - found
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD - Success
-- Found Threads: TRUE
-- Performing Test HAVE_FCNTL64
-- Performing Test HAVE_FCNTL64 - Success
-- Found OpenSSL: /usr/lib/x86_64-linux-gnu/libcrypto.so (found version 
"3.0.2")

-- The ASM compiler identification is Clang with GNU-like command-line
-- Found assembler: /usr/lib/ccache/clang
-- Looking for libuuid
-- Found uuid in /usr/include
-- Found subunit in /usr/include and 

Re: [vpp-dev] [csit-dev] VPP 23.02 release is complete!

2023-02-23 Thread Dave Wallace
Congratulations to everyone in the FD.io community who continuing the 
excellence in delivering VPP features, fixes, and improvements on a rock 
solid cadence.


A special thanks to Andrew for his effort to automate & execute the 
release process.


-daw-
FD.io TSC Chairperson

On 2/22/23 11:46 AM, Andrew Yourtchenko wrote:

Hi all,

VPP release 23.02 is complete ! Artifacts are at their usual place athttps://packagecloud.io/fdio/release  


Many thanks to all the contributors for their work that went into the release, 
and thanks to Dave Wallace and Vanessa Valderrama for the help in the process !

Onwards to 23.06! :-)

--a /* your friendly 23.02 release manager */




-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#22618): https://lists.fd.io/g/vpp-dev/message/22618
Mute This Topic: https://lists.fd.io/mt/97184849/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [vpp-dev] process node suspended indefinitely

2023-02-20 Thread Dave Barach
Please try something like this, to eliminate the possibility that some bit of 
code is sending this process an event. It’s not a good idea to skip the 
vec_reset_length (event_data) step.

 

while (1)

{

   uword event_type, * event_data = 0;

   int i;

 

   vlib_process_wait_for_event_or_clock (vm, 1e-2 /* 10 ms */);

 

   event_type = vlib_process_get_events (vm, _data);

 

   switch (event_type) {

  case ~0: /* handle timer expirations */

   rtb_event_loop_run_once ();

   break;

 

   default: /* bug! */

   ASSERT (0);

   }

 

   vec_reset_length(event_data);

}

 

From: vpp-dev@lists.fd.io  On Behalf Of Sudhir CR via 
lists.fd.io
Sent: Monday, February 20, 2023 4:02 AM
To: vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] process node suspended indefinitely

 

Hi Dave,
Thank you for your response and help. 

 

Please find the additional details below.

VPP Version 21.10


We are creating a process node rtb-vpp-epoll-process to handle control plane 
events like interface add/delete, route add/delete.
This process node waits for 10ms of time (Not Interested in any events ) once 
10ms is expired it will process control plane events mentioned above.

code snippet looks like below 

 

```

static uword
rtb_vpp_epoll_process (vlib_main_t *vm,
   vlib_node_runtime_t  *rt,
   vlib_frame_t *f)
{

...
...
while (1) {
vlib_process_wait_for_event_or_clock (vm, 10e-3);
vlib_process_get_events (vm, NULL);

rtb_event_loop_run_once();   < controlplane events handling 
}  
}
``` 

What we observed is that sometimes (when there is a high controlplane load like 
request to install more routes) "rtb-vpp-epoll-process" is suspended and not 
scheduled furever. this we found by using "show runtime rtb-vpp-epoll-process"  
(in "show runtime rtb-vpp-epoll-process" command output suspends counter is not 
incrementing.)

show runtime output in working case :


```
DBGvpp# show runtime rtb-vpp-epoll-process
 Name State Calls  Vectors
Suspends Clocks   Vectors/Call  
rtb-vpp-epoll-process   any wait 0   0  
192246  1.91e60.00
DBGvpp# 

DBGvpp# show runtime rtb-vpp-epoll-process
 Name State Calls  Vectors
Suspends Clocks   Vectors/Call  
rtb-vpp-epoll-process   any wait 0   0  
193634  1.89e60.00
DBGvpp# 

``` 

show runtime output in issue case :
```

DBGvpp# show runtime rtb-vpp-epoll-process
 Name State Calls  Vectors
Suspends Clocks   Vectors/Call  
rtb-vpp-epoll-process   any wait 0   0  
 81477  7.08e60.00
DBGvpp# show runtime rtb-vpp-epoll-process
 Name State Calls  Vectors
Suspends Clocks   Vectors/Call  
rtb-vpp-epoll-process   any wait 0   0  
 81477  7.08e60.00

```

Other process nodes like lldp-process, ip4-neighbor-age-process, ip6-ra-process 
running without any issue. only "rtb-vpp-epoll-process" process node suspended 
forever. 

 

Please let me know if any additional information is required.

Hi Jinsh,
Thanks for pointing me to the issue you faced. The issue I am facing looks 
similar.
I will verify with the given patch.


Thanks and Regards,

Sudhir

 

On Sun, Feb 19, 2023 at 6:19 AM jinsh11 mailto:jins...@chinatelecom.cn> > wrote:

HI:



*   I have the same problem,

bfd process node stop running. I raised this issue,

https://lists.fd.io/g/vpp-dev/message/22380
I think there is a problem with the porcess scheduling module when using the 
time wheel.





 

NOTICE TO RECIPIENT This e-mail message and any attachments are confidential 
and may be privileged. If you received this e-mail in error, any review, use, 
dissemination, distribution, or copying of this e-mail is strictly prohibited. 
Please notify us immediately of the error by return e-mail and please delete 
this message from your system. For more information about Rtbrick, please visit 
us at www.rtbrick.com <http://www.rtbrick.com> 


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#22605): https://lists.fd.io/g/vpp-dev/message/22605
Mute This Topic: https://lists.fd.io/mt/97032803/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [vpp-dev] process node suspended indefinitely

2023-02-18 Thread Dave Barach
Process is a bit of a misnomer, “cooperative multitasking thread” would be more 
accurate. Src/vlib/main.c makes no effort to interrupt process nodes. If a 
process runs forever vpp will have a bad day.

 

Recitations: which version of vpp is involved? Please send “show run” output 
for the process node in question.

 

The process might be waiting on an event which never happens, or for the clock 
to reach a time so far in the future it won’t happen in one’s lifetime. Worse 
luck might involve memory corruption or an issue with the timer wheel code.

 

HTH... Dave 

 

From: vpp-dev@lists.fd.io  On Behalf Of Sudhir CR via 
lists.fd.io
Sent: Friday, February 17, 2023 12:12 PM
To: vpp-dev@lists.fd.io
Subject: [vpp-dev] process node suspended indefinitely

 

Hi Team,

We have a process node. which we will use to do some control plane related 
activity. Sometimes we observe that this process node is suspended  
indefinitely.

 

I know that if any process node is taking Unreasonably long time such nodes 
will  not be scheduled further. But not able to figure out in code where this 
is done.

 

Can anyone point me to the code where we are tracking time taken by each 
process node and suspend indefinitely if it is consuming more time.

 

Thanks and regards,

Sudhir

 

NOTICE TO RECIPIENT This e-mail message and any attachments are confidential 
and may be privileged. If you received this e-mail in error, any review, use, 
dissemination, distribution, or copying of this e-mail is strictly prohibited. 
Please notify us immediately of the error by return e-mail and please delete 
this message from your system. For more information about Rtbrick, please visit 
us at www.rtbrick.com <http://www.rtbrick.com> 


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#22601): https://lists.fd.io/g/vpp-dev/message/22601
Mute This Topic: https://lists.fd.io/mt/97032803/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



[vpp-dev] FD.io Projects Retention Policy on Packagecloud.io

2023-02-13 Thread Dave Wallace

Folks,

In light of the recent VPP Security Vulnerability, the FD.io TSC 
discussed and would like to recommend that each project adopt and 
publish a retention policy for packages uploaded to 
https:packagecloud.io/fdio.


The Security Response Team is recommending that any package which was 
built from source that contains a public vulnerability in the form of a 
published CVE record be removed from packagecloud.io/fdio as soon as 
practicable after publication.


Additional factors to consider for a retention policy, is the 
availability of CI infrastructure to generate build artifacts.  CI jobs 
for releases which are no longer supported are removed shortly after the 
release has passed the End-Of-Life date.  In the TSC discussion, it was 
agreed that it made sense to remove the associated release and stable 
branch artifacts at the time the CI infrastructure was removed.  For the 
most part, artifacts uploaded to packagecloud.io are either consumed by 
the CI (e.g. CSIT performance tests), or are made available for 
newcomers to evaluate FD.io software without having to build it from 
scratch. It would be best to encourage all consumers to use supported 
software by retaining only those artifacts in packagecloud.io that are 
based on supported releases.


As it currently stands, packagecloud.io/fdio has artifacts that date 
back to early FD.io VPP releases (circa VPP 17.01).  FD.io projects are 
encouraged to be kind to packagecloud.io who is generously donating 
storage for Open Source project artifacts for free by removing 
antiquated build artifacts.


For VPP artifacts, let's discuss this at tomorrow's VPP Community Meeting.

Thanks,
-daw-

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#22588): https://lists.fd.io/g/vpp-dev/message/22588
Mute This Topic: https://lists.fd.io/mt/96954107/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



[vpp-dev] CVE-2022-46397: FD.io VPP (Vector Packet Processor) IPSec generates a predictable IV with AES-CBC mode

2023-02-13 Thread Dave Wallace

Folks,

A vulnerability in the VPP IPSec plugin was identified by Benoit Ganne 
who has also provided a fix that has been committed to master and 
cherry-picked to all affected VPP Release branches.



Here is the Security Advisory report for CVE-2022-46397 [0]:

Description:
FP.io VPP (Vector Packet Processor) 22.10, 22.06, 22.02, 21.10, 21.06, 
21.01, 20.09, 20.05, 20.01, 19.08, and 19.04 Generates a Predictable IV 
with CBC Mode.


Vulnerability Type Other:
CWE-329: Generation of Predictable IV with CBC Mode

Severity:
Moderate

Vendor of Product:
https://fd.io

Affected Product Code Base:
vpp - v22.10, v22.06, v22.02, v21.10, v21.06, v21.01, v20.09, v20.05, 
v20.01, v19.08, v19.04


Credit:
This issue was reported by Benoit Ganne of Cisco Systems, Inc per the 
FD.io Security Policy [1].


Resolution:
The fix for the vulnerability was committed to the VPP repository's main 
development branch and cherry-picked to all affected release branches on 
2023-02-07. See FD.io VPP Jira ticket VPP-2037 [2] for details.


Maintenance releases were performed on 2023-02-10 for the currently 
supported releases (VPP 22.06, VPP 22.10) and release artifacts for VPP 
22.06.1 and VPP 22.10.1 uploaded to the FD.io packagecloud.io release 
repository [3].  All release branches prior to 2206 are UNSUPPORTED and 
will NOT undergo maintenance releases.  Packages for each VPP release 
version prior to VPP-22.06.1 SHOULD NOT BE INSTALLED from 
https://packagecloud.io/fdio/release, but should be built from the 
latest source code in the release branch.


Reference:
[0] https://www.cve.org/CVERecord?id=CVE-2022-46397
[1] https://wiki.fd.io/view/TSC:Vulnerability_Management
[2] https://jira.fd.io/browse/VPP-2037
[3] https://packagecloud.io/fdio/release


Thanks,
FD.io Security Response Team

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#22587): https://lists.fd.io/g/vpp-dev/message/22587
Mute This Topic: https://lists.fd.io/mt/96953693/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [vpp-dev] Compilation errors seen in VPP v23.02-rc1 on Centos 8

2023-02-13 Thread Dave Wallace

Burcu,

Unfortunately, no one in the community has stepped up to maintain the 
Centos build infrastructure after Red Hat left the community a few years 
back.
VPP 20.09 was the last supported release of CentOS-7 and VPP 21.10 was 
the last supported release of CentOS-8 by the FD.io CI jobs.


The build infra for CentOS was left in place and some folks continue to 
update it for Red Hat variants, so hopefully one of those will fix your 
issue.


Patches are always welcome :)

Thanks,
-daw-

On 2/13/23 7:36 AM, Burcu YUKSEL wrote:

Hello,
We have exactly the same errors when we try to compile VPP v23.02 on 
Centos 7. Is there anyone who can solve this problem?


Regards,
Burcu




-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#22586): https://lists.fd.io/g/vpp-dev/message/22586
Mute This Topic: https://lists.fd.io/mt/96486179/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



[vpp-dev] February LFN Virtual Developer & Testing Forum

2023-02-10 Thread Dave Wallace

Folks,

Please register to join the virtual LFN Developer & Test Forum next week!

Thanks,
-daw-


 Forwarded Message 
Subject:[tsc] February LFN Virtual Developer & Testing Forum
Date:   Fri, 10 Feb 2023 08:12:55 -0800
From:   Casey Cain 
To: 	TAC , ODIM TSC 
, ONAP TSC , Anuket TSC 
, XGVela TSC , 
FD.io TSC , ODL TSC , EMCO 
TSC , TF TSC , 
L3AF TSC , Nephio TSC 




Dear LFN Communities,

We are looking forward to seeing you next week for the LFN Developer & 
Testing Forum *on February 13-16, 2023*. *Please remember to register 
 for 
the event; it's free! *


The schedule 
 is now 
available.  You can find further details about the sessions and speakers 
on the event wiki  page.


Please note: Zoom account authentication will be required for this 
event. If you do not already have a Zoom account, you can obtain a free 
account by going to https://www.zoom.us. We know that authentication may 
present challenges for LFN community members in regions where the use of 
free accounts may be disallowed. If such geographic limitations impact 
you, please send an email to eve...@lfnetworking.org 
 in advance of the event for assistance.


The LFN Developer & Testing Forum will begin at 13:00 UTC each day, I've 
included the current schedule here 
- the 
schedule will be updated in real-time as session details are provided.


Join the LFN Tech Slack 
. 
Slack will be used for side discussions, hallway track, and 
track-related discussions.


Additional information regarding the event can be found on the LFN Wiki 
.


We are excited to see you soon.

Best,
Casey Cain
Senior Technical Community Architect
Linux Foundation
_
WeChat: okaru6
WhatsApp: +1.503.779.4519
Book a Meeting w/ Casey 

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#1736): https://lists.fd.io/g/tsc/message/1736
Mute This Topic: https://lists.fd.io/mt/96879261/675079
Group Owner: tsc+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/tsc/leave/7245241/675079/598713070/xyzzy 
[dwallac...@gmail.com]
-=-=-=-=-=-=-=-=-=-=-=-



-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#22577): https://lists.fd.io/g/vpp-dev/message/22577
Mute This Topic: https://lists.fd.io/mt/96891372/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [vpp-dev] additional email

2023-02-02 Thread Dave Wallace

Hi Stanislav,

Please open a case with LF-IT and let me know what the case number is.

https://jira.linuxfoundation.org/plugins/servlet/theme/portal/2/create/37

I will follow up with LF-IT folks to make sure that it is picked up 
promptly.


Thanks,
-daw-

On 2/2/23 4:22 AM, Stanislav Zaikin wrote:

Hello folks,

I have a stupid question. I want to add an additional email (my 
employer asked me to sign commits with my working email). I've added 
new email at linuxfoundation.org , but 
gerrit keeps showing me the error:


Error 405 (Method Not Allowed): realm does not allow adding emails 
Endpoint: /account/self/emails/*


What can I do about it?

I also tried to push with no luck:
remote: ERROR: commit e1d7fd7: email address 
stanislav.zai...@46labs.com is not registered in your account, and you 
lack 'forge committer' permission.

remote: The following addresses are currently registered:
remote: zsta...@gmail.com

--
Best regards
Stanislav Zaikin




-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#22539): https://lists.fd.io/g/vpp-dev/message/22539
Mute This Topic: https://lists.fd.io/mt/96696880/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [vpp-dev] sigsegv and its handler

2023-02-01 Thread Dave Barach
This seems consistent with a SIGSEGV compounded by a worker-thread stack 
overflow situation. In hopes of obtaining a clean core file, you might want to 
modify the SIGSEGV handler to simply abort() instead of trying to write a 
post-mortem API dump, syslog’ing a backtrace, etc.

 

Best of luck with it.  

 

From: vpp-dev@lists.fd.io  On Behalf Of Stanislav Zaikin
Sent: Wednesday, February 1, 2023 6:17 AM
To: vpp-dev 
Subject: [vpp-dev] sigsegv and its handler

 

Hello folks,

 

I've been experiencing rare crashes (one crash in 3 months or so), it looks 
like the heap is corrupted somehow. Sometimes, the trace shows very unexpected 
nodes (like ip6-map-t although I don't configure any ipv6 map) or sometimes 
it's just a crash inside ip4-rewrite-node.

 

After a look I found that last 2 crashes occured in the same way:

1. vnet_feature_arc_start_w_cfg_index or vnet_feature_arc_start call

2. vnet_get_config_data call

 

But then VPP received and handled a SIGSEGV signal. It completely broke the 
stack trace in the core dump (for the corresponding worker):

#0  0x7f44fa0812c6 in __GI_epoll_pwait (epfd=8, events=0x7f44babe52d8, 
maxevents=, timeout=9, set=0x7f44fa5c66f8 
) at 
../sysdeps/unix/sysv/linux/epoll_pwait.c:42
#1  0x00089f6fab2b in ?? ()
#2  0x7f44babe52d8 in ?? ()
#3  0x00090100 in ?? ()
#4  0x7f44fa5c66f8 in _vlib_init_function_init_linux_epoll_input_init () 
from /lib/x86_64-linux-gnu/libvlib.so.22.10.0
#5  0x in ?? ()

 

So, I can't analyze the core dump. Any ideas on how to catch this crash 
correctly? Disable receiving SIGSEGV? Or is there a way to restore the original 
stack trace of the worker?

 

For the reference, stack traces from syslog:

vnet[2856086]: received signal SIGSEGV, PC 0x7f44b76dbee3, faulting address 
0xb0040114
vnet[2856086]: #0  0x7f44fa43885b 0x7f44fa43885b (unix_signal_handler+379)
vnet[2856086]: #1  0x7f44fa34f3c0 0x7f44fa34f3c0 (__funlockfile)
vnet[2856086]: #2  0x7f44b76dbee3 0x7f44b76dbee3 (ip6_map_t+675)
vnet[2856086]: #3  0x7f44fa3c86fb vlib_worker_loop + 0x1b3b
vnet[2856086]: #4  0x7f44fa41aafa vlib_worker_thread_fn + 0xaa
vnet[2856086]: #5  0x7f44fa414e01 vlib_worker_thread_bootstrap_fn + 0x51
vnet[2856086]: #6  0x7f44fa343609 start_thread + 0xd9
vnet[2856086]: #7  0x7f44fa081163 clone + 0x43

vnet[944491]: received signal SIGSEGV, PC 0x7faf922ca6ae, faulting address 
0x7fb3519530fc
vnet[944491]: #0  0x7faf9102785b 0x7faf9102785b
vnet[944491]: #1  0x7faf90f3e3c0 0x7faf90f3e3c0
vnet[944491]: #2  0x7faf922ca6ae ip4_rewrite_node_fn_skx + 0x149e
vnet[944491]: #3  0x7faf90fb76fb vlib_worker_loop + 0x1b3b
vnet[944491]: #4  0x7faf91009afa vlib_worker_thread_fn + 0xaa
vnet[944491]: #5  0x7faf91003e01 vlib_worker_thread_bootstrap_fn + 0x51
vnet[944491]: #6  0x7faf90f32609 start_thread + 0xd9
vnet[944491]: #7  0x7faf90c70163 clone + 0x43

 

Line information:

Line 135 of "/home/runner/work/vpp/vpp/src/vnet/config.h" starts at address 
0x7f44b76dbee3  and ends at 0x7f44b76dbee7 .

 

Line 135 of "/home/runner/work/vpp/vpp/src/vnet/config.h" starts at address 
0x7f44fb6db6ae  and ends at 0x7f44fb6db6b1 
.

 

-- 

Best regards
Stanislav Zaikin


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#22533): https://lists.fd.io/g/vpp-dev/message/22533
Mute This Topic: https://lists.fd.io/mt/96673497/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [vpp-dev] is VPP Gerrit server "No space left on device"

2023-01-30 Thread Dave Wallace
After gerrit was restarted, git review is working for me: 
https://gerrit.fd.io/r/c/vpp/+/38076 <https://gerrit.fd.io/r/c/vpp/+/38076>


Thanks,
-daw-

On 1/30/23 11:05 AM, Dave Wallace via lists.fd.io wrote:

Folks,

This issue is being actively worked on and is being tracked via the 
following ticket:


https://jira.linuxfoundation.org/plugins/servlet/desk/portal/2/IT-25113

Gerrit is being restarted now.

Thanks,
Dave
ps. Support requests for gerrit issues at 
https://jira.linuxfoundation.org/plugins/servlet/theme/portal/2/create/37


On 1/29/23 9:28 PM, Xu, Ting wrote:


Hi,

+1, Meet the same issue

*From:* vpp-dev@lists.fd.io  *On Behalf Of *Pei, 
Yulong

*Sent:* Monday, January 30, 2023 10:12 AM
*To:* vpp-dev@lists.fd.io
*Subject:* Re: [vpp-dev] is VPP Gerrit server "No space left on device"
*Importance:* High

When open patch link of gerrit, it pops up below message with web 
browser, and can not find patch contents any more,


*From:* vpp-dev@lists.fd.io  *On Behalf Of *Pei, 
Yulong

*Sent:* Saturday, January 28, 2023 10:30 PM
*To:* vpp-dev 
*Subject:* [vpp-dev] is VPP Gerrit server "No space left on device"

Hello vpp-dev,

Failed to run `git review`,  is VPP Gerrit server "No space left on 
device" ?


# git review

error: remote unpack failed: error No space left on device

fatal: Unpack error, check server log

To ssh://gerrit.fd.io:29418/vpp








-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#22521): https://lists.fd.io/g/vpp-dev/message/22521
Mute This Topic: https://lists.fd.io/mt/96587880/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [vpp-dev] is VPP Gerrit server "No space left on device"

2023-01-30 Thread Dave Wallace

Folks,

This issue is being actively worked on and is being tracked via the 
following ticket:


https://jira.linuxfoundation.org/plugins/servlet/desk/portal/2/IT-25113

Gerrit is being restarted now.

Thanks,
Dave
ps. Support requests for gerrit issues at 
https://jira.linuxfoundation.org/plugins/servlet/theme/portal/2/create/37


On 1/29/23 9:28 PM, Xu, Ting wrote:


Hi,

+1, Meet the same issue

*From:* vpp-dev@lists.fd.io  *On Behalf Of *Pei, 
Yulong

*Sent:* Monday, January 30, 2023 10:12 AM
*To:* vpp-dev@lists.fd.io
*Subject:* Re: [vpp-dev] is VPP Gerrit server "No space left on device"
*Importance:* High

When open patch link of gerrit, it pops up below message with web 
browser, and can not find patch contents any more,


*From:* vpp-dev@lists.fd.io  *On Behalf Of *Pei, 
Yulong

*Sent:* Saturday, January 28, 2023 10:30 PM
*To:* vpp-dev 
*Subject:* [vpp-dev] is VPP Gerrit server "No space left on device"

Hello vpp-dev,

Failed to run `git review`,  is VPP Gerrit server "No space left on 
device" ?


# git review

error: remote unpack failed: error No space left on device

fatal: Unpack error, check server log

To ssh://gerrit.fd.io:29418/vpp





-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#22520): https://lists.fd.io/g/vpp-dev/message/22520
Mute This Topic: https://lists.fd.io/mt/96587880/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



[vpp-dev] Topic for VPP Community Meeting (Jan 24) - DPDK Version for VPP 23.06 Release

2023-01-18 Thread Dave Wallace

Folks,

Let's discuss the status of the dpdk version for VPP 23.06 Release (dpdk 
22.11 or dpdk 23.03).


In addition to the resolution of the internal API access, NVidia has 
donated ConnectX-7 NICs to the CSIT performance lab which requires the 
latest dpdk version to enable hardware features of the NIC.


Thanks,
-daw-

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#22479): https://lists.fd.io/g/vpp-dev/message/22479
Mute This Topic: https://lists.fd.io/mt/96356937/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



[vpp-dev] [lfn-TAC] Call for Mentors - 2023 Mentorship Program is live

2023-01-12 Thread Dave Wallace

Folks,

One of the 2023 goals for the FD.io community is to foster growth of 
open source software by mentoring those interested in learning how to 
contribute.


Please consider submitting a mentorship project proposal for your area 
of expertise as described in Casey's email [0].


Thanks,
-daw-  "FD.io TSC Chair"

[0] https://lists.fd.io/g/tsc/message/1732  (use this link to access 
embedded url's)


 Forwarded Message 
Subject:[lfn-TAC] Call for Mentors - 2023 Mentorship Program is live
Date:   Thu, 12 Jan 2023 12:35:58 -0800
From:   Casey Cain 
Reply-To:   lfn-...@lists.lfnetworking.org
To: 	TAC , ODIM TSC 
, onap-tsc , 
anuket-...@lists.anuket.io, XGVela TSC , 
FD.io TSC , TSC , 
emco-...@lists.project-emco.io, TF TSC , L3AF TSC 





Today, we’re excited to open the call for mentors and project proposals 
for the 2023 LF Networking Mentorship Program 
. The 
Program is intended to provide a formal structure to connect mentors and 
student developers from around the globe to contribute their enthusiasm, 
time, and experience toward building sustainable LFN communities.


*Why should you consider mentoring for LF Networking Mentorship Program?*

 * You believe in the value of mentorship in helping new developers to
   navigate open source development, the culture, the tooling, and the
   infrastructure to be productive members of the community.
 * You are passionate about teaching and guiding student developers,
   many of whom may be first time open-source contributors,
 * You are eager to bring new perspectives, ideas, and talent into your
   community and projects.
 * You have a narrowly scoped mentorship project with clear learning
   objectives/outcomes, and a mentee's work and potential contributions
   could add value to the project or community of which you're an
   active developer or maintainer.

*I am interested in mentoring but how do I get started? *

 * Please submit a project proposal
    for consideration by the
   TSC no later than *Friday, March 3rd*.
 * Please reference 2023 program schedule
   as you plan out your project
   and commitment.
 * Please review the project proposal guidelines
    before your submit your
   proposal

*What are the elements the LFN Mentorship Program will implement to 
maximize mentor/mentee collaboration success?*


 * Mentor and mentee onboarding will be conducted at the start of the
   Program
 * Project planning that includes deliverables, milestones, and tasks
   will be completed collaboratively between the mentors and mentees
   during the first two weeks of the program and posted on the wiki to
   increase transparency and accountability.
 * Mentee presentations will be required to sharpen both presentation
   skills and to cultivate the ability to provide constructive feedback
   and critique that’s the norm in the open source community for
   developing technologies collaboratively and openly.
 * Mentee evaluation will be conducted on a regular cadence tied to
   milestone deliverable schedules to help mentors and LFN staff
   formalize and respond to progress.

If you have any questions, please contact mentors...@lfnetworking.org 



We look forward to your submission of a mentorship project and thank you 
in advance for volunteering your time to contribute to training the new 
talent pool in the LF Networking communities.


Best,
Casey Cain
Senior Technical Community Architect
Linux Foundation
_
WeChat: okaru6
WhatsApp: +1.503.779.4519
Book a Meeting w/ Casey 

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#22461): https://lists.fd.io/g/vpp-dev/message/22461
Mute This Topic: https://lists.fd.io/mt/96233648/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [vpp-dev] [csit-dev] Bumping dpdk to 22.11 in vpp 23.02 ?

2023-01-12 Thread Dave Wallace

It is on the VPP meeting wiki page: https://wiki.fd.io/view/VPP/Meeting

Thanks,
-daw-

On 1/12/2023 10:14 AM, Zhang, Fan wrote:


Then I was an hour late :-( Thanks Dave!

Where can I find the new time calendar?

On 1/12/2023 3:12 PM, Dave Wallace wrote:
There was a VPP Community meeting this Tuesday at the new time (5am 
PST) that was lightly attended.





-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#22459): https://lists.fd.io/g/vpp-dev/message/22459
Mute This Topic: https://lists.fd.io/mt/96211041/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [vpp-dev] [csit-dev] Bumping dpdk to 22.11 in vpp 23.02 ?

2023-01-12 Thread Dave Wallace

Hi Fan,

There was a VPP Community meeting this Tuesday at the new time (5am PST) 
that was lightly attended.


Thanks,
-daw-

On 1/12/2023 4:42 AM, Zhang, Fan wrote:

I agree.

It is worth discussing in VPP community call if VPP should access the 
DPDK internal APIs - it surely leaves us more flexibility with the 
price of possible more maintenance effort.


- BTW was there a meeting on this Tuesday? I joined 4 minutes late but 
nobody was there.


Apart from that I believe the patch is in relatively good shape, 
surely lacked testing though.



As of continuous build/sanity between VPP and DPDK main branch - the 
way DPDK function/perf testing the patches now are RC-based, there are 
build tests carried out per-patch based, and there is a crypto unit 
test running nightly with only SW crypto PMDs (@Kai is it still 
running?).


If VPP does the sanity check against DPDK main branch - I personally 
believe VPP may catch some potential DPDK bugs earlier than DPDK 
validation team.


Hence I believe it is a very good idea as a cooperation between two 
projects. This in my opinion also means we need DPDK tech board 
members attending regular meeting with us in case some problems have 
been catched early.



Regards,

Fan

On 1/11/2023 10:29 PM, Andrew Yourtchenko wrote:
My naive impression looking at the change, seems like it’s still work 
in progress with several comments open. Especially with the autumn 
DPDK release IIRC being the “API-breaking” one, looks a bit risky to 
me… I think haste may get us into places we don’t wanna be in. I 
would vote to merge this into master post-RC1 milestone, thus giving 
it more time to soak, and not to put undue strain on anyone.


At the same time I would like to (again?) bring up the idea of doing 
some sort of continuous build/sanity between VPP and DPDK master 
branches -  Fan, I think we discussed this once ? We could then have 
a change ready “just in time” in the future, potentially ? As I am 
not well versed with DPDK - does this idea even make sense ?


--a

On 11 Jan 2023, at 16:53, Maciek Konstantynowicz (mkonstan) via 
lists.fd.io  wrote:


Hi,

On CSIT call just now Kai made us aware of issues with above 
(cryptodev, sat), as captured in this patch:


    37840: dpdk: make impact to VPP for changes in API for DPDK 
22.11 | https://gerrit.fd.io/r/c/vpp/+/37840


23.02 RC1 is next week and in CSIT we start testing at RC1 
milestone, so it’s very last minute …


Also, in the past we got burned by DPDK bump requiring bumping 
firmware versions on FVL and CVL NICs, which for our performance 
testbed fleet is a bit of an operation (e.g. on Arm we have to 
remove the NICs and put them into Xeon machines to do firmware 
upgrade, unless things improved recently).


Asking for views if we could delay dpdk ver bumping to avoid rushing 
it in, especially that there are open issues?


Thoughts?

Cheers,
-Maciek










-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#22457): https://lists.fd.io/g/vpp-dev/message/22457
Mute This Topic: https://lists.fd.io/mt/96211041/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [vpp-dev] Error message on starting vpp

2023-01-11 Thread Dave Wallace

Merged :)

Thanks,
-daw-

On 1/11/23 9:31 AM, Ahmed Abdelsalam (ahabdels) via lists.fd.io wrote:


I just discussed this with Nathan. Should be merged soon. Cheers!

*From: *Pim van Pelt 
*Date: *Wednesday, 11 January 2023 at 13:37
*To: *vpp-dev@lists.fd.io 
*Cc: *jul...@klaiber.me , Pablo Camarillo 
(pcamaril) , Ahmed Abdelsalam (ahabdels) 


*Subject: *Re: [vpp-dev] Error message on starting vpp

Hoi,

Nathan's fix is still pending and starting VPP at HEAD still emits the 
warning:


pim@hippo:~/src/vpp$ make run
WARNING: STARTUP_CONF not defined or file doesn't exist.
         Running with minimal startup config:  unix { interactive 
cli-listen /run/vpp/cli.sock gid 1000 } dpdk { no-pci } \n
vnet_feature_arc_init:272: feature node 'ip6-lookup' not found (before 
'pt', arc 'ip6-output')


I see the other fixes from this thread were merged (thanks!) but what 
about the OP? Would be prudent to address before Jan 18th :)


groet,

Pim

On Mon, Dec 19, 2022 at 9:49 AM Nathan Skrzypczak 
 wrote:


Hi Xiaodong,

It seems like a '.runs_after' was introduced on a node that does
not belong to the arc in question. [0] should solve this.

(CCingJulian as he is the author of the original patch & sr plugin
maintainers)

Cheers

-Nathan

[0] https://gerrit.fd.io/r/c/vpp/+/37837

Le sam. 3 déc. 2022 à 19:29, Xiaodong Xu  a
écrit :

Hi VPP experts,

I got the following error message when starting vpp recently:

0: vnet_feature_arc_init:272: feature node 'ip6-lookup' not
found (before 'pt', arc 'ip6-output')

I'm using master branch from VPP git repo. By checking the
source code, it seems it might have something to do with the
comment

https://github.com/FDio/vpp/commit/b79d09bbfa93f0f752f7249ad27a08eae0863a6b
and

https://github.com/FDio/vpp/commit/39d6deca5f71ee4fe772c10d76ed5b65d1ebec44


So I remove the two commits from my local repo and the issue
is gone.

The message seems to be harmless, but if anyone who is
familiar with the commits can take a look, I'd appreciate it.

Regards,

Xiaodong





--

Pim van Pelt 
PBVP1-RIPE - http://www.ipng.nl/





-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#22447): https://lists.fd.io/g/vpp-dev/message/22447
Mute This Topic: https://lists.fd.io/mt/95432703/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [vpp-dev] Error message on starting vpp

2023-01-10 Thread Dave Wallace

Merged :)

Thanks,
-daw-

On 1/10/2023 4:24 PM, Ahmed Abdelsalam (ahabdels) via lists.fd.io wrote:


Hi Xiaodong,

The warning has been fixed here https://gerrit.fd.io/r/c/vpp/+/37874

Cheers,

Ahmed

*From: *Xiaodong Xu 
*Date: *Thursday, 29 December 2022 at 01:55
*To: *vpp-dev@lists.fd.io 
*Cc: *jul...@klaiber.me , Pablo Camarillo 
(pcamaril) , Ahmed Abdelsalam (ahabdels) 


*Subject: *Re: [vpp-dev] Error message on starting vpp

Hi Nathan,

The issue is gone after your patch is applied. Thanks for the fix. In 
the meantime, there is actually a compile warning which can be fixed 
by the following change:


@@ -124,6 +124,7 @@
   n_left_to_next -= 1;
   timestamp_64_t t64;

+  unix_time_now_nsec_fraction (, );
   b0 = vlib_get_buffer (vm, bi0);
   iface = vnet_buffer (b0)->sw_if_index[VLIB_TX];
   ls = sr_pt_find_iface (iface);
@@ -131,7 +132,6 @@
     {
       en0 = vlib_buffer_get_current (b0);
       ip0 = (void *) (en0 + 1);
-      unix_time_now_nsec_fraction (, );
       pt_midpoint_processing (vm, node, b0, ip0, ls, t64);
       pt_behavior = PT_BEHAVIOR_MID;
     }

Not sure if it makes sense for you to incorporate the change into your 
patch.


Regards,

Xiaodong

On Mon, Dec 19, 2022 at 12:49 AM Nathan Skrzypczak 
 wrote:


Hi Xiaodong,

It seems like a '.runs_after' was introduced on a node that does
not belong to the arc in question. [0] should solve this.

(CCingJulian as he is the author of the original patch & sr plugin
maintainers)

Cheers

-Nathan

[0] https://gerrit.fd.io/r/c/vpp/+/37837

Le sam. 3 déc. 2022 à 19:29, Xiaodong Xu  a
écrit :

Hi VPP experts,

I got the following error message when starting vpp recently:

0: vnet_feature_arc_init:272: feature node 'ip6-lookup' not
found (before 'pt', arc 'ip6-output')

I'm using master branch from VPP git repo. By checking the
source code, it seems it might have something to do with the
comment

https://github.com/FDio/vpp/commit/b79d09bbfa93f0f752f7249ad27a08eae0863a6b
and

https://github.com/FDio/vpp/commit/39d6deca5f71ee4fe772c10d76ed5b65d1ebec44


So I remove the two commits from my local repo and the issue
is gone.

The message seems to be harmless, but if anyone who is
familiar with the commits can take a look, I'd appreciate it.

Regards,

Xiaodong








-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#22441): https://lists.fd.io/g/vpp-dev/message/22441
Mute This Topic: https://lists.fd.io/mt/95432703/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [vpp-dev] Possible VPP deadlock

2023-01-08 Thread Dave Barach
It looks like the root-cause is a corrupted heap. See also 
mspace_free()->check_top_chunk()->do_check_top_chunk(). One of the assertions 
is failing.

 

Once the heap is pickled, all bets are off in terms of getting a useful API 
trace. 

 

Since you have a couple of (possibly) useful post-mortem dumps, the first step 
would be to figure out why printing the api traces causes a NULL pointer 
dereference.

 

It should be comparatively simple to work out the NULL pointer dereference in 
the api trace printer. You can binary search for the offending message, walk 
through vl_msg_print_trace(...) and figure out what’s going on. It’s likely 
that the message in question simply doesn’t have a print function. See 
src/vlibmemory/vlib_api_cli.c:api_trace_command_fn() for details. In 
particular, “first” and “last” describe which messages should be printed (or 
replayed).

 

HTH... Dave

 

From: vpp-dev@lists.fd.io  On Behalf Of Pim van Pelt via 
lists.fd.io
Sent: Sunday, January 8, 2023 1:24 PM
To: vpp-dev 
Subject: [vpp-dev] Possible VPP deadlock

 

Hoi,

 

I've had a few instances of a recent VPP hanging - API and CLI go unresponsive, 
forwarding stops (at least, I think), but the worker threads are still 
consuming CPU.

Attaching GDB, I see the main thread is doing the following:

(gdb) bt

#0  0x7f5f6f8f271b in sched_yield () at 
../sysdeps/unix/syscall-template.S:78

#1  0x7f5f6fb3df8b in spin_acquire_lock (sl=) at 
/home/pim/src/vpp/src/vppinfra/dlmalloc.c:468

#2  mspace_malloc (msp=0x130048040, bytes=72) at 
/home/pim/src/vpp/src/vppinfra/dlmalloc.c:4351

#3  0x7f5f6fb66f81 in mspace_memalign (msp=0x130048040, 
alignment=, bytes=72) at 
/home/pim/src/vpp/src/vppinfra/dlmalloc.c:4667

#4  clib_mem_heap_alloc_inline (heap=, size=72, align=, os_out_of_memory_on_failure=1) at 
/home/pim/src/vpp/src/vppinfra/mem_dlmalloc.c:608

#5  clib_mem_heap_alloc_aligned (heap=, size=72, align=8) at 
/home/pim/src/vpp/src/vppinfra/mem_dlmalloc.c:664

#6  0x7f5f6fba5157 in _vec_alloc_internal (n_elts=64, attr=) 
at /home/pim/src/vpp/src/vppinfra/vec.c:35

#7  0x7f5f6fb848c8 in _vec_resize (vp=, n_add=64, hdr_sz=0, 
align=8, elt_sz=) at /home/pim/src/vpp/src/vppinfra/vec.h:256

#8  serialize_vector_write (m=, s=0x7f5f0dbfebc0) at 
/home/pim/src/vpp/src/vppinfra/serialize.c:908

#9  0x7f5f6fb843c1 in serialize_write_not_inline (m=0x7f5f0dbfeb60, 
s=, n_bytes_to_write=4, flags=) at 
/home/pim/src/vpp/src/vppinfra/serialize.c:734

#10 0x7f5f6fe5a053 in serialize_stream_read_write (header=0x7f5f0dbfeb60, 
s=, n_bytes=4, flags=2) at 
/home/pim/src/vpp/src/vppinfra/serialize.h:140

#11 serialize_get (m=0x7f5f0dbfeb60, n_bytes=4) at 
/home/pim/src/vpp/src/vppinfra/serialize.h:180

#12 serialize_integer (m=0x7f5f0dbfeb60, x=, n_bytes=4) at 
/home/pim/src/vpp/src/vppinfra/serialize.h:187

#13 vl_api_serialize_message_table (am=0x7f5f6fe66258 , 
vector=) at /home/pim/src/vpp/src/vlibapi/api_shared.c:210

#14 0x7f5f6fe5a715 in vl_msg_api_trace_save (am=0x130048040, 
which=, fp=0x13f0690, is_json=27 '\033') at 
/home/pim/src/vpp/src/vlibapi/api_shared.c:410

#15 0x7f5f6fe5c0ea in vl_msg_api_post_mortem_dump () at 
/home/pim/src/vpp/src/vlibapi/api_shared.c:880

#16 0x004068c6 in os_panic () at 
/home/pim/src/vpp/src/vpp/vnet/main.c:415

#17 0x7f5f6fb3feed in mspace_free (msp=0x130048040, mem=) at 
/home/pim/src/vpp/src/vppinfra/dlmalloc.c:2954

#18 0x7f5f6fb6bf8c in clib_mem_heap_free (heap=0x0, p=) at 
/home/pim/src/vpp/src/vppinfra/mem_dlmalloc.c:768

#19 clib_mem_free (p=) at 
/home/pim/src/vpp/src/vppinfra/mem_dlmalloc.c:774

#20 0x7f5f2fa32b40 in ?? ()

#21 0x7f5f3302f848 in ?? ()

#22 0x in ?? ()

 

When I kill VPP, sometimes an api_post_mortem is emitted (although most of the 
time they are empty), but subsequently trying to dump it, makes VPP crash -

 

-rw--- 1 ipng ipng 35437 Jan  8 19:08 api_post_mortem.76724

-rw--- 1 ipng ipng 35368 Jan  8 19:08 api_post_mortem.76842

-rw--- 1 ipng ipng 0 Jan  8 19:08 api_post_mortem.76978

-rw--- 1 ipng ipng 0 Jan  8 19:08 api_post_mortem.84008

 

#0  0x in ?? ()

#1  0x77fada5f in vl_msg_print_trace (msg=0x7fff9db73bd8 "", 
ctx=0x7fff53b62ca0) at /home/pim/src/vpp/src/vlibmemory/vlib_api_cli.c:693

#2  0x766a55bb in vl_msg_traverse_trace (tp=0x7fff9b4e7998, 
fn=0x77fad790 , ctx=0x7fff53b62ca0)

at /home/pim/src/vpp/src/vlibapi/api_shared.c:321

#3  0x77fab854 in api_trace_command_fn (vm=0x7fff96000700, 
input=0x7fff53b62f30, cmd=)

at /home/pim/src/vpp/src/vlibmemory/vlib_api_cli.c:727

#4  0x7647fdad in vlib_cli_dispatch_sub_commands (vm=0x7fff96000700, 
cm=, input=0x7fff53b62f30, 

parent_command_index=) at 
/home/pim/src/vpp/src/vlib/cli.c:650

#5  0x7647fb91 in vlib_cli_dispatch_sub_commands (vm=0x7fff96000700, 
cm=, input=0x7fff53b62f30, 

parent_command_index=) at 
/home/pim/src/vp

Re: [vpp-dev] Outdated home gateway script for NAT?

2022-12-25 Thread Dave Barach
The “service restart isc-dhcp-server” command is a hack which only knows how to 
restart the isc-dhcp-server, not dnsmasq. 

 

You’ll need to tinker with it to restart dnsmasq, which almost certainly needs 
to deal with the lstack interface.

 

HTH... Dave

 

From: vpp-dev@lists.fd.io  On Behalf Of pepijn de vos
Sent: Sunday, December 25, 2022 12:49 PM
To: vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] Outdated home gateway script for NAT?

 

Hi Dave,

Works!
I modified the .gate file to define TRUNKHW (the actual hardware interface) and 
VLAN and updated TRUNK to be the subinterface.
Then I added a few lines to create the subinterface, and the rest of the script 
now automatically referred to the subinterface.
So at least the tap interface, wan dhcp client, and the nat44 setup work with 
the subinterface.
I'm not using any of the other goodies for now, since I want to keep it simple 
and understandable.
I'm using dnsmasq for the DHCP and DNS server, I could add my config to the 
docs if that would be useful.

Oh reminds me, I also got an input error from the service restart command that 
supposedly restarts the DHCP server.
Not sure why that's there, and if you should be able to execute arbitrary shell 
commands, or there is some service plugin I did not load.
I did find that dnsmasq doesn't like it if you tell it to only bind to lstack 
before vpp has started for obvious reasons, but the default behavior of binding 
to all interfaces and rejecting the ones that are not selected works like a 
treat.
(this seems fine since the kernel doesn't know about the WAN interface anyway)

Regards,
Pepijn 


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#22387): https://lists.fd.io/g/vpp-dev/message/22387
Mute This Topic: https://lists.fd.io/mt/95859254/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [vpp-dev] Outdated home gateway script for NAT?

2022-12-25 Thread Dave Barach
I think that you just need to create an L3 vlan subinterface:

 

vpp# create sub-interface  300

 

At that point, .300 should be an L3 subinterface which will 
strip vlan tag 300 for RX packets, and add vlan tag 300 for TX packets. Strikes 
me that that’s exactly what you need. 

 

if =GigabitEthernet3/0/0, setting TRUNK_PORT to 
GigabitEthernet3/0/0.300 and inhaling the rest of the configuration MAY just 
work. I’ve never tested the various NAT flavors, the DNS resolver, etc. to see 
if the code truly works with vlan subinterfaces.

 

Let me know what happens. I’ve never constructed a suitable test topology for 
this use case, so it may take some doing to fix issues.  

 

HTH... Dave

 

 

From: vpp-dev@lists.fd.io  On Behalf Of pepijn de vos
Sent: Sunday, December 25, 2022 11:30 AM
To: vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] Outdated home gateway script for NAT?

 

Hi Dave,

Thanks a lot of the update, I have managed to get it to work now, at least as a 
secondary router behind my ISP router.
My ISP wants the WAN port to use VLAN 300, and I can't figure out how to do 
that.

I've tried to push the vlan tag on the outward port 

set int l2 tag-rewrite $(TRUNK) push dot1q 300

and I tried creating a subinterface and binding nat44 to that 

create sub-interfaces $(TRUNK) 300 default

set int state $(TRUNK).300 up
set interface nat44 in bvi0 out $(TRUNK).300

and tried the reverse on the bvi0 interface.
I might be missing the correct commands by a millimeter or a kilometer, but I'm 
not getting an IP on the WAN.

TBH I did not copy most of the new additions because I had to google what some 
of them even stand for.
Maybe once I got this all set up I should make a PR to add some comments and 
instructions for beginners like me on what some of these commands do and what 
they are for.

Cheers,
Pepijn 


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#22385): https://lists.fd.io/g/vpp-dev/message/22385
Mute This Topic: https://lists.fd.io/mt/95859254/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [vpp-dev] Outdated home gateway script for NAT?

2022-12-25 Thread Dave Barach
I've updated the doc, please see https://gerrit.fd.io/r/c/vpp/+/37859

HTH... Dave

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#22383): https://lists.fd.io/g/vpp-dev/message/22383
Mute This Topic: https://lists.fd.io/mt/95859254/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [vpp-dev] Outdated home gateway script for NAT?

2022-12-24 Thread Dave Barach
Thanks for the report. I’ll update the doc…

> On Dec 24, 2022, at 3:45 AM, pepijn de vos  wrote:
> 
> 
> Hello,
> 
> I'm quite new to VPP and trying to follow the "VPP as a Home Gateway" setup.
> After following the installation instructions and copying the configuration 
> files, NAT does not seem to be working.
> When I enabled NAT44 it gave an outright error: nat44: unknown input `enable 
> users 50 user-sessions ...'
> I then tried to change that to "nat44 plugin enable" as an educated guess, 
> and also tried to enable CNAT instead as the example does.
> 
> In both cases the result is the same:
> The WAN port gets an IP, the LAN port hands out IPs, and I can ping 
> 192.168.5.2 from the LAN port.
> But I can not ping 192.168.5.1 or the rest of the internet from either the 
> router itself or the LAN port.
> What I CAN do is enable the ping plugin and ping 8.8.8.8 from vppctl.
> So it seems to me like the LAN and WAN sides are both working as intended, 
> but NAT isn't working.
> 
> I'm not really sure how to go ahead debugging this issue.
> Also apologies if this is too much of a "user" question for a "dev" mailing 
> list, but I did not find anything else, and it seems like the docs are at 
> least somewhat wrong/outdated.
> 
> Regards,
> Pepijn
> 
> 
> 


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#22382): https://lists.fd.io/g/vpp-dev/message/22382
Mute This Topic: https://lists.fd.io/mt/95859254/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



[vpp-dev] VPP AF_PACKET (aka host-interface) driver is now a plugin

2022-12-21 Thread Dave Wallace

Folks,

As part of the ongoing effort to move features from vpp/src/vnet to 
plugins (tracked Jira VPP-2040 [0]), the gerrit change [1] moving the 
VPP AF_PACKET (aka host-interface) driver to a plugin has just been 
merged into master.


If you use the VPP AF_PACKET driverand have the stanza 'plugin default 
{disable}' in your startup.conf (if not, you probably should consider 
it) then you'll have to add 'plugin af_packet_plugin.so {enable}' to the 
plugins stanza in your startup.conf for the AF_PACKET plugin to be 
loaded from now on.


Thanks,
-daw-

[0] https://jira.fd.io/browse/VPP-2040
[1] https://gerrit.fd.io/r/c/vpp/+/37830

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#22355): https://lists.fd.io/g/vpp-dev/message/22355
Mute This Topic: https://lists.fd.io/mt/95813067/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



[vpp-dev] VPP & HICN docs verify jobs now upload generated docs to a 7-day retention S3 bucket

2022-12-12 Thread Dave Wallace

Folks,

The VPP and HICN docs verify jobs now upload the generated docs for each 
patch to a 7-day retention bucket in Amazon S3 storage. The upload URL 
for the docs is the same as the log URL for the docs job except that the 
domain name is 's3-docs-7day.fd.io' instead of 's3-logs.fd.io'.


For example, the following VPP docs job:

https://s3-logs.fd.io/vex-yul-rot-jenkins-1/vpp-docs-verify-master-ubuntu2204-x86_64/742/

uploaded the VPP documentation generated for the associated patch to:

https://s3-docs-7day.fd.io/vex-yul-rot-jenkins-1/vpp-docs-verify-master-ubuntu2204-x86_64/742/


Similarly, the HICN docs job:

https://s3-logs.fd.io/vex-yul-rot-jenkins-1/hicn-docs-verify-master-ubuntu2004-x86_64/433/

uploaded the HICN documentation generated for the associated patch to:

https://s3-docs-7day.fd.io/vex-yul-rot-jenkins-1/hicn-docs-verify-master-ubuntu2004-x86_64/433/


If you attempt to access a URL for a docs verify job that is more than 7 
days old, then you will get a 404 error:


https://s3-docs-7day.fd.io/vex-yul-rot-jenkins-1/vpp-docs-verify-master-ubuntu2204-x86_64/658

 %< 
404 Not Found

    Code: NoSuchKey
    Message: The specified key does not exist.
    Key: vex-yul-rot-jenkins-1/vpp-docs-verify-master-ubuntu2204-x86_64/658
    RequestId: VZSP8G8QK91WF3AB
    HostId: 
X6+NkeAuRXpVGgDCq27Yqg7vbg6VdlyqS1utS+nPrJjCjIjDdQ+p6INLPuPfjHdMIWUW40ANht4=


An Error Occurred While Attempting to Retrieve a Custom Error Document

    Code: NoSuchKey
    Message: The specified key does not exist.
    Key: error.html
 %< 

Thanks,
-daw-

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#22321): https://lists.fd.io/g/vpp-dev/message/22321
Mute This Topic: https://lists.fd.io/mt/95627241/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [vpp-dev] [csit-dev] Core isolation on kernel command line deprecated

2022-12-12 Thread Dave Wallace

Hi Juraj,

+ vpp-dev@lists.fd.io

For those curious to learn more, here is the cpusets kernel 
documentation [0] and cpuset manpage [1].


Thanks for the heads up!
-daw-

[0] 
https://www.kernel.org/doc/Documentation/admin-guide/cgroup-v1/cpusets.rst

[1] https://manpages.ubuntu.com/manpages/jammy/man7/cpuset.7.html

On 12/5/2022 5:44 AM, Juraj Linkeš wrote:


Hello CSIT devs,

While looking for possible causes for the 3n-tsh VM testcase timeouts, 
Tianyu from arm found out that the isolcpus kernel command line 
parameter has been deprecated. It seems that no cores are actually 
being isolated:


# altra SUT

jlinkes@jlinkes:~/workspace$ alt1-perf cat /proc/self/status | grep 
Cpus_allowed_list


Cpus_allowed_list:  0-159

# icelake SUT

jlinkes@jlinkes:~/workspace$ ssh testuser@10.30.51.75 cat 
/proc/self/status | grep Cpus_allowed_list


Cpus_allowed_list:  0-127

# snowridge SUT

jlinkes@jlinkes:~/workspace$ ssh testuser@10.30.51.93 cat 
/proc/self/status | grep Cpus_allowed_list


Cpus_allowed_list:  0-23

# cascadelake SUT

jlinkes@jlinkes:~/workspace$ ssh testuser@10.32.8.18 cat 
/proc/self/status | grep Cpus_allowed_list


Cpus_allowed_list:  0-95

The kernel docs [0] themselves mention that the parameter has been 
deprecated and we should use cpusets instead.


Looks like the deprecation could have broader implications in CSIT.

Regards,

Juraj

[0] 
https://www.kernel.org/doc/Documentation/admin-guide/kernel-parameters.txt






-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#22320): https://lists.fd.io/g/vpp-dev/message/22320
Mute This Topic: https://lists.fd.io/mt/95625755/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [vpp-dev] PSA: host stack active opens from first worker

2022-12-02 Thread Dave Wallace

Florin,

Most Excellent -- very nice work on improving the VPP Hoststack! :D

Thanks,
-daw-

On 12/1/22 18:17, Florin Coras wrote:

Hi folks,

It’s been many months and patches at this point but once [1] is 
merged, session layer will accept connects from both main, with worker 
barrier, and first worker. Preference is now for the latter, 
especially if CPS performance is critical.


There should be no need to change existing apps. In particular, vcl 
applications will transparently leverage this improvement while 
builtin applications should still work even if they rely on main 
thread for the connects.


The reason why this is a PSA is because in spite of all testing, 
there’s still a chance some corner case are not supported, some 
transports might be buggy now or just plain old bugs might’ve slipped 
in. Should you hit any issues, or have any additional comments, feel 
free to reach out via this thread or directly.


Benefits of this improvement are:
- no more main thread polling under heavy connect load. Under certain 
circumstances, main can still be used to perform the connects but this 
should be the exception not the norm.

- higher CPS performance.

And to be precise, regarding the CPS performance, on my skylake 
testbed using 40Gbps nics:
o) prior to [2], albeit note that several other changes that might’ve 
affected performance have already gone in:

- 1 worker vpp, pre-warmup: 80k post warmup: 105k
- 4 worker vpp, pre-warmup: 135k post-warmup: 230k
o) after change:
- 1 worker vpp, pre-warmup: 110k, post warmup: 165k
- 4 worker vpp, pre-warmup: 150k, post warmup: 360k

You can try to reproduce these results using this [2].

Regards,
Florin

[1] https://gerrit.fd.io/r/c/vpp/+/35713/
[2] 
https://wiki.fd.io/view/VPP/HostStack/EchoClientServer#TCP_CPS_measurement








-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#22271): https://lists.fd.io/g/vpp-dev/message/22271
Mute This Topic: https://lists.fd.io/mt/95395667/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



[vpp-dev] vpp-gerrit-report with auto-abandonment

2022-11-23 Thread Dave Wallace

Folks,

As discussed at this week's VPP Community Meeting, I have completed 
development of gerrit change auto-abandonment and incorporated the 
reporting of auto-abandoned gerrit changes in the daily 
vpp-gerrit-report [0] generation scripts.


The gerrit instance is being stressed with the large number of open 
changes and leaving hundreds of open gerrit changes reduces the 
signal-to-noise ration for reviewers. Abandoned changes are not deleted 
from gerrit, so they can always be restored.  If you want them to remain 
visible, then restore the change and mark them either as 
work-in-progress (publicly visible) or private (visible to reviewers + 
author). This will remove them from regular CI processing that gerrit 
does and help improve gerrit performance.


Alternatively, gerrit changes that are to be merged can simply be 
rebased (which they should be prior to merging to ensure testing with 
the latest codebase prior to merge).


I have also written a shellscript to search the repo for gerrit changes 
that were auto-abandoned by the daily scripts to make it easy to find 
and restore auto-abandoned changes.  Here's how to use it:


1. git clone https://github.com/vpp-dev/vpp-gerrit-report && cd 
vpp-gerrit-report

2. ./scripts/find_abandoned_changes.sh 

Here is a sample output of the shellscript:

/scratch/dwallacelf/github.com/vpp-dev/vpp-gerrit-report$ 
./scripts/find_abandoned_changes.sh dwallac...@gmail.com


**Dave Wallace** :

Found in 
https://github.com/vpp-dev/vpp-gerrit-report/blob/6d844808a029747406e2e2ca39b3c6d62e56e09a/VPP-GERRIT-REPORT.rst
  | `33727 <https:gerrit.fd.io/r/c/vpp/+/33727>`_ [A 0]: tests: 
relicense
  | `33707 <https:gerrit.fd.io/r/c/vpp/+/33707>`_ [A 0]: papi: 
relicense


Found in 
https://github.com/vpp-dev/vpp-gerrit-report/blob/33cdcd6ef678873c9b5feacb81296ac6243dc352/VPP-GERRIT-REPORT.rst
  | `37088 <https:gerrit.fd.io/r/c/vpp/+/37088>`_ [A 0]: misc: 
patch to test CI infra changes


Found in 
https://github.com/vpp-dev/vpp-gerrit-report/blob/4f1f0aeed38480d39c188a2dc0d338de356a9818/VPP-GERRIT-REPORT.rst
  | `37088 <https:gerrit.fd.io/r/c/vpp/+/37088>`_ [A 0]: misc: 
patch to test CI infra changes


Found in 
https://github.com/vpp-dev/vpp-gerrit-report/blob/88e5d41324dec032db40eba4639573f2f6d37cca/VPP-GERRIT-REPORT.rst
  | `37088 <https:gerrit.fd.io/r/c/vpp/+/37088>`_ [A 0]: misc: 
patch to test CI infra changes



Thanks,
-daw-

[0] https://github.com/vpp-dev/vpp-gerrit-report

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#22235): https://lists.fd.io/g/vpp-dev/message/22235
Mute This Topic: https://lists.fd.io/mt/95224721/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [vpp-dev] RFC: move the “1”st instance of the community meeting 3 hours earlier to reduce impact for earlier time zone

2022-11-22 Thread Dave Wallace

+1

On 11/22/22 11:28 AM, Andrew Yourtchenko wrote:

Hi all,

It came up that the current time of the community meeting is extremely 
unfriendly for our community members on China timezone - it makes it midnight 
their time.

So, as per discussion on the call today, I would like to propose to move every 
other of the meetings (the one in the second Tuesday of the month) three hours 
earlier.

I would also suggest that this proposal take effect starting with the upcoming 
meeting on December 13th.

Thoughts ?

--a




-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#2): https://lists.fd.io/g/vpp-dev/message/2
Mute This Topic: https://lists.fd.io/mt/9526/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [vpp-dev] Gerrit Review Id 37642

2022-11-12 Thread Dave Wallace

Merged.

Thanks for your contribution.
-daw-

On 11/11/2022 1:51 AM, lihuawei wrote:

Hi community maintainers,
I have added a fix as gerrit review id 37642.

*gerrit link: https://gerrit.fd.io/r/c/vpp/+/37642*

*short description: *fix lib install dir and add vat2 lib install when 
build rpm.


Please have a look and review.

Best regards,
Huawei LI




-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#22174): https://lists.fd.io/g/vpp-dev/message/22174
Mute This Topic: https://lists.fd.io/mt/94953939/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



[vpp-dev] Volunteers to join the FD.io Security Response Team

2022-11-10 Thread Dave Wallace

Folks,

The TSC is looking for volunteers from the community to join the 
Security Response Team [0].


If you have any experience with open source Vulnerability Reporting 
Processes and would like to help the FD.io community by joining the 
Security Response Team, then please respond to me directly via email.


Thanks,
-daw-, TSC Chairperson

[0] https://wiki.fd.io/view/Security

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#22160): https://lists.fd.io/g/vpp-dev/message/22160
Mute This Topic: https://lists.fd.io/mt/94938558/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [vpp-dev] Bug report - IP6 ND RA default route disappear from host device

2022-11-06 Thread Dave Barach
Merged... This patch addresses similar issues with iOS devices which appear to 
pay attention to the router flag...

 

Thanks... Dave  

 

From: vpp-dev@lists.fd.io  On Behalf Of Petr Boltík
Sent: Sunday, November 6, 2022 4:09 AM
To: vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] Bug report - IP6 ND RA default route disappear from host 
device

 

Hi Matt,

 

Thank you. I can confirm that your fix works. Now I can continue to deploy ipv6 
using kea dhcpv6 (without static configuration).

 

Best regards

Petr B.

 

ne 6. 11. 2022 v 0:13 odesílatel Petr Boltík via lists.fd.io 
<http://lists.fd.io>  mailto:gmail@lists.fd.io> > napsal:

Hi Matt,

 

Than you so much. I will test it as soon as possible.

 

Petr

 

Dne so 5. 11. 2022 21:44 uživatel Matthew Smith via lists.fd.io 
<http://lists.fd.io>  mailto:netgate@lists.fd.io> > napsal:

Hi Petr,

 

You didn't miss any configuration. I don't see any place where the router flag 
is set on an NA in current VPP master branch code.

 

Can you test with https://gerrit.fd.io/r/c/vpp/+/37582 applied and see if it 
addresses the issue?

 

-Matt

 

 

 

 

On Fri, Nov 4, 2022 at 1:49 PM Petr Boltík mailto:petr.bol...@gmail.com> > wrote:

Hi,

 

Thanks for your reply. 

 

I did a packet capture using Wireshark to compare RA from the 
VPP/MikroTik/Radvd. There is no problem with routing advertisements from VPP, 
but with Neighbor Advertisement when RA is enabled. ICMP v6 flag is not set 
correctly - The Router flag is NOT set on the VPP side. Debian 11 ignores this, 
Windows and a few others remove the default gateway after receiving this 
neighbor advertisement. Wireshark .pcapng in the link.

 

I use the Kea6 dhcp6 server for prefix delegation + VPP for RA (not using radvd 
- only for testing). Many users want to use VPP as a home gateway and IPv6 RA 
not working correctly with various end-user devices (like windows for this 
testing scenario).

 

VPP RA+ND - line 914

MikroTik RA+ND - line 819

 

https://easyupload.io/m/xwvqjj

 

If I missed something in the configuration of VPP, please let me know. I did 
not find any relevant CLI 

 

Best regards

Petr

 

 

pá 4. 11. 2022 v 13:25 odesílatel Benoit Ganne (bganne) via lists.fd.io 
<http://lists.fd.io>  mailto:cisco@lists.fd.io> > napsal:

Hi Petr,

Unfortunately I can't confirm the issue, but I do not think it is a very 
commonly tested scenario so it is not really surprising...
What could help understand the issue would be if you could capture the RA 
traffic in both scenarios (VPP vs radvd) so we can compare.

Best
ben

> -Original Message-
> From: vpp-dev@lists.fd.io <mailto:vpp-dev@lists.fd.io>   <mailto:vpp-dev@lists.fd.io> > On Behalf Of Petr Boltík
> Sent: Friday, November 4, 2022 12:50
> To: vpp-dev mailto:vpp-dev@lists.fd.io> >
> Subject: Re: [vpp-dev] Bug report - IP6 ND RA default route disappear from
> host device
> 
> Hi all,
> 
> Can someone please confirm this VPP IP6 RA issue? Any idea is welcome. I
> already tested the latest VPP build v23.02-rc0~96-ge69d97438~b598 with no
> success. Installed default IP6 GW on Windows7/10/UBNTairOS disappeared
> after a short time. Thanks
> 
> Best regards
> Petr B.
> 
> pá 28. 10. 2022 v 18:37 odesílatel Petr Boltík  <mailto:petr.bol...@gmail.com> 
> <mailto:petr.bol...@gmail.com <mailto:petr.bol...@gmail.com> > > napsal:
> 
> 
>   Hi all,
> 
>   I have discovered the problem with IP6 ND RA receiving side - it
> can be observed on Windows 10/7/UBNT airos8 and some others. Issue not
> observed on the Debian 11+nmcli. Configuration is pretty straightforward.
> Tested with VPP 22.06, 22.10. Issue persists. VPP configuration is the
> default, tested on APU4D4 and a few others. No linuxcp/nl is used.
> 
>   1. configure VPP:
> 
>   set interface ip address GigabitEthernet3/0/0 2a01:500::1/64
>   set interface state GigabitEthernet3/0/0 up
>   create loopback interface
>   set interface state loop0 up
>   set interface ip address loop0 2a01:400::1/64
>   ip6 nd GigabitEthernet3/0/0 prefix 2a01:500::/64 default
>   ip6 nd GigabitEthernet3/0/0 no ra-suppress
> 
> 
> 
>   vpp# show version
> 
>   vpp v22.10-release built by root on 89a4591888eb at 2022-10-
> 26T14:00:30
> 
> 
>   2. connect host Windows7/10/ubnt to the GigabitEthernet3/0/0 and
> you can observe weird behavior
>   - RA from VPP is received, IP6 address is installed. Icmp echo to
> the VPP link local address and configured 2a01:500::1 works.
>   - RA from VPP is received, IP6 default route is installed and
> works. Icmp echo to the 2a01:400::1 works.
> 
> 
>   Issue:  After stopping all icmp e

Re: [vpp-dev] VPP Gerrit Report Enhancement

2022-11-05 Thread Dave Wallace

Hi Andrew,

Hmmm, the fix was to get_changes.py to not download changes with -2 
(before classification / report generation), so it would appear to be a 
bug in the gerrit api.  What change was it?


It worked for two of my changes which are set to -2 (33707 & 33727).

BTW, if you prefer to retain -2 changes in author's section, then I will 
need to refactor my fix to elide the -2 changes during report generation.


Thanks,
-daw-

On 11/5/2022 5:34 AM, Andrew Yourtchenko wrote:

Hi Dave,

Very cool! I assume this change reflects only for the changes showing 
in component maintainers’ lists, and not the authors ? (I saw one -2 
change in my list in this report, which is the “correct” behavior imo, 
so just making sure it is a feature and not a bug :)


--a


On 4 Nov 2022, at 16:13, Dave Wallace  wrote:

 Folks,

I have enhanced the VPP Gerrit Report to not include gerrit changes 
which are marked 'Code-review -2'.  Today's report [0] reflects that 
improvement.


Please let me know if you have any feedback on this report.

Thanks,
-daw-

[0] https://github.com/vpp-dev/vpp-gerrit-report








-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#22135): https://lists.fd.io/g/vpp-dev/message/22135
Mute This Topic: https://lists.fd.io/mt/94807675/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [vpp-dev] maintainer's email

2022-11-04 Thread Dave Barach
I cleaned up my Linux Foundation profile. Hopefully the problem won't recur. 
Thanks for the report... Dave Barach

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#22129): https://lists.fd.io/g/vpp-dev/message/22129
Mute This Topic: https://lists.fd.io/mt/94811012/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



[vpp-dev] VPP Gerrit Report Enhancement

2022-11-04 Thread Dave Wallace

Folks,

I have enhanced the VPP Gerrit Report to not include gerrit changes 
which are marked 'Code-review -2'.  Today's report [0] reflects that 
improvement.


Please let me know if you have any feedback on this report.

Thanks,
-daw-

[0] https://github.com/vpp-dev/vpp-gerrit-report

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#22124): https://lists.fd.io/g/vpp-dev/message/22124
Mute This Topic: https://lists.fd.io/mt/94807675/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



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

2022-10-26 Thread Dave Wallace

Most Excellent!

Congratulations to the VPP Community for another high quality, on time, 
release.


Thanks to Andrew for his work driving the release process to a 
successful conclusion.

-daw-

On 10/26/22 14:04, Andrew Yourtchenko wrote:

Hi all,

VPP release 22.10 is complete !

You can have a look at the release notes at
https://docs.fd.io/vpp/22.10/aboutvpp/releasenotes/v22.10.html

The artifacts are available at the https://packagecloud.io/fdio/release

Thanks to Dave Wallace and Vanessa Valderrama for the assistance in 
preparing the release, and to all of the VPP contributors for their 
valuable work!


--a /* your friendly 22.10 release manager */






-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#22078): https://lists.fd.io/g/vpp-dev/message/22078
Mute This Topic: https://lists.fd.io/mt/94587728/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



[vpp-dev] FD.io VPP (master branch) Gerrit Change Report is now being generated daily

2022-10-24 Thread Dave Wallace

Folks,

I have completed automating the generation of the VPP Gerrit Change 
Report which will now be updated daily.


The source code and latest report can be found in the repo:
https://github.com/vpp-dev/vpp-gerrit-report

The daily report can be found in the file, VPP-GERRIT-REPORT.rst and its 
contents are also included in the README.rst as a convenience.


Please let me know if this report is useful and any suggestions to make 
it more better.


Thanks,
-daw-

[0] : 
https://github.com/vpp-dev/vpp-gerrit-report/blob/main/VPP-GERRIT-REPORT.rst


On 10/12/22 10:57, Dave Wallace via lists.fd.io wrote:
New report generated today 
https://gist.github.com/dwallacelf/90f2c3b1a2a59b5bc186d89650826f6b


Please review the report and update/review/merge changes as appropriate.

Thanks,
-daw-

On 9/27/22 10:09 AM, Dave Wallace via lists.fd.io wrote:
New report generated today: 
https://gist.github.com/dwallacelf/4147e4d26ca154698ea3c881426160c3


Please review the report and update/review/merge changes as appropriate.

Thanks,
-daw-


On 9/14/22 3:55 PM, Dave Wallace via lists.fd.io wrote:
New report generated today: 
https://gist.github.com/dwallacelf/c60164b8affb65fdef690d7500d8de1a


Please review the report and update/review/merge changes as appropriate.

Thanks,
-daw-

On 9/1/22 4:04 PM, Dave Wallace via lists.fd.io wrote:

Folks,

I have updated a gerrit change report generator authored by Ole 
Troan [0] to produce a report that categorizes the state of the 
Gerrit review queue.  Each gerrit change is labeled with the 
following status:


== ===
Status Complete    Needs To Be Addressed
== ===
V - verified   v - not verified
E - not expired    e - expired
C - no unresolved comments c - comments not resolved
R - reviewed/approved  r - review incomplete
# - days since update  # - days since update > 30
== ===

Example: [VECr 23]
    - Verified
    - Not Expired
    - No unresolved comments
    - Review incomplete (Code-Review < +1)
    - 23 days since last update

The report generator sorts the gerrit changes into three categories 
based on the state and the person or group required to perform the 
next action:


- Committers:
  Status [VECR xx]: Gerrit Changes that have been verified, are not 
expired, no unresolved comments, & approved by a maintainer.
  Action: A committer should do a final review and submit the 
change or provide comment(s).


- Maintainers:
  Status [VECr]: Gerrit Changes that have been verified, are not 
expired, no unresolved comments, & not reviewed

  Action: The Maintainer should do a code review

- Authors:
  Status : Gerrit Changes that are either not verified, 
expired, or comments not resolved
  Action: Author should rebase the change, fix verification errors, 
and/or resolve comments to move the status to [VECr]


Here is a gist of the report generated today: 
https://gist.github.com/dwallacelf/8f6e7c0ea7ae07cae1460cf49b631e6f


In the near future, I will add this to a github action to generate 
an updated report daily.


Please review the report and look for gerrit changes which require 
your attention.

All feedback welcome.

Thanks,
-daw-

[0] https://github.com/dwallacelf/gerrit-review













-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#22068): https://lists.fd.io/g/vpp-dev/message/22068
Mute This Topic: https://lists.fd.io/mt/94549931/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [vpp-dev] Move VNET features to plugins

2022-10-18 Thread Dave Wallace

Hi Neale,

Comments inline...

On 10/17/22 10:46 PM, Neale Ranns wrote:


Hi Dave,

I fully support pluginification 

Is it fair though to say that if the remaining functions of vnet have 
a dependency on one of the modules below then that module is not a 
good candidate to move to a plugin?



[daw] Agreed.

If any function in the subtask list lands into this category I would 
recommend the following:

    1. Document the dependency in a comment of the subtask
    2. Mark the sub-task as 'Will Not Do'.

That way we have a list of dependencies that could potentially be 
refactored at a later time to allow the feature(s) to be moved to a plugin.


I thinking about the dependency between IPIP and TEIB. Some of the 
IPIP functionality (i.e. p2p tunnels) can be provided without TEIB but 
some cannot (i.e. p2mp tunnels).


  * Any thoughts on infrastructure to ease plugin on plugin
dependencies. For example I seem to recall a system that used a
‘registry’ that the producer would populate and the consumer would
invoke and that invocation would be sane in the absence of a producer.

[daw] Ole brought this up during our internal discussion with the 
reference to the same mechanism. I forgot to mention that I also added a 
Jira issue [2] to address this requirement.  Any features requiring 
cross-plugin dependency management should be marked as blocked by [2].  
Let's use [2] to capture the requirements and assign a volunteer to lead 
the implementation.



 *


  * How do we [unit] test the various combinations of loaded plugins?
Perhaps the default is not to load any plugins and the test-case
specifies which set to load.



[daw] I agree that it would be best to default to not loading any 
plugins and have testcase specifications load the appropriate plugins as 
required.



Thanks,
-daw-

[2] https://jira.fd.io/browse/VPP-2060


/neale

*From: *vpp-dev@lists.fd.io  on behalf of Dave 
Wallace via lists.fd.io 

*Date: *Tuesday, 18 October 2022 at 08:57
*To: *vpp-dev 
*Subject: *[vpp-dev] Move VNET features to plugins

Folks,

There has been a long standing chore to move VNET features to plugins
for which I've created a Jira ticket [0] to coordinate getting this work
done for VPP 23.02 release.

Can the maintainers of the VNET features [1] please sign up for the
associated subtask in [0] and complete the work before the 23.02 RC1
milestone (01/18/2023).  It would be great to get this done before the
end of 2022 to avoid a large influx of changes in early January.

Thanks in advance for your help!
-daw-

[0] 
https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fjira.fd.io%2Fbrowse%2FVPP-2040data=05%7C01%7Cneale%40graphiant.com%7C888ed5dcf8744e783a0708dab08a892d%7C162101cdceb34e62ab2e3abc7aeede47%7C0%7C0%7C638016406459814597%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7Csdata=qtN1mKiFVnGYzcW3lAsg7%2FSFLd5%2Bl8NICwMuqrG0m1M%3Dreserved=0 
<https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fjira.fd.io%2Fbrowse%2FVPP-2040data=05%7C01%7Cneale%40graphiant.com%7C888ed5dcf8744e783a0708dab08a892d%7C162101cdceb34e62ab2e3abc7aeede47%7C0%7C0%7C638016406459814597%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7Csdata=qtN1mKiFVnGYzcW3lAsg7%2FSFLd5%2Bl8NICwMuqrG0m1M%3Dreserved=0>


[1] Current set of VNET features to be moved:
 BFD
 BIER
 CRYPTO
 GRE
 IPFIX-EXPORT
 IPIP
 IPSEC
 LAWFUL-INTERCEPT
 MPLS
 OSI
 POLICER
 PPP
 QOS
 SRMPLS
 SRV6
 TEIB
 TLS
 VXLAN
 VXLAN-GPE
 DEVICES:
     AF_PACKET
     PIPE
     TAP
     VIRTIO





-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#22048): https://lists.fd.io/g/vpp-dev/message/22048
Mute This Topic: https://lists.fd.io/mt/94396253/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



[vpp-dev] Move VNET features to plugins

2022-10-17 Thread Dave Wallace

Folks,

There has been a long standing chore to move VNET features to plugins 
for which I've created a Jira ticket [0] to coordinate getting this work 
done for VPP 23.02 release.


Can the maintainers of the VNET features [1] please sign up for the 
associated subtask in [0] and complete the work before the 23.02 RC1 
milestone (01/18/2023).  It would be great to get this done before the 
end of 2022 to avoid a large influx of changes in early January.


Thanks in advance for your help!
-daw-

[0] https://jira.fd.io/browse/VPP-2040

[1] Current set of VNET features to be moved:
    BFD
    BIER
    CRYPTO
    GRE
    IPFIX-EXPORT
    IPIP
    IPSEC
    LAWFUL-INTERCEPT
    MPLS
    OSI
    POLICER
    PPP
    QOS
    SRMPLS
    SRV6
    TEIB
    TLS
    VXLAN
    VXLAN-GPE
    DEVICES:
        AF_PACKET
        PIPE
        TAP
        VIRTIO



-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#22042): https://lists.fd.io/g/vpp-dev/message/22042
Mute This Topic: https://lists.fd.io/mt/94396253/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [vpp-dev] pcap_write error: bad address #pcap

2022-10-17 Thread Dave Barach
Use gdb to inspect the pcap_main_t. In particular, determine 
vec_len(pm->pcap_data) [“(gdb) vl(pm->pcap_data)”] and pm->n_pcap_data_written. 
For reasonable N pcap_write(...) is known to work.

 

D. 

 

From: vpp-dev@lists.fd.io  On Behalf Of aihua1...@163.com
Sent: Sunday, October 16, 2022 11:23 PM
To: vpp-dev@lists.fd.io
Subject: [vpp-dev] pcap_write error: bad address #pcap

 

dear all:
pcap_write,use type int n;
if  n is negative。  int n = vec_len (pm->pcap_data) - 
pm->n_pcap_data_written;
write func will failed,errno = 14.
n = write (pm->file_descriptor, 

 vec_elt_at_index (pm->pcap_data, pm->n_pcap_data_written),

n); 
int   cast   to  size_t  may case  some overflow? 


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#22041): https://lists.fd.io/g/vpp-dev/message/22041
Mute This Topic: https://lists.fd.io/mt/94377467/21656
Mute #pcap:https://lists.fd.io/g/vpp-dev/mutehashtag/pcap
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [vpp-dev] Build VPP with clean Jenkins workspace

2022-10-12 Thread Dave Wallace

Marcel,

The build failure was caused by the fact that your gerrit change was not 
based on top of master and because there was another gerrit change 
merged [0] which changed the PKG_SUFFIX in build/external/Makefile [0].  
Thus build was not updating vpp-ext-deps in the CI docker container 
because the vpp-ext-dep version (22.03-3) was the same as that which was 
already installed by the CI pre-build scripts.


I rebased 37358 which resolves the cmake failure.

Thanks,
-daw-

[0] https://github.com/FDio/vpp/blob/master/build/external/Makefile#L23

On 10/11/22 17:43, Cornu, Marcel D wrote:


Hi all,

I submitted a patch toadd support for a new version of the ipsecmb 
library, used by the crypto_ipsecmb plugin.


https://gerrit.fd.io/r/c/vpp/+/37358 



A previous build downloaded and built the new version of the library 
and the build passed, great!


Subsequentbuilds are now failing stating thatsymbols from the new 
library version can’t be found.


It seems like an old library version is being picked up by the build.

I am wondering if workspaces are isolated? Or is it possible that a 
previously installed (old) version of the library could be installed 
and accessible in the workspace?


Is there any way to wipe the Jenkins workspace and start from a clean 
state?


Thanks,

Marcel





-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#22016): https://lists.fd.io/g/vpp-dev/message/22016
Mute This Topic: https://lists.fd.io/mt/94269242/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



[vpp-dev] 2022-10-12 FD.io VPP (master branch) Gerrit Change Report

2022-10-12 Thread Dave Wallace
New report generated today 
https://gist.github.com/dwallacelf/90f2c3b1a2a59b5bc186d89650826f6b


Please review the report and update/review/merge changes as appropriate.

Thanks,
-daw-

On 9/27/22 10:09 AM, Dave Wallace via lists.fd.io wrote:
New report generated today: 
https://gist.github.com/dwallacelf/4147e4d26ca154698ea3c881426160c3


Please review the report and update/review/merge changes as appropriate.

Thanks,
-daw-


On 9/14/22 3:55 PM, Dave Wallace via lists.fd.io wrote:
New report generated today: 
https://gist.github.com/dwallacelf/c60164b8affb65fdef690d7500d8de1a


Please review the report and update/review/merge changes as appropriate.

Thanks,
-daw-

On 9/1/22 4:04 PM, Dave Wallace via lists.fd.io wrote:

Folks,

I have updated a gerrit change report generator authored by Ole 
Troan [0] to produce a report that categorizes the state of the 
Gerrit review queue.  Each gerrit change is labeled with the 
following status:


== ===
Status Complete    Needs To Be Addressed
== ===
V - verified   v - not verified
E - not expired    e - expired
C - no unresolved comments c - comments not resolved
R - reviewed/approved  r - review incomplete
# - days since update  # - days since update > 30
== ===

Example: [VECr 23]
    - Verified
    - Not Expired
    - No unresolved comments
    - Review incomplete (Code-Review < +1)
    - 23 days since last update

The report generator sorts the gerrit changes into three categories 
based on the state and the person or group required to perform the 
next action:


- Committers:
  Status [VECR xx]: Gerrit Changes that have been verified, are not 
expired, no unresolved comments, & approved by a maintainer.
  Action: A committer should do a final review and submit the change 
or provide comment(s).


- Maintainers:
  Status [VECr]: Gerrit Changes that have been verified, are not 
expired, no unresolved comments, & not reviewed

  Action: The Maintainer should do a code review

- Authors:
  Status : Gerrit Changes that are either not verified, 
expired, or comments not resolved
  Action: Author should rebase the change, fix verification errors, 
and/or resolve comments to move the status to [VECr]


Here is a gist of the report generated today: 
https://gist.github.com/dwallacelf/8f6e7c0ea7ae07cae1460cf49b631e6f


In the near future, I will add this to a github action to generate 
an updated report daily.


Please review the report and look for gerrit changes which require 
your attention.

All feedback welcome.

Thanks,
-daw-

[0] https://github.com/dwallacelf/gerrit-review










-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#22008): https://lists.fd.io/g/vpp-dev/message/22008
Mute This Topic: https://lists.fd.io/mt/94282673/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



[vpp-dev] vpp-debug-verify job enabled per-patch non-voting

2022-10-12 Thread Dave Wallace

Folks,

After removing the most egregious make test testcases which fail on the 
vpp_debug image, I have re-instated the vpp-debug-verify job as 
non-voting per-patch [0].  I will continue to work on fixing or removing 
testcases which are failing on non-related patches.


Please look for failures reported like this:
https://jenkins.fd.io/job/vpp-debug-verify-master-ubuntu2204-x86_64/1021/ 
: FAILURE (skipped)


Thanks,
-daw-

[0] https://jenkins.fd.io/job/vpp-debug-verify-master-ubuntu2204-x86_64 


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#22007): https://lists.fd.io/g/vpp-dev/message/22007
Mute This Topic: https://lists.fd.io/mt/94281766/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



[vpp-dev] 2022-09-27 FD.io VPP (master branch) Gerrit Change Report

2022-09-27 Thread Dave Wallace
New report generated today: 
https://gist.github.com/dwallacelf/4147e4d26ca154698ea3c881426160c3


Please review the report and update/review/merge changes as appropriate.

Thanks,
-daw-


On 9/14/22 3:55 PM, Dave Wallace via lists.fd.io wrote:
New report generated today: 
https://gist.github.com/dwallacelf/c60164b8affb65fdef690d7500d8de1a


Please review the report and update/review/merge changes as appropriate.

Thanks,
-daw-

On 9/1/22 4:04 PM, Dave Wallace via lists.fd.io wrote:

Folks,

I have updated a gerrit change report generator authored by Ole Troan 
[0] to produce a report that categorizes the state of the Gerrit 
review queue.  Each gerrit change is labeled with the following status:


== ===
Status Complete    Needs To Be Addressed
== ===
V - verified   v - not verified
E - not expired    e - expired
C - no unresolved comments c - comments not resolved
R - reviewed/approved  r - review incomplete
# - days since update  # - days since update > 30
== ===

Example: [VECr 23]
    - Verified
    - Not Expired
    - No unresolved comments
    - Review incomplete (Code-Review < +1)
    - 23 days since last update

The report generator sorts the gerrit changes into three categories 
based on the state and the person or group required to perform the 
next action:


- Committers:
  Status [VECR xx]: Gerrit Changes that have been verified, are not 
expired, no unresolved comments, & approved by a maintainer.
  Action: A committer should do a final review and submit the change 
or provide comment(s).


- Maintainers:
  Status [VECr]: Gerrit Changes that have been verified, are not 
expired, no unresolved comments, & not reviewed

  Action: The Maintainer should do a code review

- Authors:
  Status : Gerrit Changes that are either not verified, 
expired, or comments not resolved
  Action: Author should rebase the change, fix verification errors, 
and/or resolve comments to move the status to [VECr]


Here is a gist of the report generated today: 
https://gist.github.com/dwallacelf/8f6e7c0ea7ae07cae1460cf49b631e6f


In the near future, I will add this to a github action to generate an 
updated report daily.


Please review the report and look for gerrit changes which require 
your attention.

All feedback welcome.

Thanks,
-daw-

[0] https://github.com/dwallacelf/gerrit-review







-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#21935): https://lists.fd.io/g/vpp-dev/message/21935
Mute This Topic: https://lists.fd.io/mt/93950487/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



[vpp-dev] 'make test' failures on ubuntu2204 & debian11

2022-09-26 Thread Dave Wallace

Folks,

Due to the upgrade to ubuntu-22.04 and re-enabling multi-worker tests on 
debian-11 CI jobs, there have been a number of regressions in 'make 
test' (some intermittent failures, other hard failures).


I have disabled the offending tests [0] and rebased all of the 
outstanding gerrit changes which had failed due to these 'make test' 
failures.  See below list of jobs skipped on debian-11 [1] and 
ubuntu-22.04 [2]


I will be reaching out to maintainers to help troubleshoot, fix, and 
re-enable all of these tests and will plan to discuss this effort at 
tomorrow's VPP Community Meeting


Thanks,
-daw-

[0] https://gerrit.fd.io/r/c/vpp/+/37198
https://gerrit.fd.io/r/c/vpp/+/37144

[1] Tests Disabled on Debian-11:
- %< -
fixme-on-debian11-console-timestamp.log:01:40:53  FIXME on Debian-11: 
Wireguard Test Case [2 worker threads]
fixme-on-debian11-console-timestamp.log:01:40:53  FIXME on Debian-11: 
Wireguard Tests in multi worker setup [2 worker threads]
fixme-on-debian11-console-timestamp.log:02:04:28  FIXME on Debian-11: 
FIXME with VPP workers: test ikev2 responder - rekey [main thread only]
fixme-on-debian11-console-timestamp.log:02:04:28  FIXME on Debian-11: 
FIXME with VPP workers: test ikev2 responder - rekey repeat [main thread 
only]
fixme-on-debian11-console-timestamp.log:02:04:28  FIXME on Debian-11: 
FIXME with VPP workers: test ikev2 responder - pre shared key auth [main 
thread only]
fixme-on-debian11-console-timestamp.log:02:04:28  FIXME on Debian-11: 
FIXME with VPP workers: test ikev2 responder - rekey with key exchange 
[main thread only]
fixme-on-debian11-console-timestamp.log:02:04:28  FIXME on Debian-11: 
FIXME with VPP workers: Dead peer detection test [main thread only]
fixme-on-debian11-console-timestamp.log:02:04:28  FIXME on Debian-11: 
FIXME with VPP workers: test ikev2 responder - rekey repeat with key 
exchange [main thread only]
fixme-on-debian11-console-timestamp.log:02:04:28  FIXME on Debian-11: 
FIXME with VPP workers: test ikev2 responder - non-default table id 
[main thread only]
fixme-on-debian11-console-timestamp.log:02:08:18  FIXME on Debian-11: 
NAT44EI Test Cases [2 worker threads]
fixme-on-debian11-console-timestamp.log:02:08:44  FIXME on Debian-11: 
SOLO RUN: Memif Test Case [2 worker threads]
fixme-on-debian11-console-timestamp.log:02:09:54  FIXME on Debian-11: 
SOLO RUN: Bidirectional Forwarding Detection (BFD) [2 worker threads]
fixme-on-debian11-console-timestamp.log:02:13:19  FIXME on Debian-11: 
FIXME with VPP workers: SOLO RUN: Template verification, timer tests 
[main thread only]

- %< -

[2] Tests Disabled on Ubuntu-22.04:
- %< -
fixme-on-ubuntu2204-console-timestamp.log:01:38:53  FIXME on 
Ubuntu-22.04: ipsecmb ESNon ARon AES-CBC-256/SHA1-96 IPSec test [main 
thread only]
fixme-on-ubuntu2204-console-timestamp.log:01:38:53  FIXME on 
Ubuntu-22.04: native ESNoff ARon AES-CBC-128/MD5-96 IPSec test [main 
thread only]
fixme-on-ubuntu2204-console-timestamp.log:01:38:53  FIXME on 
Ubuntu-22.04: native ESNon ARon AES-CBC-192/SHA1-96 IPSec test [main 
thread only]
fixme-on-ubuntu2204-console-timestamp.log:01:38:53  FIXME on 
Ubuntu-22.04: native ESNon ARon AES-CBC-128/MD5-96 IPSec test [main 
thread only]
fixme-on-ubuntu2204-console-timestamp.log:01:38:53  FIXME on 
Ubuntu-22.04: native ESNoff ARoff AES-CBC-192/SHA1-96 IPSec test [main 
thread only]
fixme-on-ubuntu2204-console-timestamp.log:01:38:53  FIXME on 
Ubuntu-22.04: ipsecmb ESNon ARon AES-CBC-192/SHA1-96 IPSec test [main 
thread only]
fixme-on-ubuntu2204-console-timestamp.log:01:38:53  FIXME on 
Ubuntu-22.04: native ESNon ARon AES-CBC-256/SHA1-96 IPSec test [main 
thread only]
fixme-on-ubuntu2204-console-timestamp.log:01:38:53  FIXME on 
Ubuntu-22.04: native ESNoff ARon 3DES-CBC/SHA1-96 IPSec test [main 
thread only]
fixme-on-ubuntu2204-console-timestamp.log:01:38:53  FIXME on 
Ubuntu-22.04: native ESNoff ARoff AES-CBC-128/MD5-96 IPSec test [main 
thread only]
fixme-on-ubuntu2204-console-timestamp.log:01:38:53  FIXME on 
Ubuntu-22.04: native ESNon ARoff AES-CBC-128/MD5-96 IPSec test [main 
thread only]
fixme-on-ubuntu2204-console-timestamp.log:01:38:53  FIXME on 
Ubuntu-22.04: native ESNoff ARoff 3DES-CBC/SHA1-96 IPSec test [main 
thread only]
fixme-on-ubuntu2204-console-timestamp.log:01:38:53  FIXME on 
Ubuntu-22.04: native ESNoff ARoff AES-CBC-256/SHA1-96 IPSec test [main 
thread only]
fixme-on-ubuntu2204-console-timestamp.log:01:38:53  FIXME on 
Ubuntu-22.04: ipsecmb ESNon ARon AES-CBC-128/MD5-96 IPSec test [main 
thread only]
fixme-on-ubuntu2204-console-timestamp.log:01:38:53  FIXME on 
Ubuntu-22.04: native ESNon ARoff AES-CBC-256/SHA1-96 IPSec test [main 
thread only]
fixme-on-ubuntu2204-console-timestamp.log:01:38:53  FIXME on 
Ubuntu-22.04: native ESNon ARoff AES-CBC-192/SHA1-96 IPSec test [main 
thread only]
fixme-on-ubuntu2204-console-timestamp.log:01:38:53  FIXME on 
Ubuntu-22.04: native ESNon ARon 3DES-CBC/SHA1-96 IPSec test [main thread 
only]

[vpp-dev] Input on VPP 'make test' use cases

2022-09-16 Thread Dave Wallace

Folks,

In preparation for refactoring 'make test', I'd like to get feedback on 
the which features in test/Makefile are being used and the context for 
them (e.g. FD.io CI, downstream CI, local testing, test development).


I've created a wiki page [0] to capture the feedback.  Please edit the 
wiki page and increment any of the cases in the matrix which you use.


If you have any additional use cases that you would like to be covered, 
please add a comment at the bottom of the page.


I will plan to discuss the results of this at the next VPP community 
meeting.


Thanks,
-daw-

[0] https://wiki.fd.io/view/VPP/2022_Make_Test_Use_Case_Poll

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#21899): https://lists.fd.io/g/vpp-dev/message/21899
Mute This Topic: https://lists.fd.io/mt/93729368/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



[vpp-dev] 2022-09-14 FD.io VPP (master branch) Gerrit Change Report

2022-09-14 Thread Dave Wallace
New report generated today: 
https://gist.github.com/dwallacelf/c60164b8affb65fdef690d7500d8de1a


Please review the report and update/review/merge changes as appropriate.

Thanks,
-daw-

On 9/1/22 4:04 PM, Dave Wallace via lists.fd.io wrote:

Folks,

I have updated a gerrit change report generator authored by Ole Troan 
[0] to produce a report that categorizes the state of the Gerrit 
review queue.  Each gerrit change is labeled with the following status:


== ===
Status Complete    Needs To Be Addressed
== ===
V - verified   v - not verified
E - not expired    e - expired
C - no unresolved comments c - comments not resolved
R - reviewed/approved  r - review incomplete
# - days since update  # - days since update > 30
== ===

Example: [VECr 23]
    - Verified
    - Not Expired
    - No unresolved comments
    - Review incomplete (Code-Review < +1)
    - 23 days since last update

The report generator sorts the gerrit changes into three categories 
based on the state and the person or group required to perform the 
next action:


- Committers:
  Status [VECR xx]: Gerrit Changes that have been verified, are not 
expired, no unresolved comments, & approved by a maintainer.
  Action: A committer should do a final review and submit the change 
or provide comment(s).


- Maintainers:
  Status [VECr]: Gerrit Changes that have been verified, are not 
expired, no unresolved comments, & not reviewed

  Action: The Maintainer should do a code review

- Authors:
  Status : Gerrit Changes that are either not verified, 
expired, or comments not resolved
  Action: Author should rebase the change, fix verification errors, 
and/or resolve comments to move the status to [VECr]


Here is a gist of the report generated today: 
https://gist.github.com/dwallacelf/8f6e7c0ea7ae07cae1460cf49b631e6f


In the near future, I will add this to a github action to generate an 
updated report daily.


Please review the report and look for gerrit changes which require 
your attention.

All feedback welcome.

Thanks,
-daw-

[0] https://github.com/dwallacelf/gerrit-review




-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#21880): https://lists.fd.io/g/vpp-dev/message/21880
Mute This Topic: https://lists.fd.io/mt/93686025/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [vpp-dev] One proposal for community meeting

2022-09-06 Thread Dave Wallace

Hi Xu,

Presenting your patch is a fine idea.
I will also spend a few minutes discussing the upgrade of the CI infra 
from ubuntu-20.04 to ubuntu-22.04.


You have the correct link to join the meeting.

Thanks,
-daw-

On 9/5/22 11:18 PM, Xu, Ting wrote:


Hi,

As I see in Dave’s message, our Community Meeting will be held next 
Tuesday (9.13).


I am wondering if I can have some time to present my patch – 
packetforge (5 minutes). It’s been a long time since it was last 
reviewed, and I think perhaps it is not clear to understand.


The patch link is: https://gerrit.fd.io/r/c/vpp/+/36149

BTW, should I follow the step here https://wiki.fd.io/view/VPP/Meeting 
to join the meeting?


Thanks!

Best Regards,

Xu Ting





-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#21853): https://lists.fd.io/g/vpp-dev/message/21853
Mute This Topic: https://lists.fd.io/mt/93494249/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



[vpp-dev] Fix for vpp-csit-verify-device-master-ubuntu2204-x86_64-1n-skx job failures

2022-09-02 Thread Dave Wallace

Folks,

We're in the process of upgrading our CI infrastructure to use 
Ubuntu-22.04 LTS.  An issue was discovered that causes the vpp-device 
jobs (vpp-csit-verify-device-master-ubuntu2204-x86_64-1n-*) to fail due 
to memory exhaustion.


Damjan helped identify the root cause & correct fix [1], but gerrit 
changes which do not include this patch may still encounter the job failure:


    Java Connection Closed Exception
    Caused when the TCP connection is closed between Jenkins and the 
build executor.


I've been seeing gerrit changes which do not include this fix fail 
vpp-device tests and will be rebasing them.  If you encounter this error 
signature please rebase your gerrit change on the top of master.


Thanks,
-daw-

[0] 
https://jenkins.fd.io/job/vpp-csit-verify-device-master-ubuntu2204-x86_64-1n-skx/58/

[1] https://gerrit.fd.io/r/c/vpp/+/37036

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#21846): https://lists.fd.io/g/vpp-dev/message/21846
Mute This Topic: https://lists.fd.io/mt/93427378/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [vpp-dev] vlib_log assert in dataplane workers

2022-09-02 Thread Dave Barach
A single printf() costs more clock cycles than processing a packet through
the entire forwarding graph. It's not OK to call vlib_log() in data plane
code.  

 

D.

 

From: vpp-dev@lists.fd.io  On Behalf Of Vadim Platonov
via lists.fd.io
Sent: Friday, September 2, 2022 8:14 AM
To: vpp-dev@lists.fd.io
Subject: [vpp-dev] vlib_log assert in dataplane workers

 

Hi,

 

Could you explain the reason of the assert
https://github.com/FDio/vpp/blob/master/src/vlib/log.c#L146?

Is this the performance reason?

Could we use vlib_log on dataplane workers?

 

Best Regards,

 

Vadim Platonov

 

 


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#21845): https://lists.fd.io/g/vpp-dev/message/21845
Mute This Topic: https://lists.fd.io/mt/93417565/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



[vpp-dev] 2022-09-01 FD.io VPP (master branch) Gerrit Change Report

2022-09-01 Thread Dave Wallace

Folks,

I have updated a gerrit change report generator authored by Ole Troan 
[0] to produce a report that categorizes the state of the Gerrit review 
queue.  Each gerrit change is labeled with the following status:


== ===
Status Complete    Needs To Be Addressed
== ===
V - verified   v - not verified
E - not expired    e - expired
C - no unresolved comments c - comments not resolved
R - reviewed/approved  r - review incomplete
# - days since update  # - days since update > 30
== ===

Example: [VECr 23]
    - Verified
    - Not Expired
    - No unresolved comments
    - Review incomplete (Code-Review < +1)
    - 23 days since last update

The report generator sorts the gerrit changes into three categories 
based on the state and the person or group required to perform the next 
action:


- Committers:
  Status [VECR xx]: Gerrit Changes that have been verified, are not 
expired, no unresolved comments, & approved by a maintainer.
  Action: A committer should do a final review and submit the change or 
provide comment(s).


- Maintainers:
  Status [VECr]: Gerrit Changes that have been verified, are not 
expired, no unresolved comments, & not reviewed

  Action: The Maintainer should do a code review

- Authors:
  Status : Gerrit Changes that are either not verified, expired, 
or comments not resolved
  Action: Author should rebase the change, fix verification errors, 
and/or resolve comments to move the status to [VECr]


Here is a gist of the report generated today: 
https://gist.github.com/dwallacelf/8f6e7c0ea7ae07cae1460cf49b631e6f


In the near future, I will add this to a github action to generate an 
updated report daily.


Please review the report and look for gerrit changes which require your 
attention.

All feedback welcome.

Thanks,
-daw-

[0] https://github.com/dwallacelf/gerrit-review

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#21843): https://lists.fd.io/g/vpp-dev/message/21843
Mute This Topic: https://lists.fd.io/mt/93404542/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [vpp-dev] make install-dep fails

2022-08-23 Thread Dave Wallace

Hi Hemant,

I would recommend using a more recent Ubuntu LTS release as support for 
Ubuntu 18.04 was deprecated a many releases ago.


All of our CI/CD & CSIT infrastructure are migrating to Ubuntu 22.04 for 
the upcoming VPP 22.10 release.  I anticipate that support for Ubuntu 
20.04 will be deprecated around VPP 23.06 timeframe.


You can always look back in the git history of .../vpp/Makefile for when 
Ubuntu 18.04 was deprecated from the 'install-deps' target but there is 
no guarantee that it will still work.


Thanks,
-daw-

On 8/23/2022 11:35 AM, hemant via lists.fd.io wrote:

I am using Ubuntu 18.04. I cloned the vpp repo today. I see a failure to get
enchant-2 and libffi7. I installed libffi-dev and enchant but still see the
failure.

git clonehttps://gerrit.fd.io/r/vpp

$ sudo make install-deps
Hit:2http://us.archive.ubuntu.com/ubuntu  bionic InRelease
Hit:3http://us.archive.ubuntu.com/ubuntu  bionic-updates InRelease
Get:4http://us.archive.ubuntu.com/ubuntu  bionic-backports InRelease [74.6 kB]
Hit:1https://apt.llvm.org/bionic  llvm-toolchain-bionic-11 InRelease
Hit:5http://us.archive.ubuntu.com/ubuntu  bionic-security InRelease
Hit:6http://ppa.launchpad.net/x2go/stable/ubuntu  bionic InRelease
Fetched 74.6 kB in 1s (81.3 kB/s)
Reading package lists... Done
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package enchant-2
E: Unable to locate package libffi7
Makefile:319: recipe for target 'install-dep' failed
make: *** [install-dep] Error 100

Hemant






-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#21815): https://lists.fd.io/g/vpp-dev/message/21815
Mute This Topic: https://lists.fd.io/mt/93206813/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [vpp-dev] vlib buffer allocate/free consumes too many CPU cycles

2022-08-23 Thread Dave Barach
+1, Ben has it exactly right... Dave

On 8/23/22, 4:04 AM, "Benoit Ganne (bganne) via lists.fd.io" 
 wrote:

vlib_buffer_validate_alloc_free() should only be called with debug builds 
to debug buffer allocation issues.
Debug builds are slow, because there is no optimizations and lots of 
additional checks.
Please make sure you are using a release build before benchmarking (eg. 
make build-release).

Best
ben

> -Original Message-
> From: vpp-dev@lists.fd.io  On Behalf Of zheng jie
> Sent: Tuesday, August 23, 2022 9:23
> To: vpp-dev@lists.fd.io
> Subject: [vpp-dev] vlib buffer allocate/free consumes too many CPU cycles
> 
> hi team,
> 
> recently I am doing plugin dev with VPP,  I found all threads are spending
> too many CPU cycles with locking/unlocking (with one numa
> node)buffer_main's buffer_known_hash_lockp,  it hinders burst performance.
> 
> ```
> +6.00%  vpp_wk_4 libvlib.so.22.02.0[.]
> clib_spinlock_lock
> +5.33%  vpp_wk_7 libvlib.so.22.02.0[.]
> clib_spinlock_lock
> +5.29%  vpp_wk_9 libvlib.so.22.02.0[.]
> clib_spinlock_lock
> +5.18%  vpp_wk_2 libvlib.so.22.02.0[.]
> clib_spinlock_lock
> +5.05%  vpp_wk_0 libvlib.so.22.02.0[.]
> clib_spinlock_lock
> +4.95%  vpp_wk_10libvlib.so.22.02.0[.]
> clib_spinlock_lock
> +4.92%  vpp_wk_6 libvlib.so.22.02.0[.]
> clib_spinlock_lock
> +4.90%  vpp_wk_3 libvlib.so.22.02.0[.]
> clib_spinlock_lock
> +4.63%  vpp_wk_8 libvlib.so.22.02.0[.]
> clib_spinlock_lock
> +4.41%  vpp_wk_5 libvlib.so.22.02.0[.]
> clib_spinlock_lock
> +4.33%  vpp_wk_1 libvlib.so.22.02.0[.]
> clib_spinlock_lock
> +4.24%  vpp_wk_11libvlib.so.22.02.0[.]
> clib_spinlock_lock
> +2.27%  vpp_main libvlib.so.22.02.0[.] dispatch_node
> +0.89%  vpp_main libvlib.so.22.02.0[.]
> vlib_main_or_worker_loop
> +0.85%  vpp_main libvlib.so.22.02.0[.] vlib_get_node
> +0.83%  vpp_wk_11libvlib.so.22.02.0[.] vlib_frame_free
> +0.78%  vpp_wk_1 libvlib.so.22.02.0[.] vlib_frame_free
> +0.65%  vpp_wk_5 libvlib.so.22.02.0[.] vlib_frame_free
> +0.51%  vpp_main vcgnat_dp_plugin.so   [.]
> node_channel_tx_process
> 
> 
> ```
> 
> the calling graph:
> 
> -5.33%  vpp_wk_7 libvlib.so.22.02.0[.]
> clib_spinlock_lock
>- clib_spinlock_lock
>   - 4.89% vlib_buffer_is_known
>  - vlib_buffer_validate_alloc_free
> + 1.94% vlib_buffer_alloc_from_pool
> + 1.45% vlib_buffer_pool_put
> + 1.42% vlib_buffer_alloc_from_pool
> -5.29%  vpp_wk_9 libvlib.so.22.02.0[.]
> clib_spinlock_lock
>- clib_spinlock_lock
>   - 4.89% vlib_buffer_is_known
>  - vlib_buffer_validate_alloc_free
> + 2.14% vlib_buffer_alloc_from_pool
> + 1.40% vlib_buffer_alloc_from_pool
> + 1.28% vlib_buffer_pool_put
> +5.18%  vpp_wk_2 libvlib.so.22.02.0[.]
> clib_spinlock_lock
> -5.05%  vpp_wk_0 libvlib.so.22.02.0[.]
> clib_spinlock_lock
>- clib_spinlock_lock
>   - 4.57% vlib_buffer_is_known
>  - vlib_buffer_validate_alloc_free
> + 2.25% vlib_buffer_alloc_from_pool
> + 1.20% vlib_buffer_pool_put
> + 1.03% vlib_buffer_alloc_from_pool
> 
> 
> 
> thanks,
> Looking forward to your help.
> 







-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#21813): https://lists.fd.io/g/vpp-dev/message/21813
Mute This Topic: https://lists.fd.io/mt/93199622/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [vpp-dev] Free a vlib buffer from out a VPP worker thread

2022-08-13 Thread Dave Barach
Short answer: yes. Here's an example of how to start a foreign thread taken
from the [golang dialect] g2 viewer plugin (*):

 

/* *INDENT-OFF* */

VLIB_REGISTER_THREAD (ego_g2_thread_reg, static) = {

  .name = "g2-thread",

  .short_name = "g2",

  .function = ego_g2_thread_fn,

  .use_pthreads = 1,

  .no_data_structure_clone = 1,

  .fixed_count = 1,

  .count = 1,

};

/* *INDENT-ON* */

 

In this case, we don't clone the required data structures to free a buffer.
If you remove the initialization ".no_data_structure_clone=1", you should be
all set. Check out ".use_pthreads = 1" in src/vlib/threads.c, etc. to see if
that's what you want. 

 

HTH... Dave 

 

(*) See https://github.com/dbarach/vpp-event-viewer.git if you're interested
in the g2 viewer.

 

 

From: vpp-dev@lists.fd.io  On Behalf Of Simon Barber
via lists.fd.io
Sent: Friday, August 12, 2022 9:30 AM
To: vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] Free a vlib buffer from out a VPP worker thread

 

Dave,

 

Does VPP support the concept of  additional  threads that are spawned from
within a  plugin, lets call  them 'external threads',  and the  allocation
of a  vlib_main_t / vlib_buffer_pool_thread_t for these external threads, or
should all interactions such as freeing a buffer, be performed from within
the  worker thread that the buffer was originally presented to the plugin
on.. 

 

Cheers

 

Simon

 

 

 

 

From: vpp-dev@lists.fd.io <mailto:vpp-dev@lists.fd.io>  mailto:vpp-dev@lists.fd.io> > On Behalf Of Dave Barach via lists.fd.io
Sent: Thursday, August 11, 2022 12:07 PM
To: vpp-dev@lists.fd.io <mailto:vpp-dev@lists.fd.io> 
Subject: [EXTERNAL] Re: [vpp-dev] Free from a vlib buffer from out a VPP
worker thread

 


You don't often get email from vpp=barachs@lists.fd.io
<mailto:vpp=barachs@lists.fd.io> . Learn why this is important
<https://aka.ms/LearnAboutSenderIdentification> 



As long as the thread has an associated vlib_main_t /
vlib_buffer_pool_thread_t not accidentally shared with another thread, you
shouldn't have any problems... 

 

FWIW... Dave

 

From: vpp-dev@lists.fd.io <mailto:vpp-dev@lists.fd.io>  mailto:vpp-dev@lists.fd.io> > On Behalf Of Simon Barber via lists.fd.io
Sent: Thursday, August 11, 2022 6:42 AM
To: vpp-dev@lists.fd.io <mailto:vpp-dev@lists.fd.io> 
Subject: [vpp-dev] Free from a vlib buffer from out a VPP worker thread

 

Hi,

 

Does anybody anticipate any issues calling  vlib_buffer_free_one to free a
buffer when running on a thread that is not registered as a VPP worker
thread.

 

Initial testing indicates that it works.

 

Regards

 

Simon

 

 


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#21798): https://lists.fd.io/g/vpp-dev/message/21798
Mute This Topic: https://lists.fd.io/mt/92979452/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [vpp-dev] Free from a vlib buffer from out a VPP worker thread

2022-08-11 Thread Dave Barach
As long as the thread has an associated vlib_main_t /
vlib_buffer_pool_thread_t not accidentally shared with another thread, you
shouldn't have any problems... 

 

FWIW... Dave

 

From: vpp-dev@lists.fd.io  On Behalf Of Simon Barber
via lists.fd.io
Sent: Thursday, August 11, 2022 6:42 AM
To: vpp-dev@lists.fd.io
Subject: [vpp-dev] Free from a vlib buffer from out a VPP worker thread

 

Hi,

 

Does anybody anticipate any issues calling  vlib_buffer_free_one to free a
buffer when running on a thread that is not registered as a VPP worker
thread.

 

Initial testing indicates that it works.

 

Regards

 

Simon

 

 


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#21794): https://lists.fd.io/g/vpp-dev/message/21794
Mute This Topic: https://lists.fd.io/mt/92955560/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



[vpp-dev] Aug 2022 VPP Community Meetings are cancelled

2022-07-27 Thread Dave Wallace

Folks,

Per agreement at the last VPP Community meeting, the August 2022 VPP 
Community meetings are cancelled due to the summer holiday season.


The next VPP Community meeting is scheduled for Tuesday September 13, 
2022 at 8am PDT.


Enjoy the rest of the summer!
-daw-

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#21735): https://lists.fd.io/g/vpp-dev/message/21735
Mute This Topic: https://lists.fd.io/mt/92651804/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [vpp-dev] VPP build fails

2022-07-22 Thread Dave Houser
My mistake, I meant clang, not cmake. What version of clang? However
looking back at my post on the problem I had, it looks like I was having a
different issue.
https://lists.fd.io/g/vpp-dev/topic/92250876#21631

On Fri, Jul 22, 2022 at 2:13 PM Mohamed Naiem  wrote:

> Hi Dave,
>
> I'm using v16 and I see in build logs it is using it.
> $ cmake --version
> cmake version 3.16.3
>
> vpp# make install-dep
> !
> cmake is already the newest version (3.16.3-1ubuntu1).
>
> 
>
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#21712): https://lists.fd.io/g/vpp-dev/message/21712
Mute This Topic: https://lists.fd.io/mt/92553465/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [vpp-dev] VPP build fails

2022-07-22 Thread Dave Houser
hello,

I had the same issue. Which version of CMAKE are you using? You need to use
cmake11 or higher. I had v11 installed, but my path was still set up for
cmake 6. I fixed my paths and it was able to compile. Check your paths.

$cmake --version
$ls -l $(which cmake)

On Fri, Jul 22, 2022 at 2:03 PM Mohamed Naiem  wrote:

> Hi,
>
> I'm trying to build VPP on a linux server, I'm following the same steps I
> did before when I tested VPP but this time it is not working.
>
> git clone https://gerrit.fd.io/r/vpp
> dpkg -l | grep vpp --> Empty
> dpkg -l | grep DPDK --> Empty
> make install-dep
> make install-ext-deps
> make build-release
>
> Failed from build-release
>
> -- Build files have been written to:
> /etc/vpp/vpp/build-root/build-vpp-native/vpp
>  Building vpp in /etc/vpp/vpp/build-root/build-vpp-native/vpp 
> [1517/2527] Building CXX object
> CMakeFiles/vpp-api/vapi/CMakeFiles/vapi_cpp_test.dir/vapi_cpp_test.cpp.o
> FAILED:
> CMakeFiles/vpp-api/vapi/CMakeFiles/vapi_cpp_test.dir/vapi_cpp_test.cpp.o
> ccache /usr/lib/ccache/c++  -DHAVE_FCNTL64 -D_FORTIFY_SOURCE=2
> -I/etc/vpp/vpp/src -ICMakeFiles -I/etc/vpp/vpp/src/vpp-api/vapi/..
> -ICMakeFiles/vpp-api/vapi/.. -ICMakeFiles/vpp-api/vapi -O3 -DNDEBUG   -g
> -Werror -Wall -Wno-address-of-packed-member -O3 -fstack-protector
> -fno-common -march=corei7 -mtune=corei7-avx -MD -MT
> CMakeFiles/vpp-api/vapi/CMakeFiles/vapi_cpp_test.dir/vapi_cpp_test.cpp.o
> -MF
> CMakeFiles/vpp-api/vapi/CMakeFiles/vapi_cpp_test.dir/vapi_cpp_test.cpp.o.d
> -o CMakeFiles/vpp-api/vapi/CMakeFiles/vapi_cpp_test.dir/vapi_cpp_test.cpp.o
> -c /etc/vpp/vpp/src/vpp-api/vapi/vapi_cpp_test.cpp
> In file included from /usr/include/c++/9/string:55,
>  from /usr/include/c++/9/stdexcept:39,
>  from /usr/include/c++/9/array:39,
>  from /usr/include/c++/9/tuple:39,
>  from /usr/include/c++/9/bits/unique_ptr.h:37,
>  from /usr/include/c++/9/memory:80,
>  from /etc/vpp/vpp/src/vpp-api/vapi/vapi_cpp_test.cpp:18:
> /usr/include/c++/9/bits/basic_string.h: In static member function ‘static
> int std::__cxx11::basic_string<_CharT, _Traits,
> _Alloc>::_S_compare(std::__cxx11::basic_string<_CharT, _Traits,
> _Alloc>::size_type, std::__cxx11::basic_string<_CharT, _Traits,
> _Alloc>::size_type)’:
> /usr/include/c++/9/bits/basic_string.h:409:46: error: ‘__max’ is not a
> member of ‘__gnu_cxx::__numeric_traits’
>   409 |  if (__d > __gnu_cxx::__numeric_traits::__max)
>   |  ^
> /usr/include/c++/9/bits/basic_string.h:410:45: error: ‘__max’ is not a
> member of ‘__gnu_cxx::__numeric_traits’
>   410 |return __gnu_cxx::__numeric_traits::__max;
>   | ^
> /usr/include/c++/9/bits/basic_string.h:411:51: error: ‘__min’ is not a
> member of ‘__gnu_cxx::__numeric_traits’
>   411 |  else if (__d < __gnu_cxx::__numeric_traits::__min)
>   |   ^
> /usr/include/c++/9/bits/basic_string.h:412:45: error: ‘__min’ is not a
> member of ‘__gnu_cxx::__numeric_traits’
>   412 |return __gnu_cxx::__numeric_traits::__min;
>   | ^
> In file included from /usr/include/c++/9/bits/basic_string.h:6496,
>  from /usr/include/c++/9/string:55,
>  from /usr/include/c++/9/stdexcept:39,
>  from /usr/include/c++/9/array:39,
>  from /usr/include/c++/9/tuple:39,
>  from /usr/include/c++/9/bits/unique_ptr.h:37,
>  from /usr/include/c++/9/memory:80,
>  from /etc/vpp/vpp/src/vpp-api/vapi/vapi_cpp_test.cpp:18:
> /usr/include/c++/9/ext/string_conversions.h: In static member function
> ‘static bool __gnu_cxx::__stoa(_TRet (*)(const _CharT*, _CharT**, _Base
> ...), const char*, const _CharT*, std::size_t*, _Base
> ...)::_Range_chk::_S_chk(_TRet, std::true_type)’:
> /usr/include/c++/9/ext/string_conversions.h:75:50: error: ‘__min’ is not a
> member of ‘__gnu_cxx::__numeric_traits’
>75 |  return __val < _TRet(__numeric_traits::__min)
>   |  ^
> /usr/include/c++/9/ext/string_conversions.h:76:48: error: ‘__max’ is not a
> member of ‘__gnu_cxx::__numeric_traits’
>76 ||| __val > _TRet(__numeric_traits::__max);
>   |^
> [1580/2527] Building C object
> CMakeFiles/vnet/CMakeFiles/vnet_hsw.dir/ipsec/esp_decrypt.c.o
> ninja: build stopped: subcommand failed.
> make[1]: *** [Makefile:693: vpp-build] Error 1
> make[1]: Leaving directory '/etc/vpp/vpp/build-root'
> make: *** [Makefile:408: build-release] Error 2
>
> 
>
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#21710): https://lists.fd.io/g/vpp-dev/message/21710
Mute This Topic: 

Re: [vpp-dev] vpp refuses to use of see/use dpdk interfaces

2022-07-18 Thread Dave Houser
> 
> That's a broad question... Which kind of info are you looking for?
> 

I think you kind answered one the gaps I have filled referencing linux 
macvlans, and how the packets are forwarded. However when I run `ip -br a` I 
dont see another interface created for the RDMA (maybe I shouldn't be seeing 
one?) Is there a specific interface for RDMA created in /dev somewhere that vpp 
takes control of? Looking mostly to how the DPDK + RDMA functionality works in 
the linux kernel, and how packets get from my PF interface all the way to VPP.

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#21676): https://lists.fd.io/g/vpp-dev/message/21676
Mute This Topic: https://lists.fd.io/mt/92231790/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [vpp-dev] How to add an ACE to an already created ACL?

2022-07-14 Thread Dave Houser
Thank you for the details Andrew.
In that case I will build out a script that will dump an ACL, and rebuild with 
the new ACE entry then replace. I understand the class structure more now after 
reviewing class object that is returned with acl_dump(). Thanks again!

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#21661): https://lists.fd.io/g/vpp-dev/message/21661
Mute This Topic: https://lists.fd.io/mt/92378300/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



[vpp-dev] How to add an ACE to an already created ACL?

2022-07-14 Thread Dave Houser
I would like to create a new ACE (Access Control Entry) in an already created 
ACL (Access Control List) with the acl_plugin.so mainly trying to use the 
acl_add_replace struct.

It appears I can only add a new ACL with 1 to many entries, I can also replace 
a whole ACL by its index, and lastly delete an ACL. However there does not seem 
to be a way to add an ACE to an existing ACL.

I looked at src/plugins/acl/acl.api lines 105-144

```

define acl_add_replace

{

u32 client_index;

u32 context;

u32 acl_index; /* ~0 to add, existing ACL# to replace */

string tag[64]; /* What gets in here gets out in the corresponding tag field 
when dumping the ACLs. */

u32 count;

vl_api_acl_rule_t r[count];

option vat_help = "  [src 
IP/plen] [dst IP/plen] [sport X-Y] [dport X-Y] [proto P] [tcpflags FL MASK], 
... , ...";

};

```

Most of those values in the struct make sense (Especially since above it is a 
comment describing each parameter), except for `vl_api_acl_rule_t r[count]` I 
dont know what this does and there does not appear to be any comment on what 
its purpose is. Not sure its related. Maybe I should be using a different 
struct? So the problem is when I try to target a ACL with `acl_index`, there is 
no way I can find to tell acl_add_replace "Add an entry to the existing acl 
index, dont remove or replace ACE's", therefore the call will cause vpp to 
replace the whole ACL with whatever is in the new rule list.

Either way, how can I add a new ACE to an existing ACL without affecting other 
values in the ACL?
Also, while we are talking about ACE's, how can I replace a specific ACE in an 
ACL without affecting the other ACE's in the ACL (target a specific ACE entry 
to remove or replace)?

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#21658): https://lists.fd.io/g/vpp-dev/message/21658
Mute This Topic: https://lists.fd.io/mt/92378300/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [vpp-dev] [csit-dev] FD.io CSIT-2206 Release Report is published

2022-07-13 Thread Dave Wallace
Congratulations to the CSIT Community and all FD.io community members 
who contributed to the VPP 22.06 release and CSIT 22.06 Report!


Well done!
-daw-

On 7/13/22 11:20 AM, Andrew Yourtchenko wrote:

FYI - in case you are not on csit-dev mail list.

--a

Begin forwarded message:


*From:* "Tibor Frank via lists.fd.io" 
*Date:* 13 July 2022 at 16:46:07 CEST
*To:* csit-...@lists.fd.io
*Subject:* *[csit-dev] FD.io CSIT-2206 Release Report is published*
*Reply-To:* tifr...@cisco.com



Hi All,

FD.io CSIT-2206 report is now available on FD.io docs site:

https://s3-docs.fd.io/csit/rls2206/report/

Another successful release! Many thanks to all contributors in CSIT and

VPP communities for making it happen.

See below for CSIT-2206 release summary and pointers to specific

sections in the report.

Welcome all comments, best by email to csit-...@lists.fd.io.

Tibor

CSIT-2206 Release Summary

-

BENCHMARK TESTS

- Regressions with DPDK drivers: Change from DPDK v21.08 to DPDK v21.11

introduced regression across all tests using dpdk drivers (with 
dpdk_plugin


loaded). Compared to previous VPP release performance drop varies in the

range of -15% to -6%, depending on test. It is related to updated MTU 
checks


within DPDK code and associated VPP code changes.

- Number of CSIT 9000B frame tests failing: tests with higher 
encapsulation


overhead are failing due to exceeding default Ethernet Maximum Frame Size

value that has been reduced by MTU related VPP code changes.

- Intel Xeon Ice Lake: Performance test data for these platforms is now

provided by testbeds newly installed in FD.io CSIT labs.

- Arm Ampere Altra: Performance test data for these platforms is now 
provided


by testbeds newly installed in FD.io CSIT labs.

- Reduction of tests: Removed certain test variations executed 
iteratively for


the report (as well as in daily and weekly trending) due to physical 
testbeds


overload.

TEST FRAMEWORK

- CSIT test environment version has been updated to ver. 10.

- CSIT PAPI support: Due to issues with PAPI performance, and 
deprecation of


VAT, VPP CLI is used in CSIT for many VPP scale tests.

- General Code Housekeeping: Ongoing code optimizations and bug fixes.

Pointers to CSIT-2206 Report sections

-

1. FD.io CSIT test methodology[1]

2. VPP release notes[2]

3. VPP 64B/IMIX throughput graphs[3]

4. VPP throughput speedup multi-core[4]

5. VPP latency under load[5]

6. VPP comparisons v22.06 vs. v22.02[6]

7. VPP performance all pkt sizes & NICs [7]

8. DPDK 22.03 apps release notes[8]

9. DPDK 64B throughput graphs[9]

10. DPDK latency under load[10]

11. DPDK comparisons 22.03 vs. 21.11[11]

12. TRex 2.97 release notes[12]

13. TRex loopback 64B throughput graphs [13]

14. TRex latency under load[14]

Functional device tests (VPP_Device) are also included in the report.

[1] 
https://s3-docs.fd.io/csit/rls2206/report/introduction/methodology.html


[2] 
https://s3-docs.fd.io/csit/rls2206/report/vpp_performance_tests/csit_release_notes.html


[3] 
https://s3-docs.fd.io/csit/rls2206/report/vpp_performance_tests/packet_throughput_graphs/index.html


[4] 
https://s3-docs.fd.io/csit/rls2206/report/vpp_performance_tests/throughput_speedup_multi_core/index.html


[5] 
https://s3-docs.fd.io/csit/rls2206/report/vpp_performance_tests/packet_latency/index.html


[6] 
https://s3-docs.fd.io/csit/rls2206/report/vpp_performance_tests/comparisons/current_vs_previous_release.html


[7] 
https://s3-docs.fd.io/csit/rls2206/report/detailed_test_results/vpp_performance_results/index.html


[8] 
https://s3-docs.fd.io/csit/rls2206/report/dpdk_performance_tests/csit_release_notes.html


[9] 
https://s3-docs.fd.io/csit/rls2206/report/dpdk_performance_tests/packet_throughput_graphs/index.html


[10] 
https://s3-docs.fd.io/csit/rls2206/report/dpdk_performance_tests/packet_latency/index.html


[11] 
https://s3-docs.fd.io/csit/rls2206/report/dpdk_performance_tests/comparisons/current_vs_previous_release.html


[12] 
https://s3-docs.fd.io/csit/rls2206/report/trex_performance_tests/csit_release_notes.html


[13] 
https://s3-docs.fd.io/csit/rls2206/report/trex_performance_tests/packet_throughput_graphs/index.html


[14] 
https://s3-docs.fd.io/csit/rls2206/report/trex_performance_tests/packet_latency/index.html










-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#21653): https://lists.fd.io/g/vpp-dev/message/21653
Mute This Topic: https://lists.fd.io/mt/92359742/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [vpp-dev] Up to date documentation for working with vpp_api 2.0.0?

2022-07-12 Thread Dave Houser
@Pim,

Thank you! I saw the VPPApiClient Class, just didn't know how to use it. Your 
example should give me good direction going forward.

- Dave

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#21646): https://lists.fd.io/g/vpp-dev/message/21646
Mute This Topic: https://lists.fd.io/mt/92332743/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [vpp-dev] Up to date documentation for working with vpp_api 2.0.0?

2022-07-12 Thread Dave Houser
Also "acl_add_replace" does not work directly from vppctl

```

sudo vppctl acl_add_replace ?

unknown input `acl_add_replace ?'

```

However when I am in VAT I can run the command. Am I missing a module in VPP?

```
$ sudo vppctl show plugin
Plugin path is: /usr/lib/x86_64-linux-gnu/vpp_plugins

Plugin                                   Version                          
Description
1. ioam_plugin.so                           22.10-rc0~60-g55050c31c          
Inbound Operations, Administration, and Maintenance (OAM)
2. lldp_plugin.so                           22.10-rc0~60-g55050c31c          
Link Layer Discovery Protocol (LLDP)
3. urpf_plugin.so                           22.10-rc0~60-g55050c31c          
Unicast Reverse Path Forwarding (uRPF)
4. http_static_plugin.so                    22.10-rc0~60-g55050c31c          
HTTP Static Server
5. l3xc_plugin.so                           22.10-rc0~60-g55050c31c          L3 
Cross-Connect (L3XC)
6. mdata_plugin.so                          22.10-rc0~60-g55050c31c          
Buffer metadata change tracker.
7. ping_plugin.so                           22.10-rc0~60-g55050c31c          
Ping (ping)
8. tlsopenssl_plugin.so                     22.10-rc0~60-g55050c31c          
Transport Layer Security (TLS) Engine, OpenSSL Based
9. avf_plugin.so                            22.10-rc0~60-g55050c31c          
Intel Adaptive Virtual Function (AVF) Device Driver
10. l2tp_plugin.so                           22.10-rc0~60-g55050c31c          
Layer 2 Tunneling Protocol v3 (L2TP)
11. pppoe_plugin.so                          22.10-rc0~60-g55050c31c          
PPP over Ethernet (PPPoE)
12. pnat_plugin.so                           22.10-rc0~60-g55050c31c          
Policy 1:1 NAT
13. srv6am_plugin.so                         22.10-rc0~60-g55050c31c          
Masquerading Segment Routing for IPv6 (SRv6) Proxy
14. crypto_native_plugin.so                  22.10-rc0~60-g55050c31c          
Intel IA32 Software Crypto Engine
15. flowprobe_plugin.so                      22.10-rc0~60-g55050c31c          
Flow per Packet
16. dpdk_plugin.so                           22.10-rc0~60-g55050c31c          
Data Plane Development Kit (DPDK)
17. det44_plugin.so                          22.10-rc0~60-g55050c31c          
Deterministic NAT (CGN)
18. hs_apps_plugin.so                        22.10-rc0~60-g55050c31c          
Host Stack Applications
19. adl_plugin.so                            22.10-rc0~60-g55050c31c          
Allow/deny list plugin
20. acl_plugin.so                            22.10-rc0~60-g55050c31c          
Access Control Lists (ACL)
21. hsi_plugin.so                            22.10-rc0~60-g55050c31c          
Host Stack Intercept (HSI)
22. crypto_openssl_plugin.so                 22.10-rc0~60-g55050c31c          
OpenSSL Crypto Engine
23. dslite_plugin.so                         22.10-rc0~60-g55050c31c          
Dual-Stack Lite
24. ikev2_plugin.so                          22.10-rc0~60-g55050c31c          
Internet Key Exchange (IKEv2) Protocol
25. svs_plugin.so                            22.10-rc0~60-g55050c31c          
Source Virtual Routing and Forwarding (VRF) Select
26. vrrp_plugin.so                           22.10-rc0~60-g55050c31c          
VRRP v3 (RFC 5798)
27. tracedump_plugin.so                      22.10-rc0~60-g55050c31c          
Streaming packet trace dump plugin
28. nsim_plugin.so                           22.10-rc0~60-g55050c31c          
Network Delay Simulator
29. dns_plugin.so                            22.10-rc0~60-g55050c31c          
Simple DNS name resolver
30. mss_clamp_plugin.so                      22.10-rc0~60-g55050c31c          
TCP MSS clamping plugin
31. builtinurl_plugin.so                     22.10-rc0~60-g55050c31c          
vpp built-in URL support
32. cnat_plugin.so                           22.10-rc0~60-g55050c31c          
CNat Translate
33. perfmon_plugin.so                        22.10-rc0~60-g55050c31c          
Performance Monitor
34. dhcp_plugin.so                           22.10-rc0~60-g55050c31c          
Dynamic Host Configuration Protocol (DHCP)
35. rdma_plugin.so                           22.10-rc0~60-g55050c31c          
RDMA IBverbs Device Driver
36. vmxnet3_plugin.so                        22.10-rc0~60-g55050c31c          
VMWare Vmxnet3 Device Driver
37. wireguard_plugin.so                      22.10-rc0~60-g55050c31c          
Wireguard Protocol
38. igmp_plugin.so                           22.10-rc0~60-g55050c31c          
Internet Group Management Protocol (IGMP)
39. nat_plugin.so                            22.10-rc0~60-g55050c31c          
Network Address Translation (NAT)
40. tlsmbedtls_plugin.so                     22.10-rc0~60-g55050c31c          
Transport Layer Security (TLS) Engine, Mbedtls Based
41. memif_plugin.so                          22.10-rc0~60-g55050c31c          
Packet Memory Interface (memif) -- Experimental
42. crypto_ipsecmb_plugin.so                 22.10-rc0~60-g55050c31c          
Intel IPSEC Multi-buffer 

[vpp-dev] Up to date documentation for working with vpp_api 2.0.0?

2022-07-12 Thread Dave Houser
Hello,

I am new to working with the vpp-api. I tried reading the documentation found 
here ( https://wiki.fd.io/view/VPP/Python_API ) , however I am unable import 
"VPP" from "vpp_papi". Looking at the source for 
"/usr/lib/python3/dist-packages/vpp_papi/vpp_papi.py", there is no class called 
"VPP".

I am a total newb working with vpp-api, can someone point me in the right 
direction on how I can get started? Main goal is to create an ACL, add ACE's, 
change them, and remove them.

Any help would be appreciated, thanks!

- Dave

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#21643): https://lists.fd.io/g/vpp-dev/message/21643
Mute This Topic: https://lists.fd.io/mt/92332743/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



[vpp-dev] Does VPP support Bluefield-2 NIC with offload?

2022-07-11 Thread Dave Houser
Hello,

I am curious if VPP supports Mellanox Bluefield-2 NIC, and support offload via 
GRPC?

I cant seem to find any documentation on if it is or not, or how to compile it. 
I did find this post ( https://lists.fd.io/g/vpp-dev/topic/83910198#19718 ) 
where someone else was trying to get a Bluefield-2 NIC to work but ran into 
problems. The post did not seem to have a conclusion though.

Want to make sure the NIC and offload are supported before I go down a rabbit 
hole of trying to get it to work. Any insight?

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#21640): https://lists.fd.io/g/vpp-dev/message/21640
Mute This Topic: https://lists.fd.io/mt/92310487/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [vpp-dev] Reg Failure in make pkg-rpm with stable/2206 branch

2022-07-08 Thread Dave Wallace

Hi Archana,

Unfortunately the RPM package builds have been unsupported for several 
years and CentOS CI jobs removed a few releases ago.


Thus you are essentially on your own unless someone else who have been 
building rpm packages locally has any pointers.


Thanks,
-daw-

On 7/1/22 6:32 AM, Archana Sampath wrote:


Hi Team,

I am compiling vpp on centos 7 machine . Gcc version is 9.3.1.
I am facing the below issue when I  issue "make pkg-rpm" .
Kindly advise what needs to be done.

+ /usr/lib/rpm/check-buildroot
+ /usr/lib/rpm/redhat/brp-compress
+ /usr/lib/rpm/redhat/brp-strip-static-archive /usr/bin/strip
+ /usr/lib/rpm/brp-python-bytecompile /usr/bin/python 1
Bytecompiling .py files below 
/data/archana/vpp_code/vpp/build-root/rpmbuild/BUILDROOT/vpp-22.06-release.x86_64/usr/lib/python3.6 
using /usr/bin/python3.6
Compiling 
/data/archana/vpp_code/vpp/build-root/rpmbuild/BUILDROOT/vpp-22.06-release.x86_64/usr/share/vpp/vppapigen_c.py 
...

  File "/usr/share/vpp/vppapigen_c.py", line 1298
    output += f"      return sizeof(*a)"
                                       ^
SyntaxError: invalid syntax

error: Bad exit status from /var/tmp/rpm-tmp.8XvMf6 (%install)


RPM build errors:
    Bad exit status from /var/tmp/rpm-tmp.8XvMf6 (%install)
make[1]: *** [Makefile:54: RPM] Error 1
make[1]: Leaving directory '/data/archana/vpp_code/vpp/extras/rpm'
make: *** [Makefile:619: pkg-rpm] Error 2


Thanks & Regards,
Archana




-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#21639): https://lists.fd.io/g/vpp-dev/message/21639
Mute This Topic: https://lists.fd.io/mt/92105557/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [vpp-dev] vpp refuses to use of see/use dpdk interfaces

2022-07-08 Thread Dave Houser
@Rupesh,

Thanks for the info. I am not too familiar with rdma interfaces, well at least 
the way vpp is utilizing them. It seems its polling the interfaces just like 
dpdk. I am also able to see traffic flowing through vpp, however its seems I 
can still interact with the ports via the kernel. This means that the 
interfaces are still being utilized by the kernel yes?

However my test traffic is flowing much more efficiently through the system 
than using just the interfaces with a basic linux kernel set up. I can only 
assume dpdk or rdma or a combination of both are being used properly. Matt was 
a great help and shared this link ( 
https://s3-docs.fd.io/vpp/22.10/developer/devicedrivers/rdma.html?highlight=rdma
 ) to documentation from vpp on rdma, however I would to read more about how 
the RDMA + DPDK system works. Do you have any other literature or documentation 
I can read?

Also, unrelated question, it appears with startup.conf I can set the number of 
rx/tx ques and size, what is the default values for this? Does it use whatever 
ethtool -l and ethtool -g uses? Or do I need to set to maximums for those 
values to apply?

I think its all working now, thanks again to all your help and quick responses 
:)

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#21638): https://lists.fd.io/g/vpp-dev/message/21638
Mute This Topic: https://lists.fd.io/mt/92231790/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [vpp-dev] vpp refuses to use of see/use dpdk interfaces

2022-07-08 Thread Dave Houser
OK I am not sure what combination got everything to work but the interfaces are 
showing up now in vppctl!

also rdma commands work as well.

I think it was a combination of the following:

* git clone the repo
* edit build/external/packages/dpdk.mk, * turn the following to "y" 
(DPDK_MLX4_PMD, DPDK_MLX5_PMD, DPDK_MLX5_COMMON_PMD)
* Set DPDK_MLX_IBV_LINK to static

* make make wipe-release;make build-release
* make pkg-deb
* sudo dpkg -i build-root/*.deb
* Create conf file without comments (optinal) * sudo cp /etc/vpp/startup.conf 
/etc/vpp/startup.conf.original; cat /etc/vpp/startup.conf | grep -v "^#.*" | 
grep -v ".*#.*" | awk 'NF' > /etc/vpp/startup.conf
* edit the file and add your dpdk interfaces make sure to add the dpdk section

* restart vpp

I suppose the only question I have is how is it possible the dpdk interfaces 
are showing up in vpp?

I ask this as the interfaces I configured in startup.conf are still linked to 
the kernel and up. However they still show up in vpp as interfaces. If I 
deactivate the interfaces, unbind from the kernel, and bind to dpdk, then 
restart vpp, then they dont show up. Is this expected?

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#21636): https://lists.fd.io/g/vpp-dev/message/21636
Mute This Topic: https://lists.fd.io/mt/92231790/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [vpp-dev] vpp refuses to use of see/use dpdk interfaces

2022-07-08 Thread Dave Houser
I was able to `mke pkg-dep` and `sudo dpkg -i build-root/*.deb`, however after 
install when running vpp service and checking logs I see the following:

```

$ sudo vpp show logs

mlx5_common: Cannot load glue library: 
/home/ubuntu/vpp/vpp/build-root/install-vpp-native/external/lib/dpdk/pmds-22.1-glue/librte_common_mlx5_glue.so.22.1:
 cannot open shared object file: No such file or directory

mlx5_common: Cannot initialize MLX5 common due to missing run-time dependency 
on rdma-core libraries (libibverbs, libmlx5)

vlib_call_all_config_functions: unknown input `show logs'

```
Its not clear to me from these instructions ( 
https://wiki.fd.io/view/VPP/Build,_install,_and_test_images#Build_A_VPP_Package 
) if I need to do anything after `make build`. Here is the output after make 
build completes

```
-- Configuring done
-- Generating done
-- Build files have been written to: 
/home/ubuntu/vpp/vpp/build-root/build-vpp_debug-native/vpp
 Building vpp in /home/ubuntu/vpp/vpp/build-root/build-vpp_debug-native/vpp 

[2498/2498] Linking C shared library 
lib/x86_64-linux-gnu/vpp_plugins/unittest_plugin.so
 Installing vpp 
[0/1] Install the project...
-- Install configuration: "debug"
make[1]: Leaving directory '/home/ubuntu/vpp/vpp/build-root'
```
Did it install? Do I need to create a deb package instead? Will my dpdk.mk 
changes be used in the `make pkg-deb`

I read this post ( https://lists.fd.io/g/vpp-dev/topic/77247865#17634 ) seems 
other have had the same issue. @Matt you stated

> 
> "Yeah, it seems so. Either build configurations need to be updated to
> install the glue libraries or you might be able to change
> ibverbs_link=dlopen to ibverbs_link=static."
> 

I adjusted build/external/packages/dpdk.mk, DPDK_MLX_IBV_LINK ?=static, then 
ran make pkg-deb, and installed but I get the same error. It seems DPDK is not 
linking, is there any fix for this? I am fine with using RDMA, however my 
previous post shows the commands just dont work.

Any recommendations on next steps?

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#21635): https://lists.fd.io/g/vpp-dev/message/21635
Mute This Topic: https://lists.fd.io/mt/92231790/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [vpp-dev] make install-dep on Ubuntu 18.04 fails

2022-07-08 Thread Dave Houser
Just saw this reply, thanks Matt.

Ok, well I got it working either way, just need to do a `make build` and skip 
`make install-dep`

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#21633): https://lists.fd.io/g/vpp-dev/message/21633
Mute This Topic: https://lists.fd.io/mt/92250876/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [vpp-dev] make install-dep on Ubuntu 18.04 fails

2022-07-08 Thread Dave Houser
Figured it out. I had clang-11 installed, but the build was using "clang" which 
was linked to clang v6 still on my system.

```

mv /usr/bin/clang /usr/bin/clang-6-old
ln -s /usr/bin/clang-11 /usr/bin/clang
```
Still in the end, make-build-dep fails because of the following on Ubuntu 18.04

```

E: Unable to locate package enchant-2

E: Unable to locate package libffi7

```

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#21632): https://lists.fd.io/g/vpp-dev/message/21632
Mute This Topic: https://lists.fd.io/mt/92250876/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [vpp-dev] make install-dep on Ubuntu 18.04 fails

2022-07-08 Thread Dave Houser
It seems I need to run `./extras/vagrant/build.sh` instead of running `make 
install-dep`. I can see earlier in the process that the same errors happen but 
are ignored and compiling continues. However I ran into a new error with clang, 
how do I get past this?

```

-- Configuring done

-- Generating done

-- Build files have been written to: 
/home/ubuntu/vpp/vpp/build-root/build-vpp-native/vpp

 Building vpp in /home/ubuntu/vpp/vpp/build-root/build-vpp-native/vpp 

[766/2348] Building C object 
CMakeFiles/vnet/CMakeFiles/vnet_objs.dir/ipsec/ipsec_spd_policy.c.o

FAILED: CMakeFiles/vnet/CMakeFiles/vnet_objs.dir/ipsec/ipsec_spd_policy.c.o

/usr/bin/clang --target=x86_64-linux-gnu -D_FORTIFY_SOURCE=2 
-I/home/ubuntu/vpp/vpp/src 
-I/home/ubuntu/vpp/vpp/build-root/build-vpp-native/vpp/CMakeFiles 
-I/home/ubuntu/vpp/vpp/build-root/build-vpp-native/vpp/CMakeFiles/vnet -fPIC -g 
-Werror -Wall -Wno-address-of-packed-member -O3 -fstack-protector -fno-common 
-march=corei7 -mtune=corei7-avx -MD -MT 
CMakeFiles/vnet/CMakeFiles/vnet_objs.dir/ipsec/ipsec_spd_policy.c.o -MF 
CMakeFiles/vnet/CMakeFiles/vnet_objs.dir/ipsec/ipsec_spd_policy.c.o.d -o 
CMakeFiles/vnet/CMakeFiles/vnet_objs.dir/ipsec/ipsec_spd_policy.c.o -c 
/home/ubuntu/vpp/vpp/src/vnet/ipsec/ipsec_spd_policy.c

/home/ubuntu/vpp/vpp/src/vnet/ipsec/ipsec_spd_policy.c:618:30: error: suggest 
braces around initialization of subobject [-Werror,-Wmissing-braces]

ipsec_fp_5tuple_t mask = { 0 }, policy_5tuple;

^

{}

/home/ubuntu/vpp/vpp/src/vnet/ipsec/ipsec_spd_policy.c:618:30: error: suggest 
braces around initialization of subobject [-Werror,-Wmissing-braces]

ipsec_fp_5tuple_t mask = { 0 }, policy_5tuple;

^

{}

/home/ubuntu/vpp/vpp/src/vnet/ipsec/ipsec_spd_policy.c:618:30: error: suggest 
braces around initialization of subobject [-Werror,-Wmissing-braces]

ipsec_fp_5tuple_t mask = { 0 }, policy_5tuple;

^

{}

/home/ubuntu/vpp/vpp/src/vnet/ipsec/ipsec_spd_policy.c:618:30: error: suggest 
braces around initialization of subobject [-Werror,-Wmissing-braces]

ipsec_fp_5tuple_t mask = { 0 }, policy_5tuple;

^

{}

/home/ubuntu/vpp/vpp/src/vnet/ipsec/ipsec_spd_policy.c:698:30: error: suggest 
braces around initialization of subobject [-Werror,-Wmissing-braces]

ipsec_fp_5tuple_t mask = { 0 }, policy_5tuple;

^

{}

/home/ubuntu/vpp/vpp/src/vnet/ipsec/ipsec_spd_policy.c:698:30: error: suggest 
braces around initialization of subobject [-Werror,-Wmissing-braces]

ipsec_fp_5tuple_t mask = { 0 }, policy_5tuple;

^

{}

/home/ubuntu/vpp/vpp/src/vnet/ipsec/ipsec_spd_policy.c:698:30: error: suggest 
braces around initialization of subobject [-Werror,-Wmissing-braces]

ipsec_fp_5tuple_t mask = { 0 }, policy_5tuple;

^

{}

/home/ubuntu/vpp/vpp/src/vnet/ipsec/ipsec_spd_policy.c:698:30: error: suggest 
braces around initialization of subobject [-Werror,-Wmissing-braces]

ipsec_fp_5tuple_t mask = { 0 }, policy_5tuple;

^

{}

8 errors generated.

[861/2348] Building C object 
CMakeFiles/vnet/CMakeFiles/vnet_objs.dir/ipsec/esp_decrypt.c.o

ninja: build stopped: subcommand failed.

Makefile:693: recipe for target 'vpp-build' failed

make[1]: *** [vpp-build] Error 1

make[1]: Leaving directory '/home/ubuntu/vpp/vpp/build-root'

Makefile:604: recipe for target 'pkg-deb' failed

make: *** [pkg-deb] Error 2

```

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#21630): https://lists.fd.io/g/vpp-dev/message/21630
Mute This Topic: https://lists.fd.io/mt/92250876/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



[vpp-dev] make install-dep on Ubuntu 18.04 fails

2022-07-08 Thread Dave Houser
Trying to make a Mellanox supported DPDK package for VPP, I tried running `make 
install-dep` with the latest code from github but I get these errors:

```

$ make install-dep

Hit:2 https://download.docker.com/linux/ubuntu bionic InRelease

Hit:1 https://apt.llvm.org/bionic llvm-toolchain-bionic-11 InRelease

Hit:3 http://repo.zabbix.com/zabbix/5.0/ubuntu bionic InRelease

Hit:4 http://archive.ubuntu.com/ubuntu bionic InRelease

Hit:5 http://archive.ubuntu.com/ubuntu bionic-updates InRelease

Hit:6 http://archive.ubuntu.com/ubuntu bionic-backports InRelease

Hit:7 http://archive.ubuntu.com/ubuntu bionic-security InRelease

Hit:8 https://packagecloud.io/fdio/release/ubuntu bionic InRelease

Reading package lists... Done

Reading package lists... Done

Building dependency tree

Reading state information... Done

E: Unable to locate package enchant-2

E: Unable to locate package libffi7

Makefile:319: recipe for target 'install-dep' failed

make: *** [install-dep] Error 100

```
I manually compiled and installed enchant-2 and libff7 but that did not seem to 
change anything. Seems the above command is trying to download the packages 
with apt source.list but cant find it. Not sure there is a libff7 or enchant-2 
package for Ubuntu 18.04, how should I proceed?

Following instructions here ( 
https://wiki.fd.io/view/VPP/Build,_install,_and_test_images#Build_A_VPP_Package 
)

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#21629): https://lists.fd.io/g/vpp-dev/message/21629
Mute This Topic: https://lists.fd.io/mt/92250876/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [vpp-dev] vpp refuses to use of see/use dpdk interfaces

2022-07-07 Thread Dave Houser
Also, I tried performing `make pkg-deb` but get the following error while its 
building

[41/708] Linking target drivers/librte_common_mlx5.so.22.1

*FAILED: drivers/librte_common_mlx5.so.22.1*

cc  -o drivers/librte_common_mlx5.so.22.1 
drivers/librte_common_mlx5.so.22.1.p/meson-generated_.._rte_common_mlx5.pmd.c.o 
drivers/libtmp_rte_common_mlx5.a.p/common_mlx5_mlx5_devx_cmds.c.o 
drivers/libtmp_rte_common_mlx5.a.p/common_mlx5_mlx5_common.c.o 
drivers/libtmp_rte_common_mlx5.a.p/common_mlx5_mlx5_common_mp.c.o 
drivers/libtmp_rte_common_mlx5.a.p/common_mlx5_mlx5_common_mr.c.o 
drivers/libtmp_rte_common_mlx5.a.p/common_mlx5_mlx5_malloc.c.o 
drivers/libtmp_rte_common_mlx5.a.p/common_mlx5_mlx5_common_pci.c.o 
drivers/libtmp_rte_common_mlx5.a.p/common_mlx5_mlx5_common_devx.c.o 
drivers/libtmp_rte_common_mlx5.a.p/common_mlx5_mlx5_common_utils.c.o 
drivers/libtmp_rte_common_mlx5.a.p/common_mlx5_linux_mlx5_nl.c.o 
drivers/libtmp_rte_common_mlx5.a.p/common_mlx5_linux_mlx5_common_auxiliary.c.o 
drivers/libtmp_rte_common_mlx5.a.p/common_mlx5_linux_mlx5_common_os.c.o 
drivers/libtmp_rte_common_mlx5.a.p/common_mlx5_linux_mlx5_common_verbs.c.o 
drivers/libtmp_rte_common_mlx5.a.p/common_mlx5_linux_mlx5_glue.c.o 
-Wl,--as-needed -Wl,--no-undefined -Wl,-O1 -shared -fPIC -Wl,--start-group 
-Wl,-soname,librte_common_mlx5.so.22 -Wl,--no-as-needed -pthread -lm -ldl 
lib/librte_hash.so.22.1 lib/librte_eal.so.22.1 lib/librte_kvargs.so.22.1 
lib/librte_telemetry.so.22.1 lib/librte_net.so.22.1 lib/librte_mbuf.so.22.1 
lib/librte_mempool.so.22.1 lib/librte_ring.so.22.1 lib/librte_rcu.so.22.1 
lib/librte_pci.so.22.1 drivers/librte_bus_pci.so.22.1 
drivers/librte_bus_auxiliary.so.22.1 
-Wl,--version-script=/home/ubuntu/vpp/vpp/build-root/build-vpp-native/external/src-dpdk/drivers/common/mlx5/version.map
 -lpthread -l:libmlx5.a -l:libibverbs.a -lnl-route-3 -lnl-3 -Wl,--end-group 
'-Wl,-rpath,$ORIGIN/../lib:$ORIGIN/' 
-Wl,-rpath-link,/home/ubuntu/vpp/vpp/build-root/build-vpp-native/external/build-dpdk/lib
 
-Wl,-rpath-link,/home/ubuntu/vpp/vpp/build-root/build-vpp-native/external/build-dpdk/drivers

/usr/bin/ld: 
/usr/lib/gcc/x86_64-linux-gnu/7/../../../x86_64-linux-gnu/libmlx5.a(mlx5.c.o): 
relocation R_X86_64_PC32 against symbol `stderr@@GLIBC_2.2.5' can not be used 
when making a shared object; recompile with -fPIC

/usr/bin/ld: final link failed: Bad value

collect2: error: ld returned 1 exit status

[138/708] Compiling C object 
drivers/libtmp_rte_net_mlx5.a.p/net_mlx5_mlx5_tx_empw.c.o

ninja: build stopped: subcommand failed.

Could not rebuild .

packages/dpdk.mk:208: recipe for target 
'/home/ubuntu/vpp/vpp/build-root/build-vpp-native/external/.dpdk.install.ok' 
failed

make[3]: *** 
[/home/ubuntu/vpp/vpp/build-root/build-vpp-native/external/.dpdk.install.ok] 
Error 255

make[3]: Leaving directory '/home/ubuntu/vpp/vpp/build/external'

Makefile:171: recipe for target 'ebuild-install' failed

make[2]: *** [ebuild-install] Error 2

make[2]: Leaving directory '/home/ubuntu/vpp/vpp/build/external'

Makefile:732: recipe for target 'external-install' failed

make[1]: *** [external-install] Error 2

make[1]: Leaving directory '/home/ubuntu/vpp/vpp/build-root'

Makefile:604: recipe for target 'pkg-deb' failed

make: *** [pkg-deb] Error 2

```

I see the linked library is on my host

```

Doing a search in the repo I found the following directories but no file
```
$ find . | grep librte_common_mlx5.so.22
./build-root/build-vpp-native/external/build-dpdk/drivers/librte_common_mlx5.so.22.1.p
./build-root/build-vpp-native/external/build-dpdk/drivers/librte_common_mlx5.so.22.1.p/meson-generated_.._rte_common_mlx5.pmd.c.o
./build-root/build-vpp-native/external/build-dpdk/drivers/librte_common_mlx5.so.22
```

I am not sure how else to fix this, any recommendations?

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#21627): https://lists.fd.io/g/vpp-dev/message/21627
Mute This Topic: https://lists.fd.io/mt/92231790/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [vpp-dev] vpp refuses to use of see/use dpdk interfaces

2022-07-07 Thread Dave Houser
On Thu, Jul 7, 2022 at 01:53 PM, Matthew Smith wrote:

> 
> https://s3-docs.fd.io/vpp/22.10/developer/devicedrivers/rdma.html?highlight=rdma
> 

Thanks Matt,

I unbound the interfaces from dpdk and gave back to the kernel, then restart 
vpp.
Working through the instructions, however they don't seem to work, or maybe not 
clear to me.

create int rdma host-if enp94s0f0 name rdma-0
This returns
`create interface: unknown input `rdma host-if enp65s0f6 name rd...'`

I wish there was a way to check commands I can use in vppctl (Like pressing `?` 
or tab-tab to see commands I can use based on the semantics I am using, but I 
don't see way to do this)

Dont think I ever shared the version I am running so I am now:
```
vpp# show vers
vpp v21.10.1-release built by root on 4f6ead0c141f at 2021-11-17T14:25:30
```

Am I using the command wrong?

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#21626): https://lists.fd.io/g/vpp-dev/message/21626
Mute This Topic: https://lists.fd.io/mt/92231790/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [vpp-dev] vpp refuses to use of see/use dpdk interfaces

2022-07-07 Thread Dave Houser
Hi Matt,

These are Mellanox ConnectX6 Nics.

Looking at the logs more I found these two lines:

```

$vppctl show logs

2022/07/07 17:14:19:050 notice     dpdk           EAL init args: -c 2 -n 4 
--in-memory --no-telemetry --file-prefix vpp -a :41:00.6 -a :41:01.6 
--main-lcore 1

2022/07/07 17:14:19:161 notice     dpdk           DPDK drivers found no 
Ethernet devices...

```

I just found this post ( https://lists.fd.io/g/vpp-dev/topic/87800334#20646 ) 
in the mailing list. I assume this is my issue. I did not compile from source / 
configure appropriately. (I followed these instructions here ( 
https://s3-docs.fd.io/vpp/22.10/gettingstarted/installing/index.html ) for how 
to deploy)

Which specific package would I need to compile from source? ( vpp 
vpp-plugin-core vpp-plugin-dpdk)?
Is there any documentation on how to create a RMDA interface? Would an RDMA 
interface be just as efficient as a DPDK interface?

- Dave

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#21624): https://lists.fd.io/g/vpp-dev/message/21624
Mute This Topic: https://lists.fd.io/mt/92231790/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



[vpp-dev] vpp refuses to use of see/use dpdk interfaces

2022-07-07 Thread Dave Houser
Hello,

I am not able to see my white listed dpdk interfaces in vppctl with `show
int` or `show hardware`. I did the following to integrate the interfaces.

- I shutdown the interfaces with `ifconfig`
`ifconfig enp65s0f6 down`
`ifconfig enp65s1f6 down`

- I unbound them from the kernel with dpdk_devbind.py
`sudo dpdk-devbind.py -b uio_pci_generic :41:01.6`
`sudo dpdk-devbind.py -b uio_pci_generic :41:01.6`

- I confirmed the correct interfaces were removed and bound by dpdk
`ip -br a` (interfaces removed)
`dpdk-devbind.py --status` (interfaces show up as dpdk bound interfaces)

- I made sure the interfaces were white listed in my startup.conf
```
unix {
  nodaemon
  log /var/log/vpp/vpp.log
  full-coredump
  cli-listen /run/vpp/cli.sock
}

api-trace {
  on
}

dpdk {
  dev :41:00.6
  dev :41:01.6
}
```

- I restarted vpp
`systemctl restart vpp`

- Watched journalctl -fu output
```
Jul 07 15:56:17 host1 systemd[1]: Stopping vector packet processing
engine...
Jul 07 15:56:17 host1 vnet[66266]: unix_signal_handler:190: received signal
SIGCONT, PC 0x7f5f7e426da0
Jul 07 15:56:17 host1 vnet[66266]: received SIGTERM, exiting...
Jul 07 15:56:17 host1 vnet[66266]: unix_signal_handler:190: received signal
SIGCONT, PC 0x7f5f7e426da0
Jul 07 15:56:17 host1 systemd[1]: Stopped vector packet processing engine.
Jul 07 15:56:40 host1 systemd[1]: Starting vector packet processing
engine...
Jul 07 15:56:40 host1 systemd[1]: Started vector packet processing engine.
Jul 07 15:56:40 host1 vnet[71758]: dpdk/cryptodev: dpdk_cryptodev_init:
Failed to configure cryptodev
```

- I accessed vpp
`vppctl`

Interfaces never show up. I followed everything in the following guides and
posts:
- https://lists.fd.io/g/vpp-dev/topic/10642649
- https://s3-docs.fd.io/vpp/22.02/configuration/reference.html

Here is my apt list
```
$sudo apt list | grep vpp
libvppinfra/bionic,now 21.10.1-release amd64 [installed,automatic]
libvppinfra-dev/bionic,now 21.10.1-release amd64 [installed,automatic]
python3-vpp-api/bionic 21.10.1-release amd64
vpp/bionic,now 21.10.1-release amd64 [installed]
vpp-api-java/bionic 19.04-release amd64
vpp-api-lua/bionic 19.01.3-release amd64
vpp-api-python/bionic 21.01.1-release amd64
vpp-dbg/bionic,now 21.10.1-release amd64 [installed]
vpp-dev/bionic,now 21.10.1-release amd64 [installed]
vpp-ext-deps/bionic 19.04-16 amd64
vpp-lib/bionic 19.01.3-release amd64
vpp-plugin-core/bionic,now 21.10.1-release amd64 [installed]
vpp-plugin-dpdk/bionic,now 21.10.1-release amd64 [installed]
vpp-plugins/bionic 19.01.3-release amd64
```

What am I missing? Why does vpp refuses to recognize my dpdk interfaces?
Note: these are SRIOV vf interfaces, but I dont think that matter does it?

- Dave

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#21622): https://lists.fd.io/g/vpp-dev/message/21622
Mute This Topic: https://lists.fd.io/mt/92231790/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



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

2022-06-29 Thread Dave Wallace
Congratulations to the entire FD.io Community and all who contributed to 
yet another on time, quality VPP release!


Special thanks to Andrew for his work as Release Manager.

Thanks,
-daw-

On 6/29/22 12:13 PM, Andrew Yourtchenko wrote:

Hello all,

VPP 22.06 release is complete and the artifacts are available in 
packagecloud release repository at https://packagecloud.io/fdio/release


Thanks a lot to all of you for the hard work which made this release 
possible!


Thanks to Vanessa Valderrama for the help with publishing the release 
artifacts!


Cheers! And onwards to 22.10! :-)

--a /* your friendly 22.06 release manager */




-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#21597): https://lists.fd.io/g/vpp-dev/message/21597
Mute This Topic: https://lists.fd.io/mt/92068364/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



[vpp-dev] Latest News on FD.io

2022-06-23 Thread Dave Wallace

Folks,

FD.io TSC member Ray Kinsella has been blogging recently on FD.io VPP.  
His blog posts are now included on the FD.io web site under 'The 
Latest'->'Latest News' [0].


I highly recommend that you check them out.

Many thanks to Ray for his contributions to the FD.io Community!
-daw-

[0] https://fd.io/latest/news/

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#21579): https://lists.fd.io/g/vpp-dev/message/21579
Mute This Topic: https://lists.fd.io/mt/91946428/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [vpp-dev] unable to install vpp plugin dpdk

2022-06-22 Thread Dave Wallace
Ubuntu 22.04 (Jammy Jellyfish) packages are scheduled to be produced in 
VPP 22.10 release.


Thanks,
-daw-

On 6/21/22 4:29 AM, Lokesh Chakka wrote:

$ cat /etc/apt/sources.list.d/fdio_release.list
# this file was generated by packagecloud.io  for
# the repository at https://packagecloud.io/fdio/release

deb [signed-by=/etc/apt/keyrings/fdio_release-archive-keyring.gpg] 
https://packagecloud.io/fdio/release/ubuntu/ focal main
deb-src [signed-by=/etc/apt/keyrings/fdio_release-archive-keyring.gpg] 
https://packagecloud.io/fdio/release/ubuntu/ focal main


tried jammy. not working. kept focal. able to install the vpp

Thanks & Regards
--
Lokesh Chakka.


On Tue, Jun 21, 2022 at 1:52 PM Benoit Ganne (bganne) via lists.fd.io 
  wrote:


Are you sure you're downloading the right packages for your distro?
Check the content of /etc/apt/sources.list.d/fdio_release.list and
/etc/os-release.

ben

> -Original Message-
> From: vpp-dev@lists.fd.io  On Behalf Of
Lokesh Chakka
> Sent: Tuesday, June 21, 2022 9:36
> To: vpp-dev@lists.fd.io
> Subject: [vpp-dev] unable to install vpp plugin dpdk
>
> Hello,
>
> =
>
> $ sudo apt-get install vpp-plugin-dpdk
> Reading package lists... Done
> Building dependency tree... Done
> Reading state information... Done
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
>
> The following packages have unmet dependencies:
>  vpp-plugin-dpdk : Depends: libssl1.1 (>= 1.1.0) but it is not
installable
> E: Unable to correct problems, you have held broken packages.
>
> =
>
>
> libssl is already the latest one. I have already installed dpdk. Can
> someone please help me fixing the issue
>
>
>
> Thanks & Regards
> --
> Lokesh Chakka.








-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#21573): https://lists.fd.io/g/vpp-dev/message/21573
Mute This Topic: https://lists.fd.io/mt/91895180/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [vpp-dev] Configuring linux kernel bond interface in VPP

2022-06-22 Thread Dave Wallace

Folks,

Unfortunately when performing an internet search for VPP's 
documentation, the first link found is commonly a very old copy on 
Read-The-Docs and often times a cloned RTD project.  Equally sad is the 
fact that the early doc sets did not include release labels, so it is 
not easy to discover the documentation is dated.


Here is a link to the VPP 22.06 documentation which is the equivalent 
circa VPP 18.07 doc section that Pim references below: 
https://s3-docs.fd.io/vpp/22.06/configuration/config_getting_started.html#configuration-file-startup-conf


Thanks,
-daw-

On 6/18/22 1:36 PM, Pim van Pelt wrote:

Hoi,


On Fri, Jun 17, 2022 at 8:41 AM Chinmaya Aggarwal 
 wrote:


Hi,

We configure linux kernel physical interface on VPP using below
steps:-

1. Whitelisting the physical interface in /etc/vpp/startup.conf.
2. Bringing the kernel interface down.
3. Restarting vpp service.

Is there a similar way by which we can configure linux bond
interface in VPP? I don't see pci address for bond interface in linux.

No, you cannot create a bond in Linux and make use of that in VPP. 
Bonding is a kernel driver that makes use of physical network card 
(and their driver), so you will not see a PCI address for a bonded 
ethernet device in Linux.


However, you can do it the other way around -- create the bond in VPP 
and then expose it in Linux using the Linux Control Plane.

See an example of this in https://ipng.ch/s/articles/2021/08/25/vpp-4.html

There's another way of creating the bond in startup.conf -- search for 
the string eth_bond0 in the documentation here:

https://my-vpp-docs.readthedocs.io/en/latest/gettingstarted/users/configuring/startup.html


groet,
Pim
--
Pim van Pelt 
PBVP1-RIPE - http://www.ipng.nl/




-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#21572): https://lists.fd.io/g/vpp-dev/message/21572
Mute This Topic: https://lists.fd.io/mt/91816581/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [vpp-dev] FD.io CI Outage

2022-06-21 Thread Dave Wallace

Folks,

Jenkins was restarted last night which resolved the outage.  RCA is 
still being investigated.


Thanks,
-daw-

On 6/20/22 4:36 PM, Dave Wallace via lists.fd.io wrote:

Folks,

Jenkins.fd.io was inadvertently put into maintenance mode on 
Saturday.  It was taken out of maintenance mode about 5 hours ago, but 
VPP & CSIT jobs are still stuck in the Jenkins Build Queue (currently 
18 jobs in the queue).


LF-IT tickets [0] have been opened and resolution of the issue is ongoing.

Thank you for your patience as today is a US Holiday and the regular 
LF-IT support team is short staffed.

-daw-

[0] 
https://jira.linuxfoundation.org/plugins/servlet/theme/portal/2/IT-24179

https://jira.linuxfoundation.org/plugins/servlet/theme/portal/2/IT-24181




-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#21562): https://lists.fd.io/g/vpp-dev/message/21562
Mute This Topic: https://lists.fd.io/mt/91886472/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



[vpp-dev] FD.io CI Outage

2022-06-20 Thread Dave Wallace

Folks,

Jenkins.fd.io was inadvertently put into maintenance mode on Saturday.  
It was taken out of maintenance mode about 5 hours ago, but VPP & CSIT 
jobs are still stuck in the Jenkins Build Queue (currently 18 jobs in 
the queue).


LF-IT tickets [0] have been opened and resolution of the issue is ongoing.

Thank you for your patience as today is a US Holiday and the regular 
LF-IT support team is short staffed.

-daw-

[0] https://jira.linuxfoundation.org/plugins/servlet/theme/portal/2/IT-24179
https://jira.linuxfoundation.org/plugins/servlet/theme/portal/2/IT-24181

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#21557): https://lists.fd.io/g/vpp-dev/message/21557
Mute This Topic: https://lists.fd.io/mt/91886472/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [vpp-dev] Jenkins Job failures do to TCP connectivity issues

2022-06-01 Thread Dave Wallace

Folks,

I found and fixed the root cause of the CI job failures.

Two of the four Nomad Server nodes were in a disconnected state wrt the 
Nomad Server Election pool (i.e. they both thought that there was no 
leader in the server pool and failed to initiate a new election).  The 
other two Nomad Servers were blissfully ignorant of the state as they 
both agreed upon the existing leader and apparently the leader was able 
to verify that all Nomad Server nodes were alive.


This issue was resolved by doing the following on each of the bogged up 
Nomad nodes sequentially:


1. Stop Nomad (sudo systemctl stop nomad)
2. Wait for the node to be set as 'left' (i.e. offline) in the leader's
   Nomad Server pool status
3. Start Nomad (sudo systemctl start nomad)

After both of the errant nodes had Nomad restarted, a new Nomad server 
pool leader was elected and the CI returned to normal.
Unfortunately the current monitoring tools were insufficient to directly 
identify the disconnected state of the two bad nodes.  I will work with 
Peter Mikus who helps maintain the servers to put a monitor in place to 
detect this state send an alert to reduce the downtime should this 
happen again.


It is not yet clear what triggered the disconnected state in the two 
Nomad server nodes and/or whether one or both of them had been in that 
state for a long time.


After resolving the issue, I have issued a 'recheck' on all VPP gerrit 
changes which failed due to TCP timeouts.  So far I have not seen any 
new job failures due to TCP connection resets.


Thanks for your patience during this outage.
-daw-

On 6/1/22 2:22 PM, Dave Wallace via lists.fd.io wrote:

Folks,

The FD.io CI is currently experiencing an rash of CI job failures do 
to TCP connection failures between Jenkins and the docker executor 
images.  I am currently working with LF-IT and the lab hosting vendor 
to diagnose and fix the issues.


Thank you in advance for your patience while this issue is being resolved.
-daw-




-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#21494): https://lists.fd.io/g/vpp-dev/message/21494
Mute This Topic: https://lists.fd.io/mt/91483014/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



[vpp-dev] Jenkins Job failures do to TCP connectivity issues

2022-06-01 Thread Dave Wallace

Folks,

The FD.io CI is currently experiencing an rash of CI job failures do to 
TCP connection failures between Jenkins and the docker executor images.  
I am currently working with LF-IT and the lab hosting vendor to diagnose 
and fix the issues.


Thank you in advance for your patience while this issue is being resolved.
-daw-

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#21490): https://lists.fd.io/g/vpp-dev/message/21490
Mute This Topic: https://lists.fd.io/mt/91483014/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



[vpp-dev] GoVPP Community Meetings (even weeks @ 6:30am Pacific Time)

2022-05-31 Thread Dave Wallace

Folks,

The GoVPP project is starting to hold GoVPP Community meetings every 
other week on even weeks @ 6:30am Pacific Time beginning this Thursday 
June 2, 2022.


A recent increase in downstream consumers has prompted holding regular 
meetings to address critical fixes / improve review/merge times, discuss 
downstream consumer requirements, proposed moving of the project from 
gerrit.fd.io to github, and improving automated CI test coverage.


Detailed meeting information and agenda can be found on the GoVPP wiki page:
https://wiki.fd.io/view/GoVPP/Meeting

Everyone interested in the GoVPP project is welcome to attend and 
encouraged to participate.


Thanks,
-daw-


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#21488): https://lists.fd.io/g/vpp-dev/message/21488
Mute This Topic: https://lists.fd.io/mt/91467384/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



  1   2   3   4   5   6   7   8   9   10   >