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.8 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,MENTIONS_GIT_HOSTING, SPF_HELO_NONE,SPF_PASS 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 D9F0AC4338F for ; Tue, 17 Aug 2021 02:28:30 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id B25A060EE0 for ; Tue, 17 Aug 2021 02:28:30 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S236155AbhHQC3B (ORCPT ); Mon, 16 Aug 2021 22:29:01 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:32996 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233592AbhHQC3B (ORCPT ); Mon, 16 Aug 2021 22:29:01 -0400 Received: from mail-ot1-x32c.google.com (mail-ot1-x32c.google.com [IPv6:2607:f8b0:4864:20::32c]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 54435C061764 for ; Mon, 16 Aug 2021 19:28:29 -0700 (PDT) Received: by mail-ot1-x32c.google.com with SMTP id 61-20020a9d0d430000b02903eabfc221a9so23437547oti.0 for ; Mon, 16 Aug 2021 19:28:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=cGhTf5BGdZ6XOYvkbwEmCCbYycLBUYgH6t0L4rE4Frw=; b=tzrQSih/WSHDnl7K4cBVF3LH2N5w9Xs14/fW5CGzgvE6I4nYQ+xOjQkNR0QC4OTA7T qO3yJvBlexWynGyL2+LywDaDR48HJviN1m2uyerg3YnAXtalI25+WBwbFGDAO/DgZHud H4oUyy+bE9tRDlPTt1eMg2s3REaIyTUAfXUrVs914yBpaiQQfrMNarOyXhu/RPYzn7rl S1zh8ZC6+y5GhOWcA1As4wJZnEOWp/Y0ETCVW3OEfD9BB3FnlSpfyXgqLEd/zXg9Hnt0 OqnQOZSZ2Fhd3aZM9t4UQzk7GrsdINPHc9B6aZ7bh21ZxYPLnBk2ncViI3UBobQbXrNR 56yw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=cGhTf5BGdZ6XOYvkbwEmCCbYycLBUYgH6t0L4rE4Frw=; b=XAOlR17Ft3NWTgo0yJjQTBa0F4z6cq4xWGqk3O/QVJOCQsKFeyYU773NOEF3whnlRI y7vCMFKdDW/hLLIuDJH8lTxQkqArU/b8VZvsKOxITTZ+6xCwrOmjPgju9P2hg3qkb6t0 O3+zZLduLLlH3EjCkHNSr6dUlRMlZjkTkFQFZM6H9/xkRR8DZnWOiGLX1g753q72lcD9 8HUYcdYYc0I7XjoRxJtCkHhIRFU6xBOzHGLsA27XhqzRN6vb5ucLEKQ/D0IVKUlA57bQ oIvIU7JIf5mF2qColUeLTYcb9vXFws3UJoH9o2ly2ldKxBunGcXTpkYMOypIFZ7jKBlp hhtw== X-Gm-Message-State: AOAM531LhMDiz1Q7+neXQy18tA3CX596Z0GzrRYgosTm/2zr4mUIJmxc PDNHFJJlFZQAYUoPgS17E2BNPy1lbdb1vMYwWNE= X-Google-Smtp-Source: ABdhPJwoITNq4ZkfjYxotGVFJCre4nzkoUk1H3abE7EW/kDhHbo5+DWJ0OFEfZkkO39PMBOJ+bClHOsjbJlhVCU0AZc= X-Received: by 2002:a9d:6b17:: with SMTP id g23mr854780otp.278.1629167308769; Mon, 16 Aug 2021 19:28:28 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Zhu Yanjun Date: Tue, 17 Aug 2021 10:28:16 +0800 Message-ID: Subject: Re: RXE status in the upstream rping using rxe To: Olga Kornievskaia Cc: Leon Romanovsky , Bob Pearson , Jason Gunthorpe , linux-rdma Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-rdma@vger.kernel.org On Fri, Aug 6, 2021 at 10:37 AM Olga Kornievskaia wrote: > > On Wed, Aug 4, 2021 at 5:05 AM Zhu Yanjun wrote: > > > > On Wed, Aug 4, 2021 at 1:41 PM Leon Romanovsky wrote: > > > > > > On Wed, Aug 04, 2021 at 09:09:41AM +0800, Zhu Yanjun wrote: > > > > On Wed, Aug 4, 2021 at 9:01 AM Zhu Yanjun wrote: > > > > > > > > > > On Wed, Aug 4, 2021 at 2:07 AM Leon Romanovsky wrote: > > > > > > > > > > > > Hi, > > > > > > > > > > > > Can you please help me to understand the RXE status in the upstream? > > > > > > > > > > > > Does we still have crashes/interop issues/e.t.c? > > > > > > > > > > I made some developments with the RXE in the upstream, from my usage > > > > > with latest RXE, > > > > > I found the following: > > > > > > > > > > 1. rdma-core can not work well with latest RDMA git; > > > > > > > > The latest RDMA git is > > > > https://git.kernel.org/pub/scm/linux/kernel/git/rdma/rdma.git > > > > > > "Latest" is a relative term, what SHA did you test? > > > Let's focus on fixing RXE before we will continue with new features. > > > > Thanks a lot. I agree with you. > > I believe simple rping still doesn't work linux-to-linux. The last > working version (of rping in rxe) was 5.13 I think. I have posted a > number of crashes rping encounters (gotta get that working before I > can even try NFSoRDMA). The following are my tests. 1. Modprobe rdma_rxe 2. Modprobe -v -r rdma_rxe 3. Rdma link add rxe 4. Rdma link del rxe 5. Latest rdma-core && latest kernel upstream; 6. Latest kernel < ------rping---- > 5.10.y stable 7. Latest kernel < ------rping---- > 5.11.y stable 8. Latest kernel < ------rping---- > 5.12.y stable 9. Latest kernel < ------rping---- > 5.13.y stable It seems that the latest kernel upstream (5.14-rc6) can rping other stable kernels. Can you make tests again? Zhu Yanjun > > Thank you for working on the code. > > We (NFS community) do test NFSoRDMA every git pull using rxe and siw > but lately have been encountering problems. > > > rdma-core: > > 313509f8 (HEAD -> master, origin/master, origin/HEAD) Merge pull > > request #1038 from selvintxavier/master > > 2d3dc48b Merge pull request #1039 from amzn/pyverbs-mac-fix-pr > > 327d45e0 tests: Add missing MAC element to args list > > 66aba73d bnxt_re/lib: Move hardware queue to 16B aligned indices > > 8754fb51 bnxt_re/lib: Use separate indices for shadow queue > > be4d8abf bnxt_re/lib: add a function to initialize software queue > > > > kernel rdma: > > 0050a57638ca (HEAD -> for-next, origin/for-next, origin/HEAD) > > RDMA/qedr: Improve error logs for rdma_alloc_tid error return > > 090473004b02 RDMA/qed: Use accurate error num in qed_cxt_dynamic_ilt_alloc > > 991c4274dc17 RDMA/hfi1: Fix typo in comments > > 8d7e415d5561 docs: Fix infiniband uverbs minor number > > bbafcbc2b1c9 RDMA/iwpm: Rely on the rdma_nl_[un]register() to ensure > > that requests are valid > > bdb0e4e3ff19 RDMA/iwpm: Remove not-needed reference counting > > e677b72a0647 RDMA/iwcm: Release resources if iw_cm module initialization fails > > a0293eb24936 RDMA/hfi1: Convert from atomic_t to refcount_t on > > hfi1_devdata->user_refcount > > > > with the above kernel and rdma-core, the following messages will appear. > > " > > [ 54.214608] rdma_rxe: loaded > > [ 54.217089] infiniband rxe0: set active > > [ 54.217101] infiniband rxe0: added enp0s8 > > [ 167.623200] rdma_rxe: cqe(32768) > max_cqe(32767) > > [ 167.645590] rdma_rxe: cqe(1) < current # elements in queue (6) > > [ 167.733297] rdma_rxe: cqe(32768) > max_cqe(32767) > > [ 169.074755] rdma_rxe: check_rkey: no MW matches rkey 0x1000247 > > [ 169.074796] rdma_rxe: qp#27 moved to error state > > [ 169.138851] rdma_rxe: check_rkey: no MW matches rkey 0x10005de > > [ 169.138889] rdma_rxe: qp#30 moved to error state > > [ 169.160565] rdma_rxe: check_rkey: no MW matches rkey 0x10006f7 > > [ 169.160601] rdma_rxe: qp#31 moved to error state > > [ 169.182132] rdma_rxe: check_rkey: no MW matches rkey 0x1000782 > > [ 169.182170] rdma_rxe: qp#32 moved to error state > > [ 169.667803] rdma_rxe: check_rkey: no MR matches rkey 0x18d8 > > [ 169.667850] rdma_rxe: qp#39 moved to error state > > [ 198.872649] rdma_rxe: cqe(32768) > max_cqe(32767) > > [ 198.894829] rdma_rxe: cqe(1) < current # elements in queue (6) > > [ 198.981839] rdma_rxe: cqe(32768) > max_cqe(32767) > > [ 200.332031] rdma_rxe: check_rkey: no MW matches rkey 0x1000887 > > [ 200.332086] rdma_rxe: qp#58 moved to error state > > [ 200.396476] rdma_rxe: check_rkey: no MW matches rkey 0x1000b0d > > [ 200.396514] rdma_rxe: qp#61 moved to error state > > [ 200.417919] rdma_rxe: check_rkey: no MW matches rkey 0x1000c40 > > [ 200.417956] rdma_rxe: qp#62 moved to error state > > [ 200.439616] rdma_rxe: check_rkey: no MW matches rkey 0x1000d24 > > [ 200.439654] rdma_rxe: qp#63 moved to error state > > [ 200.933104] rdma_rxe: check_rkey: no MR matches rkey 0x37d8 > > [ 200.933153] rdma_rxe: qp#70 moved to error state > > [ 206.880305] rdma_rxe: cqe(32768) > max_cqe(32767) > > [ 206.904030] rdma_rxe: cqe(1) < current # elements in queue (6) > > [ 206.991494] rdma_rxe: cqe(32768) > max_cqe(32767) > > [ 208.359987] rdma_rxe: check_rkey: no MW matches rkey 0x1000e4d > > [ 208.360028] rdma_rxe: qp#89 moved to error state > > [ 208.425637] rdma_rxe: check_rkey: no MW matches rkey 0x1001136 > > [ 208.425675] rdma_rxe: qp#92 moved to error state > > [ 208.447333] rdma_rxe: check_rkey: no MW matches rkey 0x10012d8 > > [ 208.447370] rdma_rxe: qp#93 moved to error state > > [ 208.469511] rdma_rxe: check_rkey: no MW matches rkey 0x100137a > > [ 208.469550] rdma_rxe: qp#94 moved to error state > > [ 208.956691] rdma_rxe: check_rkey: no MR matches rkey 0x5670 > > [ 208.956731] rdma_rxe: qp#100 moved to error state > > [ 216.879703] rdma_rxe: cqe(32768) > max_cqe(32767) > > [ 216.902199] rdma_rxe: cqe(1) < current # elements in queue (6) > > [ 216.989264] rdma_rxe: cqe(32768) > max_cqe(32767) > > [ 218.363765] rdma_rxe: check_rkey: no MW matches rkey 0x10014d6 > > [ 218.363808] rdma_rxe: qp#119 moved to error state > > [ 218.429474] rdma_rxe: check_rkey: no MW matches rkey 0x10017e4 > > [ 218.429513] rdma_rxe: qp#122 moved to error state > > [ 218.451443] rdma_rxe: check_rkey: no MW matches rkey 0x1001895 > > [ 218.451481] rdma_rxe: qp#123 moved to error state > > [ 218.473869] rdma_rxe: check_rkey: no MW matches rkey 0x1001910 > > [ 218.473908] rdma_rxe: qp#124 moved to error state > > [ 218.963602] rdma_rxe: check_rkey: no MR matches rkey 0x757b > > [ 218.963641] rdma_rxe: qp#130 moved to error state > > [ 233.855140] rdma_rxe: cqe(32768) > max_cqe(32767) > > [ 233.877202] rdma_rxe: cqe(1) < current # elements in queue (6) > > [ 233.963952] rdma_rxe: cqe(32768) > max_cqe(32767) > > [ 235.305274] rdma_rxe: check_rkey: no MW matches rkey 0x1001ac2 > > [ 235.305319] rdma_rxe: qp#149 moved to error state > > [ 235.368800] rdma_rxe: check_rkey: no MW matches rkey 0x1001db8 > > [ 235.368838] rdma_rxe: qp#152 moved to error state > > [ 235.390155] rdma_rxe: check_rkey: no MW matches rkey 0x1001e4d > > [ 235.390192] rdma_rxe: qp#153 moved to error state > > [ 235.411336] rdma_rxe: check_rkey: no MW matches rkey 0x1001f4c > > [ 235.411374] rdma_rxe: qp#154 moved to error state > > [ 235.895784] rdma_rxe: check_rkey: no MR matches rkey 0x9482 > > [ 235.895828] rdma_rxe: qp#161 moved to error state > > " > > Not sure if they are problems. > > IMO, we should make further investigations. > > > > Thanks > > Zhu Yanjun > > > > > > Thanks