-Original Message-
From: on behalf of Ole Troan
Date: Thursday, November 2, 2017 at 7:41 AM
To: vpp-dev
Subject: [vpp-dev] VPP @ IETF 100
Guys,
VPP is in a couple of projects at the IETF 100 Hackathon in Singapore.
https://www.ietf.org/registration/MeetingWiki/wik
Hi,
in below fun ip4_lookup_inline,i have a question, please see also the
following red part.
always_inline uword
ip4_lookup_inline (vlib_main_t * vm,
vlib_node_runtime_t * node,
vlib_frame_t * frame,
in
One looks up the FIB attached to the interface the packet arrives on. The other
checks whether a previous node indicated which FIB this packet should be
forwarded via. Many nodes have documented how they use sw_if_index[], see
https://docs.fd.io/vpp/18.01/dc/da9/ip4__forward_8c.html#a981572b7783
Hi neale,
I've added a protection on it, but should it be invalid somehow?
Regards,
Ewan
yug...@telincn.com
From: Neale Ranns (nranns)
Date: 2017-11-04 23:01
To: yug...@telincn.com; vpp-dev
Subject: Re: [vpp-dev] IPV6 Forwarding error
Hi Ewan,
I would guess that fib_index0 is invalid.
/n
Hi ,
We are measuring performance of ip6 lookup in multi-core multi-worker
environments and
we don't see good scaling of performance when we keep increasing the number
of cores/workers.
We are just changing the startup.conf file to create more workers,
rx-queues, sock-mem etc. Should we do anythi
Hi neale,
I add this protection, but other errors come out in many different ways, all
are ipv6 fib process errors.
fib_node_index_t
ip6_mfib_table_lookup2 (const ip6_mfib_t *mfib,
const ip6_address_t *src,
const ip6_address_t *grp)
{
ip6_mfib
Hi Phaneendra,
Please see inline comments.
-Hongjun
From: Phaneendra Manda [mailto:mphaneen...@gmail.com]
Sent: Sunday, November 5, 2017 1:18 AM
To: Ni, Hongjun
Cc: vpp-dev@lists.fd.io; nsh_sfc-...@lists.fd.io
Subject: Re: [vpp-dev] [SFC] Query regarding SFC classifier configuration for
ip4 tra
