From: Lars Marowsky-Bree <lmb@suse.de>
To: Patrick Mansfield <patmans@us.ibm.com>, linux-kernel@vger.kernel.org
Subject: Re: Accessing the same disk via multiple channels
Date: Mon, 17 Feb 2003 10:52:15 +0100 [thread overview]
Message-ID: <20030217095215.GF9034@marowsky-bree.de> (raw)
In-Reply-To: <20030214153747.A28502@beaverton.ibm.com>
On 2003-02-14T15:37:47,
Patrick Mansfield <patmans@us.ibm.com> said:
> Generic multi-path without the lower levels knowing anything can waste a
> lot of resources. For example, for each extra path to a block device
> (disk) we end up with an extra sd plus associated data structures, and an
> extra scsi_device including multiple request queues.
I think these somehow still need to be exposed so that userspace can do
per-path diagnostics; unless you also want to move this into the kernel space,
which I'm not sure about.
What we really need is better error handling and escalation so that a higher
layer actually has a chance at really well done recovery and retrying.
Sincerely,
Lars Marowsky-Brée <lmb@suse.de>
--
Principal Squirrel
SuSE Labs - Research & Development, SuSE Linux AG
"If anything can go wrong, it will." "Chance favors the prepared (mind)."
-- Capt. Edward A. Murphy -- Louis Pasteur
next prev parent reply other threads:[~2003-02-17 9:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-13 19:49 Accessing the same disk via multiple channels Jurjen Oskam
2003-02-13 22:45 ` Bernd Eckenfels
2003-02-14 10:03 ` Lars Marowsky-Bree
2003-02-14 22:01 ` Tim Pepper
2003-02-14 23:37 ` Patrick Mansfield
2003-02-17 9:52 ` Lars Marowsky-Bree [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-02-14 3:20 steve cameron
2003-02-14 16:27 ` Lars Marowsky-Bree
2003-02-14 18:17 ` Patrick Mansfield
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=20030217095215.GF9034@marowsky-bree.de \
--to=lmb@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=patmans@us.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 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.