From: William Lee Irwin III <wli@holomorphy.com>
To: Gene Heskett <gene.heskett@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: New thread RDSL, post-2.6.20 kernels and amanda (tar) miss-fires
Date: Tue, 13 Mar 2007 23:19:22 -0700 [thread overview]
Message-ID: <20070314061922.GR2986@holomorphy.com> (raw)
In-Reply-To: <200703140209.58375.gene.heskett@gmail.com>
> On Wednesday 14 March 2007, William Lee Irwin III wrote:
> >On Tue, Mar 13, 2007 at 11:31:53PM -0400, Gene Heskett wrote:
> >> Now, can someone suggest a patch I can revert that might fix this?
> >> The total number of patches between 2.6.20 and 2.6.21-rc1 will have me
> >> building kernels to bisect this till the middle of June at this rate.
> >
> >4 billion patches could be bisected in 34 boots. Between 2.6.20 and
> >2.6.21-rc1 there are only:
> >
> >$ git rev-list --no-merges v2.6.20..v2.6.21-rc1 |wc -l
> >3118
> >
> >patches, requiring 14 boots. In general ceil(log(n)/log(2))+2 boots.
> >
> >Of course, this is a little optimistic because it assumes no additional
> >breakage occurring at the various bisection points. In any event,
> >assuming (pessimistically) 10 minutes per build, this is 280 minutes or
> >4 hours and 40 minutes of build time. I estimate the process should
> >complete well before Friday of this week, never mind June.
>
On Wed, Mar 14, 2007 at 02:09:57AM -0400, Gene Heskett wrote:
> Chuckle, sorry to disappoint you wli, on that 32 cpu Niagra Con was
> calling 'poor equipment', maybe.
> Even using ccache, its about 15-18 minutes per build, with another 10 to
> edit my build script and construct the kernel tree with the proper
> patches applied. Then a reboot, probably 10 minutes by the time I get
> the nvidia driver installed for the new kernel and get startx'd, then its
> another 2 hours or a bit less for an amanda run to test it.
2 hours, 48 minutes times 13 boots (see the correction post) is 36
hours, 24 minutes. One attempt a day (24 hours instead of 2 hours, 48
minutes) yyields 2 weeks. So you're still done by April, not June.
-- wli
next prev parent reply other threads:[~2007-03-14 6:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-13 8:28 New thread RDSL, post-2.6.20 kernels and amanda (tar) miss-fires Gene Heskett
2007-03-13 18:36 ` Gene Heskett
2007-03-14 3:31 ` Gene Heskett
2007-03-14 5:07 ` William Lee Irwin III
2007-03-14 5:44 ` William Lee Irwin III
2007-03-14 6:09 ` Gene Heskett
2007-03-14 6:19 ` William Lee Irwin III [this message]
2007-03-14 14:54 ` Gene Heskett
2007-03-14 21:49 ` Ray Lee
2007-03-15 3:12 ` Gene Heskett
2007-03-15 4:45 ` Ray Lee
2007-03-15 6:30 ` Gene Heskett
2007-03-15 5:28 ` [OT] " Willy Tarreau
2007-03-15 6:33 ` Gene Heskett
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070314061922.GR2986@holomorphy.com \
--to=wli@holomorphy.com \
--cc=gene.heskett@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).