All of lore.kernel.org
 help / color / mirror / Atom feed
From: Muneendra Kumar M <mmandala@Brocade.com>
To: "dm-devel@redhat.com" <dm-devel@redhat.com>
Subject: deterministic io throughput in multipath
Date: Mon, 19 Dec 2016 11:50:36 +0000	[thread overview]
Message-ID: <1649d4b8538d4b4cb1efacdfe8cf31eb@BRMWP-EXMB12.corp.brocade.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 829 bytes --]

Customers using Linux host (mostly RHEL host) using a SAN network for block storage, complain the Linux multipath stack is not resilient to handle non-deterministic storage network behaviors. This has caused many customer move away to non-linux based servers. The intent of the below patch and the prevailing issues are given below. With the below design we are seeing the Linux multipath stack becoming resilient to such network issues. We hope by getting this patch accepted will help in more Linux server adoption that use SAN network.
I have already sent the design details to the community in a different mail chain and the details are available in the below link.
https://www.redhat.com/archives/dm-devel/2016-December/msg00122.html.
Can you please go through the design and send the comments to us.

Regards,
Muneendra.



[-- Attachment #1.2: Type: text/html, Size: 3573 bytes --]

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



             reply	other threads:[~2016-12-19 11:50 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-19 11:50 Muneendra Kumar M [this message]
2016-12-19 12:09 ` deterministic io throughput in multipath Hannes Reinecke
2016-12-21 16:09 ` Benjamin Marzinski
2016-12-22  5:39   ` Muneendra Kumar M
2016-12-26  9:42   ` Muneendra Kumar M
2017-01-03 17:12     ` Benjamin Marzinski
2017-01-04 13:26       ` Muneendra Kumar M
2017-01-16 11:19       ` Muneendra Kumar M
2017-01-17  1:04         ` Benjamin Marzinski
2017-01-17 10:43           ` Muneendra Kumar M
2017-01-23 11:02           ` Muneendra Kumar M
2017-01-25  9:28             ` Benjamin Marzinski
2017-01-25 11:48               ` Muneendra Kumar M
2017-01-25 13:07                 ` Benjamin Marzinski
2017-02-01 11:58                   ` Muneendra Kumar M
2017-02-02  1:50                     ` Benjamin Marzinski
2017-02-02 11:48                       ` Muneendra Kumar M
2017-02-02 17:39                         ` Benjamin Marzinski
2017-02-02 18:02                           ` Muneendra Kumar M
2017-02-02 18:29                             ` Benjamin Marzinski
2017-02-03 11:43                               ` Muneendra Kumar M

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=1649d4b8538d4b4cb1efacdfe8cf31eb@BRMWP-EXMB12.corp.brocade.com \
    --to=mmandala@brocade.com \
    --cc=dm-devel@redhat.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.