On 06/06/2011 11:16, Nicolas CARRIER wrote: > Ok, everything seems to work fine on my ARM target. Will this patch be > merge with main branch so that it could be shipped with the next release > of Barry ?
Hopefully. Making use of libusb 1.0 is something that will hopefully make it into the main branch, but it's likely that there will be some (hopefully minor) changes to it before it is merged into the main branch. > Now I'm targeting Memory consumption... 12Megs a far too much for my 64M > target ^^. I've never done any analysis of memory consumption, but my first guess would be to have a look at where and how Barry::Data is used. By default each Barry::Data object will allocate a 16k buffer. It might well be that there are lots of Data objects each with their own buffer. Does your 12Megs include code loaded into RAM? If so (and your target doesn't support paging) thenit might be worth stripping out all the bits of barry that aren't needed by pppob (such as the desktop, javaloader and raw channel modes) and seeing if that helps to bring the RAM usage down. Regards, Toby ------------------------------------------------------------------------------ Simplify data backup and recovery for your virtual environment with vRanger. Installation's a snap, and flexible recovery options mean your data is safe, secure and there when you need it. Discover what all the cheering's about. Get your free trial download today. http://p.sf.net/sfu/quest-dev2dev2 _______________________________________________ Barry-devel mailing list Barry-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/barry-devel
