If you use an rx pthread to tickle your main thread [via eventfd if you like] – 
and to do nothing else – I don’t see why you’d need to lock anything.

We’d want to make a couple of very simple changes to 
.../src/vlibmemory/memory_client.c so folks can use any rx pthread function 
they like, instead of the default function.

If you’re interested, I can make those changes.

FWIW... Dave

From: vpp-dev@lists.fd.io <vpp-dev@lists.fd.io> On Behalf Of Satya Murthy
Sent: Wednesday, November 13, 2019 8:43 AM
To: vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] fd to poll in VPP-API-CLIENT with no RX thread

Thanks Dave for the quick reply.

Main problem we are seeing with having RX thread is:

1) Our application sends VPP-API-request in main thread and stores the Request 
and context information in a list
2) If the response comes in the RX thread, we need to access the context 
information list in this thread which may force us to have locks across these 
data structures to clear contention between main and RX thread.
We are worried abt performance degradation in control plane due to these locks 
when we have thousands of FIB entries ( in the order of 50K ).

--
Thanks & Regards,
Murthy
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#14588): https://lists.fd.io/g/vpp-dev/message/14588
Mute This Topic: https://lists.fd.io/mt/55586364/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to