imho we should boot in 64m even with x86-64. reality is once you start running stuff, data will be much bigger than code in memory usage (textures, data structures, images, audio etc.). so if we were even 30% smaller and could boot, we'd have no room for data at all.
imho there needs to be a lot of leaning down of tizen - removing dameons or merging them to save memory. trimming stuff down. this also has to happen at the ui level (eg for background apps their buffers should be removed or minimized - eg scaled down to 1/4 size or something, with back buffers and other spare buffers dumped). tizen is a bit bloated these days. :) On 07/22/2014 09:51 AM, ??? wrote: > Samsung Enterprise Portal mySingle > > Reason: the ISA itself is different. > > > > Even between x86-32 vs x86-64, usually, people report that the size > (both the binary size and runtime memory footprint) increases around > 20%. Besides, we have been using THUMB for ARM (armv7 / aarch32) to > reduce the size and aarch64 does not allow to use THUMB, which in > turn, increases the size gap between aarch32 vs aarch64 further than > x86-32 vs x86-64. > > > > Thus, it's trivial to expect that x86-64 (or even aarch64) will have > much larger size than aarch32/arm7 binaries. The question for you will > be how to reduce the size to fit in 64MB :) > > > > Cheers, > > MyungJoo. > > ------- *Original Message* ------- > > *Sender* : ???<[email protected]> S3(??)/??/System S/W > Lab(S/W??)/???? > > *Date* : 2014-07-22 09:45 (GMT+09:00) > > *Title* : Re: Re: [Dev] How should I do to make it boot on the low-end > machine with 64MB main memory? > > > > Thanks for your reply. > > > > As you expected, the image size of x86-64 is much larger then that of > arm. Also, the RSS and PSS of the > > processes on x86-64 is larger than that of arm, even though > the gap betweenthe same processes differs > > depending on the process. I also suspected like you, when I saw that > the boot with the x86-64 image failed. > > But I couldn't find the reason from where this difference comes. From > where, could you expect like you said? > > > > Best regards, > > Hyungwon Hwang > > > > ------- *Original Message* ------- > > *Sender* : ???<[email protected]> S5(??)/??/Frontier CS > Lab(S/W??)/???? > > *Date* : 2014-07-22 08:59 (GMT+09:00) > > *Title* : Re: [Dev] How should I do to make it boot on the low-end > machine with 64MB main memory? > > > > Have you compared the image size (and runtime memory footprint as > well) of ARM binaries and x86-64 binaries? I expect that the latter is > much larger. > > ------- Original Message ------- > Sender : ???S3(??)/??/System S/W Lab(S/W??)/???? > Date : 2014-07-22 08:56 (GMT+09:00) > Title : [Dev] How should I do to make it boot on the low-end machine > with 64MB main memory? > > Hi, > > I'm trying to run Tizen Linux in the machine with Intel ivy bridge, > and 64MB main memory. I followed the instructions in > https://wiki.tizen.org/wiki/Tizen_on_yocto. But it failed to boot > becuase out of memory. The image which is made after the instructions > includes weston for GUI, and systemd for init. It seems that they use > too many memory to run on the machine with 64MB. I saw that the image > core-image-sato, which includes X and matchbox for GUI and sysvinit > for init, is able to run on QEMU-ARM with 64MB, even though it failed > to do on QEMU-x86_64. But especially I am interested to boot the image > with weston. I wonder what I am missing. Is there someone who > succeeded to boot the Tizen Linux or a Linux with weston in this kind > of environments, or can give me some advice? > > > Thanks. > > > Best regards, > Hyungwon Hwang > > > -- > MyungJoo Ham (???), PHD > Frontier CS Lab, Software Center > Samsung Electronics > Cell: +82-10-6714-2858 > > > > -- > > MyungJoo Ham (???), PHD > > Frontier CS Lab, Software Center > Samsung Electronics > Cell: +82-10-6714-2858 > > > > > > _______________________________________________ > Dev mailing list > [email protected] > https://lists.tizen.org/listinfo/dev -- The above message is intended solely for the named addressee and may contain trade secret, industrial technology or privileged and confidential information otherwise protected under applicable law including the Unfair Competition Prevention and Trade Secret Protection Act. Any unauthorized dissemination, distribution, copying or use of the information contained in this communication is strictly prohibited. If you have received this communication in error, please notify the sender by email and delete this communication immediately.
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Dev mailing list [email protected] https://lists.tizen.org/listinfo/dev
