From: Andy Pfiffer <andyp@osdl.org>
To: "Timothy D. Witham" <wookie@osdl.org>
Cc: fastboot@osdl.org, cgl_discussion@osdl.org,
dcl_discussion@osdl.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [dcl_discussion] [ANNOUNCE] OSDL Whitepaper: "Reducing System Reboot Time With Kexec"
Date: 24 Apr 2003 13:55:27 -0700 [thread overview]
Message-ID: <1051217727.2302.10.camel@andyp.pdx.osdl.net> (raw)
In-Reply-To: <1051208689.1787.326.camel@localhost.localdomain>
On Thu, 2003-04-24 at 11:24, Timothy D. Witham wrote:
> So questions and comments are being accepted?
Sure.
> The actual values from the measurements in an appendix
> would be helpful. Including the boot time breakdown
> for the 8 way.
...
On your chart, the time saved column is distracting to
> me as it is extra data.
...
On the relative percentage column
> if it could be kexec/full boot that would make it so that
> I wouldn't have to go back to the text to understand the
> column.
Fair enough. The 8-way measurements aren't currently available because
that specific system has been assigned to another OSDL Lab Associate.
> Also on the kernel boot time, I think that you
> are talking about the kernel init time. So why not call
> it that?
I was hoping to avoid dancing around the semantics and interpretation of
"booted" vs. "initialized". I guess that didn't work as well as I had
hoped. ;^)
>
> On future and ongoing work.
> The crash dump seems to be orthogonal to fast booting. I
> would like to see future and ongoing work that applies to
> fast booting.
>
> Tim
Thanks for taking the time to generate feedback.
Andy
prev parent reply other threads:[~2003-04-24 20:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-24 17:09 [ANNOUNCE] OSDL Whitepaper: "Reducing System Reboot Time With Kexec" Andy Pfiffer
2003-04-24 18:24 ` [dcl_discussion] " Timothy D. Witham
2003-04-24 20:55 ` Andy Pfiffer [this message]
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=1051217727.2302.10.camel@andyp.pdx.osdl.net \
--to=andyp@osdl.org \
--cc=cgl_discussion@osdl.org \
--cc=dcl_discussion@osdl.org \
--cc=fastboot@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wookie@osdl.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).