From: Ingo Molnar <mingo@elte.hu>
To: Andi Kleen <ak@muc.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [3/4] [PATCH]Diskdump - yet another crash dump function
Date: Fri, 28 May 2004 09:38:14 +0200 [thread overview]
Message-ID: <20040528073814.GA11289@elte.hu> (raw)
In-Reply-To: <m34qq1v9p6.fsf@averell.firstfloor.org>
* Andi Kleen <ak@muc.de> wrote:
> > yeah, this is arguably the biggest (and i think only) conceptual item
> > that needs to be solved before this can be integrated.
>
> I would think netdump is more important than this though (so if
> anything should be integrated i would start with netdump)
i think both are important. Dumping to disks is a frequent customer
request, and not all setups can dump to a network, for performance,
security or reliability reasons. The diskdump format is the same as the
netdump format, and can be handled/analyzed by the same userspace tools,
so in this sense it's an extension of netdump to another class of IO
devices.
> > it would also be easier to enable diskdump in a driver if this was
> > handled in add_timer()/del_timer()/mod_timer()/tasklet_schedule().
>
> I don't think it's a good idea to add this to these fast paths. Timers
> are critical for lots of things, tasklet_schedule too.
>
> How about a standard wrapper that does the check and everybody who may
> need that uses the wrappers ?
that's what the patch does currently. It needs to be decided one way or
another. But it doesnt make alot of sense to introduce another vector of
APIs for this purpose - it would need possibly wide driver changes for
no good reason.
Ingo
next prev parent reply other threads:[~2004-05-28 7:37 UTC|newest]
Thread overview: 34+ 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
[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 [this message]
2004-05-27 9:33 Takao Indoh
2004-05-27 12:39 ` [3/4] " Takao Indoh
2004-05-27 13:51 ` Christoph Hellwig
2004-05-27 21:04 ` Ingo Molnar
2004-06-17 11:34 ` Takao Indoh
2004-06-17 12:00 ` Christoph Hellwig
2004-06-17 12:45 ` Takao Indoh
2004-06-17 12:13 ` Ingo Molnar
2004-06-17 12:18 ` Christoph Hellwig
2004-06-17 12:32 ` Ingo Molnar
2004-06-17 14:56 ` Jeff Moyer
2004-06-17 15:45 ` Nobuhiro Tachino
2004-06-17 13:04 ` Takao Indoh
2004-06-17 13:10 ` Ingo Molnar
2004-06-17 13:11 ` Ingo Molnar
2004-06-17 13:15 ` Ingo Molnar
2004-06-17 14:00 ` Takao Indoh
2004-06-17 14:45 ` Nobuhiro Tachino
2004-06-17 14:53 ` Takao Indoh
2004-06-18 12:02 ` Takao Indoh
2004-06-21 20:40 ` Nobuhiro Tachino
2004-06-22 10:19 ` Ingo Molnar
2004-06-23 12:11 ` Takao Indoh
2004-06-23 13:00 ` Takao Indoh
2004-06-21 5:46 ` Keith Owens
2004-06-21 6:25 ` Takao Indoh
2004-06-22 4:21 ` Rob Landley
2004-06-22 7:56 ` Ingo Molnar
2004-05-28 9:38 ` Takao Indoh
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=20040528073814.GA11289@elte.hu \
--to=mingo@elte.hu \
--cc=ak@muc.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.