Thank you for your reply.
I did use a VMware virtual machine before, I switched to a physical NIC for
testing and now there is no problem setting rx-num to 5.
Also, I tested redis using redis-benchmark, the specific command is as follows:
sudo taskset -c 9 bash -c
Thank you for you reply.
I did use a VMware virtual machine before, I switched to a physical NIC for
testing and now there is no problem setting rx-num to 5.
Also, I tested redis using redis-benchmark, the specific command is as follows:
sudo taskset -c 9 bash -c
Hi,
The problem seems to be that you’re using a vmxnet3 interface, so I suspect
this might be a vm configuration issue. Your current config should work but
could end up being inefficient.
With respect to your problem, I just built redis and ran redis-server and cli
over LDP. Everything
Thank you for your reply.
I tried to change num-tx-queues from 2 to 5, but it got a SIGSEGV, the
backtrace is:
#0 0x7fffb453ff89 in rte_write32_relaxed (addr=0x80007ef0, value=0)
at ../src-dpdk/lib/eal/include/generic/rte_io.h:310
#1 rte_write32 (addr=0x80007ef0, value=0)
at
Hi,
First of all, could you try this [1] with latest vpp? It’s really interesting
that iperf does not exhibit this issue.
Regarding your config, some observations:
- I see you have configured 4 worker. I would then recommend to use 4 rx-queues
and 5 tx-queues (main can send packets), as
Thanks for your reply.
I give a more detailed backtrace and config in
https://lists.fd.io/g/vpp-dev/message/22731. (
https://lists.fd.io/g/vpp-dev/message/22731, ) My installation method is to
clone vpp from github and make build on Ubuntu 22.04(Kernel version is
5.19)，and I use make run for
Thank you for your reply.
This is the stacktrace captured by gdb:
2: /home/chenweihao/vpp_dev/src/vnet/session/session.c:233 (session_is_valid)
assertion `! pool_is_free (session_main.wrk[thread_index].sessions, _e)' fails
Thread 4 "vpp_wk_1" received signal SIGABRT, Aborted.
[Switching to
I just tried iperf3 in cut-through mode, i.e., server and client attached to
the same vpp instance running 4 workers, with 128 connections and this seems to
be working fine.
Could you try that out and see if it’s also working for you? It might be that
this is something specific to how Redis
Hi,
That may very well be a problem introduced by the move of connects to first
worker. Unfortunately, I we don’t have tests for all of those corner cases yet.
However, to replicate this issue, could you provide a bit more details about
your setup and the exact backtrace? It looks like you’re
Hi vpp-team,
I'm new to VPP and I'm trying to run Redis 6.0.18 in VCL with LD_PRELOAD using
VPP 22.10 and VPP 23.02. I found that assert fails frequently in VPP 23.02, and
after checking, I found that the assert fails in the session_get function in
vnet/session/session.h. The cause was an
10 matches
Mail list logo
