From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-7.1 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS,URIBL_BLOCKED,USER_AGENT_GIT autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 8CC71C433E2 for ; Thu, 10 Sep 2020 21:25:38 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 478AC20758 for ; Thu, 10 Sep 2020 21:25:38 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1599773138; bh=HXDMf0WwGpvkHzJQa+L89oXrj1hJrch64nYIs4kz63I=; h=From:To:Cc:Subject:Date:List-ID:From; b=LUvmyhwnF0nU72eMzRBN3FX4ZrnykoEvpoKvRTL1pcrCfkU9VkVTRROngd5KVrlmr msxwi27YANHAkFgpn4X26GcM9vzMcsG657VBkI2zGGjxOPlUASnMCJU95ZnstJ5qKV O/QnDFZX6JsTqBn+cOes+jtt+9vT/2Lz3zE+1I/g= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726741AbgIJVZd (ORCPT ); Thu, 10 Sep 2020 17:25:33 -0400 Received: from mail.kernel.org ([198.145.29.99]:45978 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1731017AbgIJOXL (ORCPT ); Thu, 10 Sep 2020 10:23:11 -0400 Received: from localhost (unknown [213.57.247.131]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id C939020855; Thu, 10 Sep 2020 14:22:09 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1599747730; bh=HXDMf0WwGpvkHzJQa+L89oXrj1hJrch64nYIs4kz63I=; h=From:To:Cc:Subject:Date:From; b=oJvxd0TtbbC2mbSA1CBlomzUXm6dR1fRinqXKefD/cwkniNKO8F1NvMx/MwJ1Mp8X hoo9q+yKUijIoM5mQroCeOC7BT06sAA5g2XYXJ2WcPySmPXY449HJSXREp4hT4H4Oi Z/Xlud87Qp5gUKjDFRoT2ZmL6cstmLpQi8Wdxzpw= From: Leon Romanovsky To: Doug Ledford , Jason Gunthorpe Cc: Leon Romanovsky , Ariel Elior , Avihai Horon , linux-kernel@vger.kernel.org, linux-rdma@vger.kernel.org, Michal Kalderon Subject: [PATCH rdma-next 0/4] Query GID table API Date: Thu, 10 Sep 2020 17:22:00 +0300 Message-Id: <20200910142204.1309061-1-leon@kernel.org> X-Mailer: git-send-email 2.26.2 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Sender: linux-rdma-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-rdma@vger.kernel.org From: Leon Romanovsky >From Avihai, When an application is not using RDMA CM and if it is using multiple RDMA devices with one or more RoCE ports, finding the right GID table entry is a long process. For example, with two RoCE dual-port devices in a system, when IP failover is used between two RoCE ports, searching a suitable GID entry for a given source IP, matching netdevice of given RoCEv1/v2 type requires iterating over all 4 ports * 256 entry GID table. Even though the best first match GID table for given criteria is used, when the matching entry is on the 4th port, it requires reading 3 ports * 256 entries * 3 files (GID, netdev, type) = 2304 files. The GID table needs to be referred on every QP creation during IP failover on other netdevice of an RDMA device. In an alternative approach, a GID cache may be maintained and updated on GID change event was reported by the kernel. However, it comes with below two limitations: (a) Maintain a thread per application process instance to listen and update the cache. (b) Without the thread, on cache miss event, query the GID table. Even in this approach, if multiple processes are used, a GID cache needs to be maintained on a per-process basis. With a large number of processes, this method doesn't scale. Hence, we introduce this series of patches, which introduces an API to query the complete GID tables of an RDMA device, that returns all valid GID table entries. This is done through single ioctl, eliminating 2304 read, 2304 open and 2304 close system calls to just a total of 2 calls (one for each device). While at it, we also introduce an API to query an individual GID entry over ioctl interface, which provides all GID attributes information. Thanks Avihai Horon (4): RDMA/core: Change rdma_get_gid_attr returned error code RDMA/core: Modify enum ib_gid_type and enum rdma_network_type RDMA/core: Introduce new GID table query API RDMA/uverbs: Expose the new GID query API to user space drivers/infiniband/core/cache.c | 99 +++++++++- drivers/infiniband/core/cma.c | 10 - drivers/infiniband/core/cma_configfs.c | 13 +- drivers/infiniband/core/cma_priv.h | 10 + drivers/infiniband/core/sysfs.c | 3 +- .../infiniband/core/uverbs_std_types_device.c | 180 +++++++++++++++++- drivers/infiniband/core/verbs.c | 2 +- drivers/infiniband/hw/mlx5/cq.c | 2 +- drivers/infiniband/hw/mlx5/main.c | 4 +- drivers/infiniband/hw/qedr/verbs.c | 4 +- include/rdma/ib_cache.h | 5 + include/rdma/ib_verbs.h | 19 +- include/uapi/rdma/ib_user_ioctl_cmds.h | 16 ++ include/uapi/rdma/ib_user_ioctl_verbs.h | 14 ++ 14 files changed, 351 insertions(+), 30 deletions(-) -- 2.26.2