public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nobuhiro Tachino <ntachino@redhat.com>
To: Andi Kleen <ak@muc.de>, tachino@jp.fujitsu.com
Cc: Takao Indoh <indou.takao@soft.fujitsu.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH]Diskdump - yet another crash dump function
Date: Thu, 27 May 2004 10:45:42 -0400	[thread overview]
Message-ID: <40B5FF16.7030503@redhat.com> (raw)
In-Reply-To: <m3k6yyuhvz.fsf@averell.firstfloor.org>

Andi Kleen wrote:
> I like the concept - it's basically netconsole for SCSI drivers
> and the driver changes are surprisingly simple and clean.
> 
> But it would be better if it coexisted with LKCD so that netdump
> would also work. Can't you make it a low level driver for LKCD? 

Diskdump can exist with netdump without LKCD. Actually in our
system, diskdump and netdump both exist and can be selected by
module loading. When both modules are loaded, diskdump runs first
and if it detects I/O error when writing dump, it falls backs
to netdump.

---
Nobuhiro Tachino
FUJITSU LIMITED

  parent reply	other threads:[~2004-05-27 14:46 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20pwP-55v-5@gated-at.bofh.it>
2004-05-27 13:19 ` [PATCH]Diskdump - yet another crash dump function Andi Kleen
2004-05-27 13:49   ` Christoph Hellwig
2004-05-27 14:02   ` Takao Indoh
2004-05-27 14:45   ` Nobuhiro Tachino [this message]
     [not found] ` <20suK-7C5-11@gated-at.bofh.it>
     [not found]   ` <20tAB-5c-31@gated-at.bofh.it>
     [not found]     ` <20AiB-69m-17@gated-at.bofh.it>
2004-05-27 21:31       ` [3/4] " Andi Kleen
2004-05-28  7:38         ` Ingo Molnar
2004-05-27  9:33 Takao Indoh
2004-06-03 13:10 ` Pavel Machek
2004-06-04  0:44   ` Takao Indoh
2004-06-04  9:33     ` Pavel Machek

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=40B5FF16.7030503@redhat.com \
    --to=ntachino@redhat.com \
    --cc=ak@muc.de \
    --cc=indou.takao@soft.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tachino@jp.fujitsu.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