L4Android performance issue
haohui.mai at gmail.com
Mon Jul 9 22:49:35 CEST 2012
Getting rid of mag does improve the performance. I want to push it
even further -- can I get rid of fb-drv completely to let L4Linux
access the hardware directly?
I played around the configuration file a little bit but I had no luck.
On Mon, Jul 9, 2012 at 4:04 AM, Adam Lackorzynski
<adam at os.inf.tu-dresden.de> wrote:
> On Fri Jul 06, 2012 at 17:07:24 -0500, Haohui Mai wrote:
>> I just got a chance to run both L4Android and Android-x86 on an Asus EEE PC to measure their performance. In short, it seems to me that
>> mag is causing some problem.
>> I ran the Android web browser, and measured the page load latency to measure the performance of both system.
>> I tried to keep the configuration of both side the same. For example, both system only use VESA, and they share the same userspace binaries.
>> L4Android did well in some cases, however, I saw more than 2x slow down from L4Android (notably http://www.android.com)
>> I suspect that this comes from mag -- I noticed that the graphics performance of L4Android is not great, for example, even boot animation lags on L4Android.
>> I suspect it'll take some time to fix, so is there a way to disable mag and let l4linux takes care of the frame buffer directly?
> Just give the fb cap, that is given to mag, directly to L4Linux.
> Additionally you need to configure L4Linux to provide the input device
> you need and adapt the io config accordingly so L4Linux can access those
> input devices.
> Adam adam at os.inf.tu-dresden.de
> Lackorzynski http://os.inf.tu-dresden.de/~adam/
> l4-hackers mailing list
> l4-hackers at os.inf.tu-dresden.de
More information about the l4-hackers