This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
Restrictions around freeing memory with bgpdump_free_memory
- Previous message (by thread): Two years of selective peering with RIS
- Next message (by thread): Restrictions around freeing memory with bgpdump_free_memory
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Rob Ballantyne
robballantyne3 at gmail.com
Tue Nov 28 03:11:50 CET 2023
Hi, I’m running into memory access exceptions when using bgpdump_free_memory(). I’m collecting an interval worth of BGPDUMP_ENTRYs (1 minute worth) into buckets. After I have a bucket full I do a pairwise computation (that can take some time) of just this buckets data on a thread (from a pool) while the main thread moves onto the second bucket (and then starts up potentially another thread on the second bucket). … After the thread completes its summary statistics computation, it goes to call bgpdump_free_memory() on each of the BGPDUMP_ENTRY. I mutex lock so that only on thread will execute in bgpdump_free_memory() at a time. Are there restrictions (express or implied) on how to call bgpdump_free_memory() whether multi-threaded or not? BTW, if I run just a single thread it does seem to work just fine. Thanks, Rob
- Previous message (by thread): Two years of selective peering with RIS
- Next message (by thread): Restrictions around freeing memory with bgpdump_free_memory
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]