Hi Cipher,
Has submitted a patch to fix the VPP hang issue.
I tested in my server, and it does not hang again.
https://gerrit.fd.io/r/#/c/vpp/+/22329/
Thanks,
Hongjun
From: vpp-dev@lists.fd.io [mailto:vpp-dev@lists.fd.io] On Behalf Of Cipher Chen
Sent: Tuesday, September 24, 2019 4:28 PM
To: vpp
Hi Chris,
This is tricky... I've never ran into the issue even though I also build w/o
ext-deps from time to time.
My understanding of what could happen here: we have the top Makefile building
external dependencies outside of the VPP cmake infra. So from VPP cmake PoV,
those external libs are r
Hi,
So since you're looking into this I wanted to try and narrow down a way to
recreate. It looks like if you touch any source file in the external dpdk build
it will trigger the problem. In my case I did:
touch
build-root/build-vpp_debug-native/external/dpdk-19.05/lib/librte_mbuf/rte_mbuf.c
my code is on master commit f5667c3055dbd6755277f085c6778c2b1104aa6e
in stat_segment.c: stat_validate_counter_vector(), create two dimension:
*counter[thread_num][max]
*
--
static void
stat_validate_c
Hi,
Could you give the steps to reproduce?
Cheers,
Ole
> On 27 Sep 2019, at 11:59, jiangxiaom...@outlook.com wrote:
>
> my code is on master commit f5667c3055dbd6755277f085c6778c2b1104aa6e
> in stat_segment.c: stat_validate_counter_vector(), create two dimension:
> counter[thread_num][max]
I am seeing the same problem when remove the file you mentioned, Chris.
In my case, I had additional problems after I had removed package
vpp-ext-deps on my Ubuntu system. I had to remove
build-root/build-vpp_debug-native/vpp/CMakeCache.txt. But I still have the
problem you describe. Looks like th
If I go into build-root/build-vpp_debug-native/external/build-quicly and
make install
I get libquicly.a where it is needed.
However, then when I go back to the top and say "make build" that
libquicly.a gets removed prior to it being used.
Burt
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all mess
Hi,
We have a use case that requires us to implement a hash table with multi-thread
support. In our use case all VPP workers can add/remove/access (i.e. write and
read) entries to/from this hash table. I looked at the VPP Bihash
implementation that has the property of not requiring reader locks
Start with bihash and see how much serialization you encounter in practice. If
your use case will write the hash table anywhere near as often as it reads the
hash table, I wouldn’t think that’s a good sign...
D.
From: vpp-dev@lists.fd.io On Behalf Of
krishnamurthy.m...@gmail.com
Sent: Friday,
Hi,
I've just submitted a few changes for review (9 actually), a couple of which I
think (if and once they are approved) might should be cherry-picked to 19.08
stable. For the 2 bugs I feel meet this criteria I opened Jira tickets and
tagged them 19.08 as well as 20.01.
Is that the correct wor
10 matches
Mail list logo