iwarp kernel mode applications are broken with commit f35faa4ba

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Parav,

The following commit f35faa4ba broke iWARP kernel mode applications.

commit f35faa4ba9568138eea1c58abb92e8ef415dce41
Author: Parav Pandit <parav@xxxxxxxxxxxx>
Date:   Sun Apr 1 15:08:20 2018 +0300

    IB/core: Simplify ib_query_gid to always refer to cache

    Currently following inconsistencies exist.
    1. ib_query_gid() returns GID from the software cache for a RoCE port
    and returns GID from the HCA for an IB port.
    This is incorrect because software GID cache is maintained regardless
    of HCA port type.

    2. GID is queries from the HCA via ib_query_gid and updated in the
    software cache for IB link layer. Both of them might not be in sync.

    ULPs such as SRP initiator, SRP target, IPoIB driver have historically
    used ib_query_gid() API to query the GID. However CM used cached version
    during CM processing, When software cache was introduced, this
    inconsitency remained.

    In order to simplify, improve readability and avoid link layer
    specific above inconsistencies, this patch brings following changes.

    1. ib_query_gid() always refers to the cache layer regardless of link
    layer.

    2. cache module who reads the GID entry from HCA and builds the cache,
    directly invokes the HCA provider verb's query_gid() callback function.

    3. ib_query_port() is being called in early stage where GID cache is not
    yet build while reading port immutable property. Therefore it needs to
    read the default GID from the HCA for IB link layer to publish the
    subnet prefix.

    Signed-off-by: Parav Pandit <parav@xxxxxxxxxxxx>
    Signed-off-by: Leon Romanovsky <leonro@xxxxxxxxxxxx>
    Signed-off-by: Jason Gunthorpe <jgg@xxxxxxxxxxxx>


nvmef/iser discovery failed...

[root@bhumthang]# nvme discover -t rdma -a 102.1.1.17
Failed to write to /dev/nvme-fabrics: Invalid argument

[root@bhumthang]# dmesg
[55961.151787] nvme nvme0: rdma_connect failed (-22).
[55961.151971] nvme nvme0: rdma connection establishment failed (-22)

------------
iser
-------------
[54714.834984] iw_cxgb4: Chelsio T4/T5 RDMA Driver - version 0.1
[54714.834987] iw_cxgb4: 0000:04:00.4: Up
[54714.834987] iw_cxgb4: 0000:04:00.4: On-Chip Queues not supported on this device
[54714.855963] ib_srpt MAD registration failed for cxgb4_0-1.
[54714.855972] ib_srpt srpt_add_one(cxgb4_0) failed.
[54715.123119] iw_cxgb4: 0000:07:00.4: Up
[54715.123121] iw_cxgb4: 0000:07:00.4: On-Chip Queues not supported on this device
[54715.125977] cxgb4 0000:07:00.4 enp7s0f4: port module unplugged
[54715.166076] ib_srpt MAD registration failed for cxgb4_1-1.
[54715.166080] ib_srpt srpt_add_one(cxgb4_1) failed.
 [54834.322675] iser: iser_route_handler: failure connecting: -22
[54835.326918] iser: iser_route_handler: failure connecting: -22
[54836.331221] iser: iser_route_handler: failure connecting: -22
[54837.335625] iser: iser_route_handler: failure connecting: -22
[54838.339980] iser: iser_route_handler: failure connecting: -22
[54839.343882] iser: iser_route_handler: failure connecting: -22

Thanks,
Raju.
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Photo]     [Yosemite News]     [Yosemite Photos]     [Linux Kernel]     [Linux SCSI]     [XFree86]

  Powered by Linux