Hello folks,
Looking at `wg_peer_assign_thread` function One can see the logic behind peer
thread assigning which is: " Use the same thread that the packet has come from,
unless its main thread. In main thread case, randomly choose a worker thread to
handoff".
I understand assigning all peers
Greetings,
Let me preface this by saying that I really do not know much about the CMake
utility. But I am trying to see if there is a way to make the DPDK libs
accessible to other plugins (aside from the dpdk plugin) that are in their
own project/subdirectory similar. I am working with v20.05
>
> On 24.10.2021., at 18:08, Mrityunjay Kumar wrote:
>
>
> Well, almost VPP experts/users are familiar about dpdk.
I don’t understand why somebody needs to be familiar with DPDK to use memif.
Actually we see more and more people looking to use VPP without DPDK so we have
significant
Well, almost VPP experts/users are familiar about dpdk.
But dollor price question, which one is stable one and less effort to
marry with VPP over shared memory,
I suggest, VPP user have both option open, let them decide, which one is
better and convenient for them.
On Sun, 24 Oct, 2021,
And what is the benefit of doing that?
—
Damjan
> On 24.10.2021., at 11:24, Mrityunjay Kumar wrote:
>
> Well, I can dump my opinion regarding this. we can disable memif plugin and
> same feature can be achieved using dpdk EAL option. For details please refer
> bellow link.
>
>
Well, I can dump my opinion regarding this. we can disable memif plugin
and same feature can be achieved using dpdk EAL option. For details
please refer bellow link.
https://doc.dpdk.org/guides/nics/memif.html
This required small patch by adding a new statrup.conf section under
dpdk {
