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=-2.4 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS,USER_AGENT_SANE_1 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 918B3C3A59E for ; Wed, 21 Aug 2019 16:24:06 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 6148A2339E for ; Wed, 21 Aug 2019 16:24:06 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=amazon.com header.i=@amazon.com header.b="GlK0YViH" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727975AbfHUQYF (ORCPT ); Wed, 21 Aug 2019 12:24:05 -0400 Received: from smtp-fw-4101.amazon.com ([72.21.198.25]:33247 "EHLO smtp-fw-4101.amazon.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726857AbfHUQYF (ORCPT ); Wed, 21 Aug 2019 12:24:05 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=amazon.com; i=@amazon.com; q=dns/txt; s=amazon201209; t=1566404645; x=1597940645; h=subject:to:cc:references:from:message-id:date: mime-version:in-reply-to:content-transfer-encoding; bh=FVsd+EOteoJmLhh67CZiySkaPnEpsNPXs/QO2Is2js8=; b=GlK0YViH8xp55c+HhpLMAQIuoeeBpJDjwhviCaa9hTY0iIWSzQxDpRgl I2oczgbK12S4wcY+BdjjwoZm74a4ksCbnUUAXctVZ/h+KFGCYJVCUJgz7 2u/R4p/fnN2FsZ1FjSnl0uT4pLbdD6cPg/uyVqfDxeDPV5L9TML9X7IJB U=; X-IronPort-AV: E=Sophos;i="5.64,412,1559520000"; d="scan'208";a="780521525" Received: from iad6-co-svc-p1-lb1-vlan3.amazon.com (HELO email-inbound-relay-2c-4e7c8266.us-west-2.amazon.com) ([10.124.125.6]) by smtp-border-fw-out-4101.iad4.amazon.com with ESMTP; 21 Aug 2019 16:24:03 +0000 Received: from EX13MTAUEA001.ant.amazon.com (pdx4-ws-svc-p6-lb7-vlan2.pdx.amazon.com [10.170.41.162]) by email-inbound-relay-2c-4e7c8266.us-west-2.amazon.com (Postfix) with ESMTPS id 81F07A24D0; Wed, 21 Aug 2019 16:24:02 +0000 (UTC) Received: from EX13D19EUB003.ant.amazon.com (10.43.166.69) by EX13MTAUEA001.ant.amazon.com (10.43.61.82) with Microsoft SMTP Server (TLS) id 15.0.1367.3; Wed, 21 Aug 2019 16:24:02 +0000 Received: from 8c85908914bf.ant.amazon.com (10.43.162.137) by EX13D19EUB003.ant.amazon.com (10.43.166.69) with Microsoft SMTP Server (TLS) id 15.0.1367.3; Wed, 21 Aug 2019 16:23:57 +0000 Subject: Re: [PATCH v7 rdma-next 0/7] RDMA/qedr: Use the doorbell overflow recovery mechanism for RDMA To: Michal Kalderon CC: "jgg@ziepe.ca" , "dledford@redhat.com" , Ariel Elior , "bmt@zurich.ibm.com" , "sleybo@amazon.com" , "leon@kernel.org" , "linux-rdma@vger.kernel.org" References: <20190820121847.25871-1-michal.kalderon@marvell.com> <87468101-ace2-b718-fd1c-aa6d84554773@amazon.com> <8470780c-7366-dd71-fcb5-372f2c420e8b@amazon.com> From: Gal Pressman Message-ID: <3b7e92ce-d74c-201d-1ed0-31f8fd360d2a@amazon.com> Date: Wed, 21 Aug 2019 19:23:51 +0300 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:60.0) Gecko/20100101 Thunderbird/60.8.0 MIME-Version: 1.0 In-Reply-To: <8470780c-7366-dd71-fcb5-372f2c420e8b@amazon.com> Content-Type: text/plain; charset="utf-8" Content-Language: en-US Content-Transfer-Encoding: 7bit X-Originating-IP: [10.43.162.137] X-ClientProxiedBy: EX13D13UWA004.ant.amazon.com (10.43.160.251) To EX13D19EUB003.ant.amazon.com (10.43.166.69) Sender: linux-rdma-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-rdma@vger.kernel.org On 21/08/2019 15:25, Gal Pressman wrote: > On 21/08/2019 13:41, Gal Pressman wrote: >> On 21/08/2019 13:32, Michal Kalderon wrote: >>> Thanks Gal, >>> >>> I think I found the problem for the issue below, attached a patch that should be applied on top of the series. >>> Please let me know if this fixed the issues you are seeing. >>> In qedr we work with only single pages, and this issue will only occur with multiple pages. >> >> Will apply and rerun, thanks. > > I see different traces now: Well it seems that these traces are there regardless of this series, I will debug separately. Your fix did make the other traces disappear.