Received: by 2002:ad5:4acb:0:0:0:0:0 with SMTP id n11csp3785948imw; Mon, 18 Jul 2022 14:36:09 -0700 (PDT) X-Google-Smtp-Source: AGRyM1v+aDSew9LgtJHXBN+1aGCjdzjgvXI5Lvmsq0Nep6mlmuyt9FoF+73jNvT5BMfiFOnj6Hyl X-Received: by 2002:a05:6a00:1145:b0:52b:78c:fa26 with SMTP id b5-20020a056a00114500b0052b078cfa26mr29896197pfm.27.1658180169167; Mon, 18 Jul 2022 14:36:09 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1658180169; cv=none; d=google.com; s=arc-20160816; b=eiqbtcxYJE02oMm2KKcuGVNbEK/kzjxWCWURWoCjXsbIsG7UMOwyPJTmrPjcZQEIUp oiMd/wY0DIb7Xdauy3WLLRU+DovZ14dFBWCEURHUQY3jvntvAQIzdUirVxwOzcSiTdLi 2q9QyMI/IxR6opcA9R2XmjFWZpTb5yBHqKYyKWxh2wJ/wFkVBpZ3LR2ka5it+5DMh2P8 Wl2SN8wTMIS4Suos6rRofAxI1e61RRcwYFKanz+FnZfonREz1G0epOjuBEYtDa8PgL1l GRyUNJGvdbAmBGz2FBzQo7mNUGCByylMAX6a8EJ66TdW1jrvpENosuEoySpZ9kzlsBof rm3Q== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date:dkim-signature; bh=l8uo0guaOVRQ3ALjLP6lZE7PWqqqke5+PStc6yRq+YM=; b=Kf58VNgivdWNCUmb6/QCO6NUDTlo5cYMlF5YWDX+1VLAPmel1i6dDOm1z9cXJ00VBY lDTqswbVsr03yKBTbVjrgKR36PDUN+Nn06TLJgtR38xlcX/tmXg+NjBbyrsgT+vbjxZR 1+eb6CgxBOT+KVhKvLGqYT3fGThCGcsVvKSa9tF/jFc+dc9Qnx0374Z0r8rmzTYDGvQO aVnG7eNqA3SJN8BkagtJBNafpxK++nGC3O5YcPJoGueDnazSG3dLf+jq/oCT2R2I+5GX KAzOdmVgesSCr5EA/6/e9wZmD6YsQn7hnFbfPmzLh8tpbrCZh2RbSc8cx+f13YeqdFwM VTfA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@infradead.org header.s=casper.20170209 header.b=pRBtMISt; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id x21-20020a63b215000000b00411bc000639si15930979pge.93.2022.07.18.14.35.51; Mon, 18 Jul 2022 14:36:09 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@infradead.org header.s=casper.20170209 header.b=pRBtMISt; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234531AbiGRVZN (ORCPT + 99 others); Mon, 18 Jul 2022 17:25:13 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:48696 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S234435AbiGRVZK (ORCPT ); Mon, 18 Jul 2022 17:25:10 -0400 Received: from casper.infradead.org (casper.infradead.org [IPv6:2001:8b0:10b:1236::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id CE3A32A24D; Mon, 18 Jul 2022 14:25:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=infradead.org; s=casper.20170209; h=In-Reply-To:Content-Type:MIME-Version: References:Message-ID:Subject:Cc:To:From:Date:Sender:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description; bh=l8uo0guaOVRQ3ALjLP6lZE7PWqqqke5+PStc6yRq+YM=; b=pRBtMIStMfZUuUH0onfRkGgdRy skpq8m+P+0Y/POkkU/7naWbxeZBNp+ogGn9XQIYqZrQOx/Ca5LSOkIeoBJTlWej/r7ekBgrL5Em20 ru4wKhBJeEmNeMLywFKK1rGqFeNuvIzRgO+rHLzDbCH8wWSMXgm5yT+fHDBlqN5RghEs+UiSGCFX6 ZYKZKjTPlpVvsn9m0IAwaFehk8akGxI9uGe3jYURUzZRbUyjX0TYN+NZKkFGjQ2evRzAoXhEpNiAD /LdGou7Frnmy5gfjs/Us9sB2W831kMwl7omfl3RQF9FZJSQFaLpM4uT+rQKCA76Y/1W4w1iOzYBwV ZleDXyqQ==; Received: from j130084.upc-j.chello.nl ([24.132.130.84] helo=worktop.programming.kicks-ass.net) by casper.infradead.org with esmtpsa (Exim 4.94.2 #2 (Red Hat Linux)) id 1oDYEc-00D2rz-Fk; Mon, 18 Jul 2022 21:24:58 +0000 Received: by worktop.programming.kicks-ass.net (Postfix, from userid 1000) id 191139802A7; Mon, 18 Jul 2022 23:24:58 +0200 (CEST) Date: Mon, 18 Jul 2022 23:24:57 +0200 From: Peter Zijlstra To: Tariq Toukan Cc: Tariq Toukan , "David S. Miller" , Saeed Mahameed , Jakub Kicinski , Ingo Molnar , Juri Lelli , Eric Dumazet , Paolo Abeni , netdev@vger.kernel.org, Gal Pressman , Vincent Guittot , linux-kernel@vger.kernel.org Subject: Re: [PATCH net-next V2 2/2] net/mlx5e: Improve remote NUMA preferences used for the IRQ affinity hints Message-ID: References: <20220718124315.16648-1-tariqt@nvidia.com> <20220718124315.16648-3-tariqt@nvidia.com> <2fc99d26-f804-ad34-1fd7-90cfb123b426@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <2fc99d26-f804-ad34-1fd7-90cfb123b426@gmail.com> X-Spam-Status: No, score=-4.4 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_MED,SPF_HELO_NONE, SPF_NONE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Jul 18, 2022 at 10:49:21PM +0300, Tariq Toukan wrote: > > > + first = cpumask_local_spread(0, dev->priv.numa_node); > > > > Arguably you want something like: > > > > first = cpumask_any(cpumask_of_node(dev->priv.numa_node)); > > Any doesn't sound like what I'm looking for, I'm looking for first. > I do care about the order within the node, so it's more like > cpumask_first(cpumask_of_node(dev->priv.numa_node)); > > Do you think this has any advantage over cpumask_local_spread, if used only > during the setup phase of the driver? Only for the poor sod trying to read this code ;-) That is, I had no idea what cpumask_local_spread() does, while cpumask_first() is fairly obvious. > > > @@ -830,8 +887,7 @@ static int comp_irqs_request(struct mlx5_core_dev *dev) > > > ret = -ENOMEM; > > > goto free_irqs; > > > } > > > - for (i = 0; i < ncomp_eqs; i++) > > > - cpus[i] = cpumask_local_spread(i, dev->priv.numa_node); > > > + mlx5_set_eqs_cpus(dev, cpus, ncomp_eqs); > > > > So you change this for mlx5, what about the other users of > > cpumask_local_spread() ? > > I took a look at the different netdev users. > While some users have similar use case to ours (affinity hints), many others > use cpumask_local_spread in other flows (XPS setting, ring allocations, > etc..). > > Moving them to use the newly exposed API needs some deeper dive into their > code, especially due to the possible undesired side-effects. > > I prefer not to include these changes in my series for now, but probably > contribute it in a followup work. Fair enough.