From: Rogier Wolff <R.E.Wolff@BitWizard.nl>
To: linux-kernel@vger.kernel.org
Subject: Fastfail: Device flag?
Date: Fri, 25 Aug 2006 13:06:06 +0200 [thread overview]
Message-ID: <20060825110606.GA20146@bitwizard.nl> (raw)
Hi,
The "md" and "multpath" drivers set a flag called "fastfail". I would
like this to become a flag that could also be set/cleared on a
per-device basis.
I'd rather not spend the time doing the retries, and get an error
immediately. This is an application issue, and I would like to make
that choice myself.....
If there is a chance I won't have to patch kernels until eternity,
I'll write the patch to make this settable from userspace.
The current situation is that the IDE driver thinks it knows which
errors stand a chance of retrying (sectoridnotfound), and which don't
(datacrcerror). This was probably true of some disk in some distant
past.
I'd rather not spend the time doing the retries, and get an error
immediately. This is an application issue....
I was thinking about adding a flag to genhd->flags, and then centrally
in "make_request" set the flag on the specific request if that flag is
set. But if I'm not mistaken, make_request has disappeared (possibly
changed into generic_make_request), and thus this change would have to
be in all "make_request" functions. I'd rather have a single line. So if
anbody has a hint as to where to put it, feel free to point me in the
right direction... ;-)
Comments?
Roger.
--
** R.E.Wolff@BitWizard.nl ** http://www.BitWizard.nl/ ** +31-15-2600998 **
*-- BitWizard writes Linux device drivers for any device you may have! --*
Q: It doesn't work. A: Look buddy, doesn't work is an ambiguous statement.
Does it sit on the couch all day? Is it unemployed? Please be specific!
Define 'it' and what it isn't doing. --------- Adapted from lxrbot FAQ
reply other threads:[~2006-08-25 11:06 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20060825110606.GA20146@bitwizard.nl \
--to=r.e.wolff@bitwizard.nl \
--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.