<div class="gmail_quote">On Fri, Sep 3, 2010 at 6:04 PM, Jan Berger <span dir="ltr"><<a href="mailto:jan.berger@video24.no">jan.berger@video24.no</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Dave Rowe got Asterisk running on ucLinux quite fast so will check with him<br>
as well - but exactly what type of work do we need to do?<br>
<br>
ucLinux got it's own version of libc etc, so I was hoping it was mostly a<br>
recompile and removal of fat - lack of MMU is not something you see that<br>
much unless you use different processes - from a c coding point of view -<br>
the difference in one app w/threading should not be that visible - or am I<br>
missing some?<br>
<br>
The main difference tend to be restrained memory.<br>
<div class="im"><br></div></blockquote><div><br></div><div>Memory fragmentation. The MMU plays tricks so the process can see a contiguous chunk of memory even when physically is not. Without MMU you are more susceptible to memory fragmentation problems.</div>
<div><br></div><div>I guess the fact that FreeSWITCH uses memory pools should help.</div><div><br></div><div>All in all, I don't see it like a onda day task fixing silly compilation issues.</div><div><br></div><div><div>
Moises Silva<br>Senior Software Engineer<br>Sangoma Technologies Inc. | NEW 100 Renfrew Drive, Suite 100, Markham ON L3R 9R6 Canada<br>t. 1 905 474 1990 x128 | e. <a href="mailto:moy@sangoma.com" target="_blank">moy@sangoma.com</a></div>
<br><br></div></div>