Goody goody, see what a promise of beer at the hottest of the day can do. Enneh. . . . ., this is nonsense: >we drink beer, and *everything* gets slow.
In Africa we certainly talk much faster, and LOUDER after a good refreshment! (And we talk very well as it is, you know that. In fact I wonder wether we do anything else) Now for the scary stuff: there IS a PROBLEM with ulibc and PREEMPT_RT. Even more scary: I forgot where I read it! but I am quite positive about it. I will try to re-read all my stuff and see where it is. The stack problem is well known in literature, but normally the other way round: You run out of memory space assigning too many and too big. So John since you are soo good with yr toolbelt: rip out the dynamic stack measuring tool and measure, than double the size. Or maybe how about tripling the old size (since it worked a while back still) And lastly I think that the whole business of error reporting by the program needs careful consideration. the problem came about when Epler broke out the error reporting to the operator and through a fifo to the user interface so he/we can internationalize it. Which is good off course. So here is a thought: Why is not all error reporting done that way! Some errors are then just marked "system error xx" which would almost automatically cause a bug report to be filed. Last question to you experts: what latencies are you measuring? cheers, j. On Fri, May 4, 2012 at 11:29 PM, Charles Steinkuehler < char...@steinkuehler.net> wrote: > On 5/4/2012 4:07 PM, John Morris wrote: > > Hi list, > > > > I'm simultaneously happy and embarrassed to present a possible fix, > > which I have tested about 3 times only. > > Verified it works here!!!! THANKS!!! > > I also don't really care much about the new huge stack-size. I might at > some point, but right now I'm running on systems with 4-12G of RAM, most > of which is just sitting around idle. :) > > If it is decided to switch out libc, I may be able to help a bit. One > of the other projects I worked on was (at the time) a floppy-disk based > linux router (LRP or Linux Router Project, which later became LEAF): > http://leaf.sourceforge.net/ > > The LEAF project is now using uClibc for space reasons, and is beginning > to port the system to arm cores (IIRC someone here was making noise > about running on a Beagle Board). > > -- > Charles Steinkuehler > char...@steinkuehler.net > > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > Emc-developers mailing list > Emc-developers@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/emc-developers > ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
