All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Snitzer <snitzer@redhat.com>
To: Muneendra Kumar M <mmandala@Brocade.com>
Cc: Todd Gill <tgill@redhat.com>,
	"dm-devel@redhat.com" <dm-devel@redhat.com>,
	Gris Ge <fge@redhat.com>
Subject: Re: Pushing the multipath state info into the fabric
Date: Mon, 30 Oct 2017 15:17:22 -0400	[thread overview]
Message-ID: <20171030191722.GA13837@redhat.com> (raw)
In-Reply-To: <9a527555006647c6b4586fe78cf6d7b1@BRMWP-EXMB12.corp.brocade.com>

(please don't top-post once someone establishes bottom-posting)

On Mon, Oct 30 2017 at 12:40am -0400,
Muneendra Kumar M <mmandala@Brocade.com> wrote:

> Hi Mike,
> Our intention is to train the multipathd for pushing the  multipath
> info into the fabric using LIBHBA api's. 
> Can we call libhba apis in multipathd to push the info into fabric?

I'll defer to others who maintain and develop multipathd but I'll say
that I think it'd be more logical/correct to _not_ code multipathd to do
this directly.  But rather have your own code that interfaces with
multipathd to get the multipath info and push it where you'd like.

Newer multipathd code that was added to make programmatic access to
multipathd state easier/possible includes:

1) multipathd show maps json
   multipathd show map $map json

2) Use libdmmp (see multipath-tools commit 4335abb36f33f1).  libdmmp
   provides access to the json output via C api.

(thanks to Todd and Gris for providing pointers to these interfaces)

Mike

      reply	other threads:[~2017-10-30 19:17 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
2017-10-30  4:40   ` Muneendra Kumar M
2017-10-30 19:17     ` Mike Snitzer [this message]

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=20171030191722.GA13837@redhat.com \
    --to=snitzer@redhat.com \
    --cc=dm-devel@redhat.com \
    --cc=fge@redhat.com \
    --cc=mmandala@Brocade.com \
    --cc=tgill@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.