Received: by 10.223.185.116 with SMTP id b49csp2067750wrg; Thu, 22 Feb 2018 07:41:08 -0800 (PST) X-Google-Smtp-Source: AH8x227vAtATsMJPG+21WyklDGDdrf1mMY/cfKSadtewPyDNwHUORQPvYd/XMNITxixdDerRsoZD X-Received: by 10.99.165.71 with SMTP id r7mr6091605pgu.60.1519314068804; Thu, 22 Feb 2018 07:41:08 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1519314068; cv=none; d=google.com; s=arc-20160816; b=CaRO4zzH1a0JrcksFDFvomloAaSjw0RQChkviNRqCTD8JBEbEtdrl5jPYGGAYZvOSP QNYTlm8gGiW7a8SR3XdlZQpgHgCsEqGAtmMXebast+D6rOTysCkQKbrobnoz6aolktj+ /sY5PdtMpcf8yI00bvKVtEIRsfJFvjm628YLlenJifOpXzsFAQ1jiKWvhnp5/XmTiI0d ksScfU7xef8OPDAnWqI8NBWfRkxPaXCLv39lnWiHNSMt1D0hCUmep7zy0jOJWCQ21XAV zdepCZEHz9oRfc9w6qu723PYQCXiZTwHF6+7BVhhxGgJInfku/9+W1P5ciXTmo5q1NA8 lHJA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject:arc-authentication-results; bh=E7zxa1cM3Qmj2hxveX0v3hQuQk4tlLNl4SH146kpOaU=; b=IAHcJRN+VOx9PF/y5nxl+D6EBVM2A+t04vIzPCJBlFAF1LNdgm/KctQWVhV7U1cR5w Fl0OTz30NLxYwbX8pf+uX4y2b+fkJtFJ6o9KOjKhPZPXMjby9C6CoxC3G4WJ2f+1Wzl7 g20z15uRSM4Jcj4uFL/60JkHhi5LJK3Fdd8AqsLV/Nx9jhTUqmGep5ZrJABqDeJbqNHp SgQQ3Ph6uhKO14y3r2gSGr3Ms8/F584uZwR80KCNBFVfMjwdA1DfymlMJyqath3VyL8z OIrJX8ppoB2DMTCieFpZLcHjWXzbAQHvUTIYWUxDNTG28fncfme11bY9kOAzFsjJY+oI +mlQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id v24si204491pff.274.2018.02.22.07.40.53; Thu, 22 Feb 2018 07:41:08 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933088AbeBVPjO (ORCPT + 99 others); Thu, 22 Feb 2018 10:39:14 -0500 Received: from mail-wm0-f41.google.com ([74.125.82.41]:53264 "EHLO mail-wm0-f41.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932919AbeBVPjN (ORCPT ); Thu, 22 Feb 2018 10:39:13 -0500 Received: by mail-wm0-f41.google.com with SMTP id t74so4732199wme.3; Thu, 22 Feb 2018 07:39:12 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=E7zxa1cM3Qmj2hxveX0v3hQuQk4tlLNl4SH146kpOaU=; b=XDTBc6Fx7XEHS5RJ/ch7jes3Ux+v37nQyJjCxrwh5mmbd9lCVSeempTgb95jKQyneo 4c9zneZxrIHMo5Ovzwvmbin+yB59ZKq1TPh0IsemYokTDuBlYDqNcbF+eJ8nxeevyH2H mAMElPgbZCtmCcJr+Xvy36v/dIvFL5bw58WccIEnDddj2GrOdMPXpULEpLvWXth/SlMH 5PxJzusuzvHE/GL5X4PqnAXJDtzKqQaxhk74ONLTkD1MHQK2UTt+/dq1ZUFNROzsPSA6 sy/i4JniyrGx9TPBAcdNyP+cHn5F/VxkVu/+4kn2Np0xoFhkW7jcCMLLTZi5if0/Jrlw BEAA== X-Gm-Message-State: APf1xPDgymghG9OIA4aoNQ0AIUpshP0T4RLDtnOBsgUQzxGVAx5caEOL HvLBKa50FIZ8sWdDKeK1M7NL2NuA X-Received: by 10.28.183.195 with SMTP id h186mr5485062wmf.66.1519313951737; Thu, 22 Feb 2018 07:39:11 -0800 (PST) Received: from [192.168.64.168] (bzq-219-42-90.isdn.bezeqint.net. [62.219.42.90]) by smtp.gmail.com with ESMTPSA id s14sm860290wmb.32.2018.02.22.07.39.10 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 22 Feb 2018 07:39:11 -0800 (PST) Subject: Re: [PATCH] RDMA/core: reduce IB_POLL_BATCH constant To: Max Gurtovoy , Chuck Lever , Bart Van Assche Cc: "jgg@ziepe.ca" , "arnd@arndb.de" , "dledford@redhat.com" , "linux-kernel@vger.kernel.org" , "leonro@mellanox.com" , "linux-rdma@vger.kernel.org" References: <20180220205924.2035765-1-arnd@arndb.de> <1519161268.3737.12.camel@wdc.com> <0f90134c-3d40-1d24-711f-e4ab32802bd8@mellanox.com> From: Sagi Grimberg Message-ID: Date: Thu, 22 Feb 2018 17:39:09 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: <0f90134c-3d40-1d24-711f-e4ab32802bd8@mellanox.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org >> The only reason why I added this array on-stack was to allow consumers >> that did not use ib_alloc_cq api to call it, but that seems like a >> wrong decision when thinking it over again (as probably these users >> did not set the wr_cqe correctly). >> >> How about we make ib_process_cq_direct use the cq wc array and add >> a WARN_ON statement (and fail it gracefully) if the caller used this >> API without calling ib_alloc_cq? > > but we tried to avoid cuncurrent access to cq->wc. Not sure its a valid use-case. But if there is a compelling reason to keep it as is, then we can do smaller on-stack array.