From: Jan Blunck <jblunck@suse.de>
To: Heiko Carstens <heiko.carstens@de.ibm.com>
Cc: Andrew Morton <akpm@osdl.org>, Stefan Weinhuber <wein@de.ibm.com>,
Horst Hummel <horst.hummel@de.ibm.com>,
Christoph Hellwig <hch@lst.de>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] s390: dasd extended error reporting module.
Date: Mon, 6 Feb 2006 12:30:46 +0100 [thread overview]
Message-ID: <20060206113046.GC5564@hasse.suse.de> (raw)
In-Reply-To: <4de7f8a60602060237o5c19d796hb08c237a9b5f3c64@mail.gmail.com>
On Wed, Feb 01, Heiko Carstens wrote:
> From: Stefan Weinhuber <wein@de.ibm.com>
>
> The DASD extended error reporting is a facility that allows to
> get detailed information about certain problems in the DASD I/O.
> This information can be used to implement fail-over applications
> that can recover these problems.
> This is a resubmit of this patch because at first submission it
> didn't get included due to Christoph's ioctl changes.
> Since these aren't in the -mm tree anymore this one should be
> merged now.
Why don't you use the sysfs for this purpose? This new character device
interface seems very odd to me. Why don't you introduce new attributes to the
dasd device for that purpose and make online pollable for failovers?
Or use dm-netlink to report the extended errors via multipath to the user
space.
Regards,
Jan
--
Jan Blunck jblunck@suse.de
SuSE LINUX AG - A Novell company
Maxfeldstr. 5 +49-911-74053-608
D-90409 Nürnberg http://www.suse.de
next prev parent reply other threads:[~2006-02-06 11:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-01 11:56 [PATCH 1/3] s390: dasd extended error reporting module Heiko Carstens
2006-02-04 13:14 ` Christoph Hellwig
[not found] ` <4de7f8a60602060237o5c19d796hb08c237a9b5f3c64@mail.gmail.com>
2006-02-06 11:30 ` Jan Blunck [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-02-06 18:15 Stefan Weinhuber
2006-02-06 18:23 Stefan Weinhuber
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=20060206113046.GC5564@hasse.suse.de \
--to=jblunck@suse.de \
--cc=akpm@osdl.org \
--cc=hch@lst.de \
--cc=heiko.carstens@de.ibm.com \
--cc=horst.hummel@de.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=wein@de.ibm.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