From: dpreed@reed.com
To: "Outback Dingo" <outbackdingo@gmail.com>
Cc: cerowrt-devel@lists.bufferbloat.net
Subject: [Cerowrt-devel] Pointers on build setup?
Date: Mon, 30 Apr 2012 11:14:50 -0400 (EDT) [thread overview]
Message-ID: <1335798890.08871546@apps.rackspace.com> (raw)
In-Reply-To: <CAKYr3zw-Es=4MevUL9dOrhzuuzGApdHHj-ogzBpj_r03qzNn0A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2722 bytes --]
Regarding builds - can someone who is building cerowrt from source (including kernel) point me at the recipe for building it completely from scratch?
Besides running 3.3-2 on a 3800, I've begun my project to validate that Cerowrt can run on my ubnt RouterStation Pro box, which is preliminary to doing some experimentation on dense scalability that interests me. I verified that it runs the latest stable Backfire release of OpenWRT this weekend, and it does so quite well.
My own private home build server is (essentially) a cluster of two AMD8160 8-core 32 GB servers connected with 40 Gb/s Infiniband and a 6-way RAID5 storage array on one of them that gives quite nice read performance. I'm not worried about how long it takes to do a build...
Anyway - the recipe doesn't have to be perfected for me to use it - and I suspect it's similar to OpenWRT's build, so maybe pointing me to the best help for that and what the differences are would be great.
I promise I will write the "port" experience up and post it on the Wiki, in case others want to port cerowrt to other "OpenWRT platforms" of sufficient capabilities.
David
-----Original Message-----
From: "Outback Dingo" <outbackdingo@gmail.com>
Sent: Sunday, April 29, 2012 9:42pm
To: "Dave Taht" <dave.taht@gmail.com>
Cc: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] speeding up builds
On Sun, Apr 29, 2012 at 8:15 PM, Dave Taht <dave.taht@gmail.com> wrote:
> I finally acquired a machine with 32GB of ram, an intel 3930k (6
> cores), and an SSD.
>
> I put the build_dir, /tmp and /var/tmp on ramdisks, and...
>
> This cut a complete cerowrt build (including toolchain) down from >
> 3.5 hrs down to under 45 minutes.
>
> Without the toolchain rebuild, but after a make clean (to rebuild the
> packages and kernel), it's about 28 minutes.
>
> I can see that it is possible to parallelize things more to maybe chop
> another 30% of of things...
> ...but I'm glad to have 3 hrs of my life back, per build.
>
> I wanted to figure out to what extent modern hardware would enhance
> the existing buildbot system.
> Now I know...
odd my laptop will do a full build with tool chain in about an
hour..... its only a core i3 with 6gb and an ssd
>
>
> --
> Dave Täht
> SKYPE: davetaht
> US Tel: 1-239-829-5608
> http://www.bufferbloat.net
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
_______________________________________________
Cerowrt-devel mailing list
Cerowrt-devel@lists.bufferbloat.net
https://lists.bufferbloat.net/listinfo/cerowrt-devel
[-- Attachment #2: Type: text/html, Size: 3613 bytes --]
next prev parent reply other threads:[~2012-04-30 15:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-30 0:15 [Cerowrt-devel] speeding up builds Dave Taht
2012-04-30 1:42 ` Outback Dingo
2012-04-30 1:59 ` Dave Taht
2012-04-30 2:24 ` Dave Taht
2012-04-30 2:42 ` Dave Taht
2012-04-30 2:52 ` Dave Taht
2012-04-30 15:14 ` dpreed [this message]
2012-04-30 15:50 ` [Cerowrt-devel] Pointers on build setup? Dave Taht
2012-04-30 16:50 ` Dave Taht
2012-04-30 23:32 ` Maciej Soltysiak
2012-04-30 23:46 ` Dave Taht
2012-04-30 19:15 ` dpreed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1335798890.08871546@apps.rackspace.com \
--to=dpreed@reed.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=outbackdingo@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox