Re: [yocto] bitbake controlling memory use

Op 08-06-2021 om 21:08 schreef Trevor Gamblin: On 2021-06-05 9:35 a.m., Gmane Admin wrote: [Please note: This e-mail is from an EXTERNAL e-mail address] Op 14-04-2021 om 06:59 schreef Richard Purdie: On Tue, 2021-04-13 at 21:14 -0400, Randy MacLeod wrote: On 2021-04-11 12:19 p.m., Alexander

Re: [yocto] bitbake controlling memory use

Op 05-06-2021 om 15:35 schreef Gmane Admin: Op 14-04-2021 om 06:59 schreef Richard Purdie: On Tue, 2021-04-13 at 21:14 -0400, Randy MacLeod wrote: On 2021-04-11 12:19 p.m., Alexander Kanavin wrote: make already has -l option for limiting new instances if load average is too high, so it's

Re: [yocto] bitbake controlling memory use

Op 14-04-2021 om 06:59 schreef Richard Purdie: On Tue, 2021-04-13 at 21:14 -0400, Randy MacLeod wrote: On 2021-04-11 12:19 p.m., Alexander Kanavin wrote: make already has -l option for limiting new instances if load average is too high, so it's only natural to add a RAM limiter too.    -l

Re: [yocto] bitbake controlling memory use

Hi, Op 18-04-2021 om 11:59 schreef Richard Purdie: On Sun, 2021-04-18 at 00:17 +0200, Gmane Admin wrote: Hi, Op 14-04-2021 om 06:59 schreef Richard Purdie: On Tue, 2021-04-13 at 21:14 -0400, Randy MacLeod wrote: On 2021-04-11 12:19 p.m., Alexander Kanavin wrote: make already has -l option

Re: [yocto] bitbake controlling memory use

Hi, Op 14-04-2021 om 06:59 schreef Richard Purdie: On Tue, 2021-04-13 at 21:14 -0400, Randy MacLeod wrote: On 2021-04-11 12:19 p.m., Alexander Kanavin wrote: make already has -l option for limiting new instances if load average is too high, so it's only natural to add a RAM limiter too.   

Re: [yocto] bitbake controlling memory use

Op 12-04-2021 om 10:13 schreef Robert ber...@yocto.user: Hi, My comments are in-line. On 11/04/2021 18:23, Gmane Admin wrote: My build machine has 8 cores + HT so bitbake enthusiastically assumes 16. However I have (only?) 16GB of RAM (+24GB swap space). 16GB of RAM has always been more

Re: [yocto] bitbake controlling memory use

to have it built into bitbake, but this would work too. On 04/11/2021 11:23 PM, Gmane Admin wrote: My build machine has 8 cores + HT so bitbake enthusiastically assumes 16. However I have (only?) 16GB of RAM (+24GB swap space). 16GB of RAM has always been more then enough with 4 core + HT, but now

Re: [yocto] bitbake controlling memory use

Op 11-04-2021 om 17:55 schreef Alexander Kanavin: On Sun, 11 Apr 2021 at 17:49, Gmane Admin <mailto:gley-yo...@m.gmane-mx.org>> wrote: Yes, and make project doesn't care, because make is called with -j 16 so that is what it does. So here's my pitch: bitbake can stop

Re: [yocto] bitbake controlling memory use

16. The individual makes don't know about each other. And normally it's not an issue (compiling c), but sometimes compiling c++ it explodes (I saw 4GB ram in use for 1 g++ and there were 4 of them). On Sun, 11 Apr 2021 at 17:23, Gmane Admin <mailto:gley-yo...@m.gmane-mx.org>> wrote:

[yocto] bitbake controlling memory use

My build machine has 8 cores + HT so bitbake enthusiastically assumes 16. However I have (only?) 16GB of RAM (+24GB swap space). 16GB of RAM has always been more then enough with 4 core + HT, but now building certain recipes (nodejs, but rust will probably do it as well) eats up more memory

Re: [yocto] How to include initrd.cpio to image

Op 03-05-2020 om 13:42 schreef Gmane Admin: Op 30-04-2020 om 23:33 schreef Gmane Admin: I am generating core-image-minimal-initramfs-edison.cpio.gz which is found in the deploy-core-image-minimal-initramfs-image-complete/ directory. When I build my image edison-image initrd gets included

Re: [yocto] perf Makefile issue building with 5.6.2 kernel image

Op 07-05-2020 om 13:36 schreef sateesh m: Hi Sir,            I am getting issue with perf tool building with 5.6.2 kernel yocto image  .can anybody knows this issue can you give any suggestions or any patch file. I got it to work in zeus with 5.6.0 kernel by copying in perf.bb from

Re: [yocto] How to include initrd.cpio to image

Op 30-04-2020 om 23:33 schreef Gmane Admin: I am generating core-image-minimal-initramfs-edison.cpio.gz which is found in the deploy-core-image-minimal-initramfs-image-complete/ directory. When I build my image edison-image initrd gets included and deployed in edison-image-edison.hddimg

Re: [yocto] [WIC] Grow last partition up to disk size

Op 01-05-2020 om 01:11 schreef Rudolf J Streif: Thanks, guys, I appreciate it. Doing it dynamically on first boot would probably work as it is a data partition and not the rootfs partition. If you use btrfs you can even resize the rootfs (mounted) partition. I will give it a try. :rjs On

[yocto] How to include initrd.cpio to image

I am generating core-image-minimal-initramfs-edison.cpio.gz which is found in the deploy-core-image-minimal-initramfs-image-complete/ directory. When I build my image edison-image initrd gets included and deployed in edison-image-edison.hddimg. But I am not using that. I also generate

Re: [yocto] Compressing btrfs image

Op 28-03-2020 om 21:06 schreef Konrad Weihmann: AFAIK there is no way to mount something without root credentials. You can loop mount the image file using udisksctl as an ordinary user, which mounts the image under /media/. fakeroot/pseudo is intercepting some calls before they will reach

Re: [yocto] Image size reduction

Op 29-03-2020 om 18:28 schreef Ajam Ali: Hi All, Actually my current image size is 3.9GB because of heavy size packages required by my project and without project required packages my image size in Yocto is 800MB. So your project adds 3.1GB right I want to reduce the image size as maximum

Re: [yocto] How to create a btrfs snapshot in the rootfs image (during build)?

Self answering below. Op 22-02-2020 om 16:06 schreef Ferry Toth: > Hi all, > > I am able to generate a rootfs image of type btrfs. > Btrfs supports subvolumes, for instance with name @. > > Using subvolumes instead of partitions allow more efficient use of the emmc compared to separate