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 Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id BB47BC41513 for ; Fri, 28 Jul 2023 17:43:18 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230086AbjG1RnR (ORCPT ); Fri, 28 Jul 2023 13:43:17 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:38348 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229527AbjG1RnQ (ORCPT ); Fri, 28 Jul 2023 13:43:16 -0400 Received: from mail-qk1-x730.google.com (mail-qk1-x730.google.com [IPv6:2607:f8b0:4864:20::730]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 9CF4E2D60 for ; Fri, 28 Jul 2023 10:43:15 -0700 (PDT) Received: by mail-qk1-x730.google.com with SMTP id af79cd13be357-76ae0784e0bso110078585a.0 for ; Fri, 28 Jul 2023 10:43:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ziepe.ca; s=google; t=1690566194; x=1691170994; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:from:to:cc:subject:date:message-id:reply-to; bh=Ow1dOB44syTAe0NpfhihQwAompkV9GWSbhBvMRdYVTQ=; b=Ouhhw6u7fqADJY+H1/kFxhxmp2WKsqPyd03Mlv5dUG0DmvPy9caWPbD1AvCkvGYbWe 1kLa0VVzdrCbfWm+rqWk9WsLPe+jFF1Zi7i2Ut2T9rY+MpLK7fh0NEblFrvF2djUssq7 F+fxk1WcuUjH9a9p7T9UXCMqzVOHGcIC/A4wQL3T0r/pJ8cyWQbVwr1cqf5m3WjvYkbL AejUb+m5m7NR5Y3nppmUsxomi56ZmV904voI9terGcp9GZaBXll39GTC6ztqPGWmC2fz b/9J/bwNHZIbQRfvPCKH3fLM1b/mm5+lA1YfVxCKL6EThXIF0Y0GRBFXTxXo2aVYVyqy wapA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1690566194; x=1691170994; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=Ow1dOB44syTAe0NpfhihQwAompkV9GWSbhBvMRdYVTQ=; b=fDtBxzbdffYH776rg5npuSyod+jxC+hWtxO7wfeV5UReaA4iMxwnx8ojazy87NNWAI yjHsiB1ioEKKuluoL3Ldtlhmo5ehNVctDQafc+qrSrqvasjR6R2rw3JUipwXKF1mVw8R fNhJD+Wd2kEQ6eDsM2FQYC4Oaf/umcg6jYGk3fUz6cgoQsgxYgqfRd3ngqL8jgqw/Vo1 Elc9ehMzLmZHpcFeM+Uefi3D3LW1Qm0coCmQ32M1R0zt+c1uy4244uOtAGR9/XhZQASv 9gV62F7Jj6edHIxXz0svu+Cd1Wev6vhIePPUnWkY0reMKht4wjwnifKFu2n2d/kXdQ73 0JJw== X-Gm-Message-State: ABy/qLaKSyruwcjJPQe/J8cZ1Zy/CEmt013D1MdScdnwjwtYXBw0A96+ nVtxgiznzfe6pHE1CQod6lmfBg== X-Google-Smtp-Source: APBJJlEf/l5iXtW9hUonbvLBpNRFVYCeb6kxyBQ2YKwEADRmvKg5uR+6zMAiiWhpmjOswALp7BGS5w== X-Received: by 2002:a05:620a:4082:b0:767:1d7e:ec3d with SMTP id f2-20020a05620a408200b007671d7eec3dmr5043744qko.2.1690566194647; Fri, 28 Jul 2023 10:43:14 -0700 (PDT) Received: from ziepe.ca (hlfxns017vw-142-68-25-194.dhcp-dynamic.fibreop.ns.bellaliant.net. [142.68.25.194]) by smtp.gmail.com with ESMTPSA id f7-20020a05620a15a700b007682634ac20sm1274983qkk.115.2023.07.28.10.43.13 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 28 Jul 2023 10:43:13 -0700 (PDT) Received: from jgg by wakko with local (Exim 4.95) (envelope-from ) id 1qPRUe-001fhT-S8; Fri, 28 Jul 2023 14:43:12 -0300 Date: Fri, 28 Jul 2023 14:43:12 -0300 From: Jason Gunthorpe To: Wei Hu Cc: netdev@vger.kernel.org, linux-hyperv@vger.kernel.org, linux-rdma@vger.kernel.org, longli@microsoft.com, sharmaajay@microsoft.com, leon@kernel.org, kys@microsoft.com, haiyangz@microsoft.com, wei.liu@kernel.org, decui@microsoft.com, davem@davemloft.net, edumazet@google.com, kuba@kernel.org, pabeni@redhat.com, vkuznets@redhat.com, ssengar@linux.microsoft.com, shradhagupta@linux.microsoft.com Subject: Re: [PATCH v4 1/1] RDMA/mana_ib: Add EQ interrupt support to mana ib driver. Message-ID: References: <20230728170749.1888588-1-weh@microsoft.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20230728170749.1888588-1-weh@microsoft.com> Precedence: bulk List-ID: X-Mailing-List: linux-rdma@vger.kernel.org On Fri, Jul 28, 2023 at 05:07:49PM +0000, Wei Hu wrote: > Add EQ interrupt support for mana ib driver. Allocate EQs per ucontext > to receive interrupt. Attach EQ when CQ is created. Call CQ interrupt > handler when completion interrupt happens. EQs are destroyed when > ucontext is deallocated. It seems strange that interrupts would be somehow linked to a ucontext? interrupts are highly limited, you can DOS the entire system if someone abuses this. Generally I expect a properly functioning driver to use one interrupt per CPU core. You should tie the CQ to a shared EQ belong to the core that the CQ wants to have affinity to. Jason