From: Bart Van Assche <bart.vanassche@sandisk.com>
To: device-mapper development <dm-devel@redhat.com>,
Hannes Reinecke <hare@suse.de>,
Benjamin Marzinski <bmarzins@redhat.com>
Subject: Re: [LSF/MM ATTEND][LSF/MM TOPIC] Multipath redesign
Date: Thu, 14 Jan 2016 11:09:36 -0800 [thread overview]
Message-ID: <5697F270.3070205@sandisk.com> (raw)
In-Reply-To: <56974D80.2020803@suse.de>
On 01/13/2016 11:25 PM, Hannes Reinecke wrote:
> On 01/13/2016 06:52 PM, Benjamin Marzinski wrote:
>> On Wed, Jan 13, 2016 at 10:10:43AM +0100, Hannes Reinecke wrote:
>>> c) implement block or scsi events whenever a remote port becomes
>>> unavailable. This removes the need of the 'path_checker'
>>> functionality in multipath-tools.
>>
>> I'm not convinced that we will be able to find out when paths come back
>> online in all cases without some sort of actual polling. Again, I'd love
>> this to be simpler, but asking all the types of storage we plan to
>> support to notify us when they are up and down may not be realistic.
>
> Currently we have three main transports: FC, iSCSI, and SAS.
Hello Hannes,
Since several years the Linux SRP initiator driver also has reliable and
efficient H.A. support. The IB spec supports port state change
notifications. But whether or not port state information affects the
path state should be configurable. Several IB users wouldn't like it if
port state information would affect the path state because the time
during which a port is down can be shorter than the time during which an
IB HCA keeps retrying to send a packet.
Bart.
next prev parent reply other threads:[~2016-01-14 19:09 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-13 9:10 [LSF/MM ATTEND][LSF/MM TOPIC] Multipath redesign Hannes Reinecke
2016-01-13 10:50 ` Sagi Grimberg
2016-01-13 10:50 ` Sagi Grimberg
2016-01-13 11:46 ` Hannes Reinecke
2016-01-13 11:46 ` Hannes Reinecke
2016-01-13 15:42 ` Mike Snitzer
2016-01-13 15:42 ` Mike Snitzer
2016-01-13 16:06 ` Sagi Grimberg
2016-01-13 16:06 ` Sagi Grimberg
2016-01-13 16:21 ` Mike Snitzer
2016-01-13 16:21 ` Mike Snitzer
2016-01-13 16:30 ` Sagi Grimberg
2016-01-13 16:30 ` Sagi Grimberg
2016-01-13 16:18 ` Hannes Reinecke
2016-01-13 16:18 ` Hannes Reinecke
2016-01-13 16:54 ` Mike Snitzer
2016-01-13 16:54 ` Mike Snitzer
2016-01-13 11:08 ` [dm-devel] " Alasdair G Kergon
2016-01-13 11:17 ` Hannes Reinecke
2016-01-13 11:25 ` Alasdair G Kergon
2016-01-13 17:52 ` Benjamin Marzinski
2016-01-14 7:25 ` Hannes Reinecke
2016-01-14 19:09 ` Bart Van Assche [this message]
2016-01-15 7:12 ` Hannes Reinecke
2016-01-21 0:38 ` Benjamin Marzinski
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=5697F270.3070205@sandisk.com \
--to=bart.vanassche@sandisk.com \
--cc=bmarzins@redhat.com \
--cc=dm-devel@redhat.com \
--cc=hare@suse.de \
/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.