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: Tue, 10 Feb 2015 11:00:39 -0700	[thread overview]
Message-ID: <20150210180039.GD7427@obsidianresearch.com> (raw)
In-Reply-To: <20150210155643.GB13690-99BIx50xQYGELgA04lAiVw@public.gmane.org>

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.

> As soon as the migration happens I expect that a IB_EVENT_PATH_MIG* is
> generated on the QP event handler, but I don't receive any QP events.

qp_event_handler is a RDMA CM event handler, it handles
RDMA_CM_EVENT_* and there is no RDMA_CM_EVENT_PATH_MIGRATED.

You'd need to listen to the verbs level events directly, I don't
recall if this is possible with RDMA CM or not, sorry.

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-10 18:00 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 [this message]
     [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
     [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=20150210180039.GD7427@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