Hi Prahasur ,
mode=multi-core, corelist= is missing in configuration.
But still it will not work as it needs some code changes in VPP.
Regards,
Bindiya
On Sun, Sep 2, 2018 at 6:37 PM wrote:
> Hi,
> I configured the VPP startup.conf to bringup a crypto scheduler (the
> snippet of the conf
Hi all,
I am trying to check crypto multi-core functionality of dpdk with VPP[18.04]
I did following configuration in startup.conf.
cpu {
## In the VPP there is one main thread and optionally the user can
create worker(s)
## The main thread and worker thread(s) can be pinned to
hreads.
>
> And to be even more precise, DPDK threads are also pthreads, they just
> come with some extra stuff.
>
> What do you want to achieve?
>
> —
> Damjan
>
> On 17 May 2018, at 13:43, bindiya Kurle wrote:
>
> Hi all,
> I am tried to use use_pthread in star
Hi all,
I am tried to use use_pthread in startup.conf.but still it takes
Tried following option for creating multiple threads
cpu {
use-pthreads
main-core 1
corelist-workers 2,3
}
With this config , code always hit else part of below config ,
file : src/vlib/threads.c
Hi Ole,
Thanks for pointers for IPv6.
"Are you saying that the following works in Linux:"
[Bindiya] : Yes .Little change to your configuration below
192.0.2.1/24 -> Eth0
192.0.2.2/24 -> *Eth0.111*(vlan interface on eth0)
Or are you saying that Linux ignores the second entry and just uses the
f
Hi Ole,
Linux had allowed this configuration and test cases which were running on
Linux failed on VPP.
The reason why it had passed is that linux always picks up the 1st entry
that gets added in routing table i.e. plain interface while in VPP fib
entry always return last interface that get added.
>
> Your scenario will be a configuration error once:
>
> https://gerrit.fd.io/r/#/c/8057/
>
> is committed.
>
>
>
> /neale
>
>
>
> *From: * on behalf of bindiya Kurle <
> bindiyaku...@gmail.com>
> *Date: *Monday, 7 May 2018 at 07:27
> *To: *&q
*Hi,*
13.0.0.200 ---|GigabitEthernet1/0/0 (plain
interface)13.0.0.2
|
GigabitEthernet1/0/0.111(vlan interface)13.0.0.5packet to send out
destination IP (13.0.0.200)
Fig 1.
I am trying to configure tw
Hi ,
I am trying ipv6 ping .It is not working when ip6 classifier is configured.
Reason of non-working case from below traces ,seems classify gets attached
for icmpv6 packets and since no rule is to handle v6 classifier ping
doesn't work. Any clue how this can be changed to work?
non-working case
DBGvpp# sh ip fib 6.6.6.1/32
ipv4-VRF:0, fib_index:0, flow hash:[src dst sport dport proto ]
locks:[src:(nil):2, src:default-route:1, ]
6.6.6.1/32 fib:0 index:10 locks:3
src:classify refs:1 src-flags:added,active,
path-list:[14] locks:2 uPRF-list:8 len:0 itfs:[]
path:[14] pl-index:14 ip
iya,
>
>
>
> Could you please show me the output of:
>
> sh ip fib 6.6.6.1/32
>
>
>
> Thanks,
>
> neale
>
>
>
> *From: * on behalf of bindiya Kurle <
> bindiyaku...@gmail.com>
> *Date: *Monday, 29 January 2018 at 10:04
> *To: *"vpp-dev
Hi,
my vpp version :
DBGvpp# show version
vpp v18.04-rc0~81-g18e955e .
I am observing whenever I do classifier configuration , arp resolution does
not work
my configuration:
set interface state GigabitEthernet1/0/1 up
set interface ip address GigabitEthernet1/0/1 6.6.6.1/24
classify table mask
Hi guys ,
Use case that I am trying to achieve is :
IP packet from IP should be forwarded to certain node.
Looking at different mail chains discussed on vpp forum I thought
classifier can be used for same.
Hence tried below configuration :
My setup :
---
| ||
13 matches
Mail list logo
