public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
To: Fabian Holler <fabian.holler-EIkl63zCoXaH+58JC4qpiA@public.gmane.org>
Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: mlx4: IB_EVENT_PATH_MIG not generated on path migration
Date: Wed, 11 Feb 2015 10:38:38 -0700	[thread overview]
Message-ID: <20150211173837.GA20243@obsidianresearch.com> (raw)
In-Reply-To: <20150211092136.GB492-99BIx50xQYGELgA04lAiVw@public.gmane.org>

On Wed, Feb 11, 2015 at 10:21:36AM +0100, Fabian Holler wrote:
> Hello Jason,
> 
> thanks for your answer.
> 
> On Tue, Feb 10, 2015 at 11:00:39AM -0700, Jason Gunthorpe wrote:
> > On Tue, Feb 10, 2015 at 04:56:43PM +0100, Fabian Holler wrote:
> > 
> > > Does anybody have an idea what could be wrong?
> > > Are the PATH_MIG* notifications with mlx4 drivers are working for somebody?
> > 
> > IIRC rdmacm does not forward these events.
> > 
> > There is a lot missing to support APM with RDMA CM, it doesn't do any
> > of the CM state machine operations to coordinate loading alternate
> > paths, for instance.
> 
> Alternate paths can be set directly at the QP.

APM requires a certain amount of synchronization between the local and
remote QP state, particularly if you want it to work more than
once. That is supposed to be done with CMA mads.

> The event handler specified in the struct ib_qp_init_attr * parameter of
> rdma_create_qp() is registered as QP event handler.
> rdma_create_qp() calls ib_create_qp() and sets qp->event_handler to
> ib_qp_init_attr->event_handler.

Okay, right, I was thinking of something else.

We had exactly this working a few months ago for a demo, in kernel
using Lustre and RDMA CM. I checked the patches we made and yes, the
event_handler was being properly called with IB_EVENT_PATH_MIG on
mlx4 and qib cards.

IIRC we may have needed the latest firmware on the mlx side.

Jason
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2015-02-11 17:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-10 15:56 mlx4: IB_EVENT_PATH_MIG not generated on path migration Fabian Holler
     [not found] ` <20150210155643.GB13690-99BIx50xQYGELgA04lAiVw@public.gmane.org>
2015-02-10 18:00   ` Jason Gunthorpe
     [not found]     ` <20150210180039.GD7427-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2015-02-10 21:26       ` Jack Wang
2015-02-11  9:21       ` Fabian Holler
     [not found]         ` <20150211092136.GB492-99BIx50xQYGELgA04lAiVw@public.gmane.org>
2015-02-11 17:38           ` Jason Gunthorpe [this message]
     [not found]             ` <20150211173837.GA20243-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2015-02-12  8:20               ` Fabian Holler
2015-02-16 11:48               ` Fabian Holler

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=20150211173837.GA20243@obsidianresearch.com \
    --to=jgunthorpe-epgobjl8dl3ta4ec/59zmfatqe2ktcn/@public.gmane.org \
    --cc=fabian.holler-EIkl63zCoXaH+58JC4qpiA@public.gmane.org \
    --cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox