On 01/19/2012 08:55 AM, Jim Abernathy wrote:
On 01/18/2012 04:34 PM, Darren Hart wrote:

On 01/18/2012 09:05 AM, Jim Abernathy wrote:

FYI for those wanting to use Soft RAID, make sure you create one very
small primary partition for GRUB2 to put the second part of the
boot-loader in.  Can't use the old process.
I strongly recommend using a separate DISK for your OS installation.
Yocto builds are hard on disks, and RAID 0 increases your risk of
failure in exchange for the added performance. I use a small SSD for my
OS disk and a large RAID0 array of spinning disks for /build and another
array for /virt (where my VM images live - easily recreated).

Learned a few things in this process. I appreciate all the help and advice.

   1. So we know that at least with Edison, btrfs does not work with
      bitbake.

This looks pretty important to me. Can you create a bug report for this Jim? It may be decided that it is a dup of the one Darren already pointed to but I would like to see someone prove that. It is not clear to me why the blockstats feature could not be supported on btrfs so could justify seperate tracking anyway. (The resolution of the one Darren pointed to will be to just disable blockstats for filesystem that don't have block devices.)

   2. When I rebuilt the system, this time I put the Linux root
      directory on an 80GB SSD. That is where I also have my clone of
      Linux-Yocto repository, poky, and download directory , DL_DIR.
   3. I have create /build with EXT4 format on a Software RAID 0
      (striped) partition, using 2 separate hard drives, to use as the
      working build directory for bitbake. I have a striped swap file on
      the same two drives. But with 8GB or RAM, I shouldn't be using
      that much.

My build times for some of the basic meta-intel BSPs is around 103 minutes.

Jim A




_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto

Reply via email to