Benny, Thank you for clarification. I did not know executable pages would not swap.
Shaun wrote a patch with mlockall() and it crashed my system badly. Is there a way to lock just a specific module in memory vs. the whole Asterisk application? -Vladimir On 6/17/2012 9:39 AM, Benny Amorsen wrote: > Vladimir Mikhelson <v...@mikhelson.com> writes: > >> But interestingly enough, yesterday morning I had zero (0) bytes in the >> swap file and still experienced missing DTMF detection on an outgoing >> call. > Executables do not get written to swap, their pages just get discarded > under pressure, and reloaded directly from their original location on > disk. > > The only way to ensure that Asterisk always stays in memory is to use > the mlockall() system call; doing that would require patching Asterisk. > > > /Benny > > -- > _____________________________________________________________________ > -- Bandwidth and Colocation Provided by http://www.api-digital.com -- > New to Asterisk? Join us for a live introductory webinar every Thurs: > http://www.asterisk.org/hello > > asterisk-users mailing list > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-users > -- _____________________________________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users