All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Snitzer <snitzer@redhat.com>
To: Muneendra Kumar M <mmandala@Brocade.com>
Cc: "dm-devel@redhat.com" <dm-devel@redhat.com>
Subject: Re: Pushing the multipath state info into the fabric
Date: Thu, 26 Oct 2017 10:35:32 -0400	[thread overview]
Message-ID: <20171026143532.GA5490@redhat.com> (raw)
In-Reply-To: <003dec9a190f45aa91bff7e0010968e1@BRMWP-EXMB12.corp.brocade.com>

On Thu, Oct 26 2017 at  6:18am -0400,
Muneendra Kumar M <mmandala@Brocade.com> wrote:

>    Hi ,
> 
> 
> 
>    We are working on the SAN fabric side to collect and present the multipath
>    status information to the SAN administrators.
> 
>    So, I am looking forward to push the multipath state information to the
>    fabric in the form of CT (Common Transport) frames, by using the libhba
>    APIs.
> 
>    Since the multipath daemon is already keeping track of the multipath
>    device and state info, I feel that it is the correct place to add the code
>    to push the info to the fabric.
> 
>    Please kindly let me know your thoughts on this.

Sounds like you'd probably want to expose APIs that enable you to access
the state you require from multipathd rather than train multipathd to
inject anything into the fabric.

But that is just my initial take.

Mike

  reply	other threads:[~2017-10-26 14:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-26 10:18 Pushing the multipath state info into the fabric Muneendra Kumar M
2017-10-26 14:35 ` Mike Snitzer [this message]
2017-10-30  4:40   ` Muneendra Kumar M
2017-10-30 19:17     ` Mike Snitzer

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=20171026143532.GA5490@redhat.com \
    --to=snitzer@redhat.com \
    --cc=dm-devel@redhat.com \
    --cc=mmandala@Brocade.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.