public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Fabian Holler <fabian.holler-EIkl63zCoXaH+58JC4qpiA@public.gmane.org>
To: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: mlx4: IB_EVENT_PATH_MIG not generated on path migration
Date: Tue, 10 Feb 2015 16:56:43 +0100	[thread overview]
Message-ID: <20150210155643.GB13690@fholler.de> (raw)

Hello,

We are using Linux 3.14.29 with mlx4 drivers and trying to use automatic path
migration for RC connections.
The path migration works, but no IB_EVENT_PATH_MIG* events are generated when
it happens.

APM is configured on machine A by the following code snippet:
        [..]
        err = ib_query_qp(qp, &qp_attr, 0, &init_attr);                                                                                            
        if (err)                                                                                                                                   
                return err;                                                                                                                        
                                                                                                                                                   
        memcpy(&qp_attr.alt_ah_attr, &qp_attr.ah_attr,
               sizeof(qp_attr.alt_ah_attr));
                                                                                                                                                   
        qp_attr.alt_pkey_index          = qp_attr.pkey_index;
        qp_attr.alt_timeout             = qp_attr.timeout;
        qp_attr.path_mig_state          = IB_MIG_REARM;
        qp_attr.alt_ah_attr.dlid        = dlid; /* peer's 2. port dlid */

        err = ib_modify_qp(con->qp, &qp_attr,
                           IB_QP_ALT_PATH | IB_QP_PATH_MIG_STATE);

(I experiment with setting also the ah_attr.port_num and alt_port_num
attributes, they seem to have no effect.)

The QP event handler is registered when calling rdma_create_qp():
        [..]
        init_attr.event_handler = qp_event_handler;
        init_attr.qp_context = con;
        ret = rdma_create_qp(cm_id, pd, &init_attr);


Both machines have MT26428 HCAs.
1 Port of machine A, both ports of machine B are connected to a switch.
We establish the connection to the 1. port of machine B, unplug the
corresponding cable and the path is migrated transparently to the second port
of machine B.
The connection can be used like nothing happens.

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.

We need the event notification to rearm the path migration state machine for
another migration.

Does anybody have an idea what could be wrong?
Are the PATH_MIG* notifications with mlx4 drivers are working for somebody?


thanks

Fabian
--
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

             reply	other threads:[~2015-02-10 15:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-10 15:56 Fabian Holler [this message]
     [not found] ` <20150210155643.GB13690-99BIx50xQYGELgA04lAiVw@public.gmane.org>
2015-02-10 18:00   ` mlx4: IB_EVENT_PATH_MIG not generated on path migration 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
     [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=20150210155643.GB13690@fholler.de \
    --to=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