|
From: | Marcus Müller |
Subject: | [Discuss-gnuradio] Shared Memory Confusion (was: Running out of memory during BER simulations) |
Date: | Wed, 26 Nov 2014 15:30:08 +0100 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 |
Hi Everybody, I had a very interesting dive into vmcircbuffer_sysv_shm today. Questions that arose from that are: a) why is a SYSV circbuffer implementation the default one on my linux 3.17 box? b) SYSV shared memory segments have a flag that should tell the OS to release the segment as soon as its global reference count goes to 0. If I read vmcircbuffer_sysv_shm.cc correctly, it's not getting set for all segments. That is what could have caused Felix' problems. Is that a bug? c) I think I might need someone to explain to me why our circular buffers depend on shared memory -- can't one just mmap() anonymously without generating shared memory handles underneath? d) what's the order in which circbuffer implementations are chosen? Greetings, Marcus On 11/25/2014 07:28 PM, Felix W. wrote: > That fixed it! Thanks!! > > 2014-11-25 18:48 GMT+01:00 Marcus Müller <address@hidden>: > Does increasing kernel.shmmni using sysctl to let's say 16k improve>> >> _______________________________________________ >> Discuss-gnuradio mailing list >> address@hidden >> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio >> > > > > _______________________________________________ > Discuss-gnuradio mailing list > address@hidden > https://lists.gnu.org/mailman/listinfo/discuss-gnuradio |
[Prev in Thread] | Current Thread | [Next in Thread] |