From: Itsuro Oda <oda@valinux.co.jp>
To: Robin Holt <holt@sgi.com>
Cc: linux-kernel@vger.kernel.org, fastboot@osdl.org, oda@valinux.co.jp
Subject: Re: Yet another crash dump tool
Date: Mon, 18 Oct 2004 12:33:19 +0900 [thread overview]
Message-ID: <20041018112919.26F7.ODA@valinux.co.jp> (raw)
In-Reply-To: <20041015130602.GA32020@lnx-holt.americas.sgi.com>
Hi,
> Can
> you add a feature to only dump kernel pages, kernel pages +
> page/buffer cache, or all of memory? If not, this is a step
yes. actually the mini kernel dump has an interface from the
operational kernel to the mini kernel that contains "what pfn
should be dumped".
It takes 2-3 minutes to dump 8GB memory (our typical customer).
So it is relative low priority to support selecting dump pages,
but I remind it.
> backwards in dumping. We have seen RFPs from some potential
> customers for as much as 16PB of memory. I am not sure that
> anybody builds hardware that scales to that level, but it
> certainly shows you a problem.
Maybe we should develop another fault isolation method on such
system.
> classified data. They require assurances that the minimal amount
> of their unclassified data is being sent outside their control to
> reduce the chance that someone can infer their methods.
It is an important point to provide the fault analysis service.
We are considering that point. It is rather an operational problem
than technical problem. We are planning some cryptographic mechanism.
Thank you.
--
Itsuro ODA <oda@valinux.co.jp>
next prev parent reply other threads:[~2004-10-18 3:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-13 23:05 Itsuro Oda
2004-10-14 11:29 ` Robin Holt
2004-10-15 0:08 ` Itsuro Oda
2004-10-15 13:06 ` Robin Holt
2004-10-18 3:33 ` Itsuro Oda [this message]
2004-12-23 11:59 ` [Fastboot] " Eric W. Biederman
2005-01-06 1:54 ` Itsuro Oda
2005-01-06 5:25 ` Eric W. Biederman
2005-01-06 23:55 ` Itsuro Oda
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=20041018112919.26F7.ODA@valinux.co.jp \
--to=oda@valinux.co.jp \
--cc=fastboot@osdl.org \
--cc=holt@sgi.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
all inboxes | Powered by JetHome®