Received: by 2002:a25:7ec1:0:0:0:0:0 with SMTP id z184csp4492070ybc; Fri, 15 Nov 2019 05:37:53 -0800 (PST) X-Google-Smtp-Source: APXvYqzhEmw5aJFyds0az6Mlk94LDSsIJvOn0H3AVMcxJAzClJMWtWWykhQwfUaeDM0V1QR/Fr27 X-Received: by 2002:a17:906:1395:: with SMTP id f21mr977147ejc.152.1573825073126; Fri, 15 Nov 2019 05:37:53 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1573825073; cv=none; d=google.com; s=arc-20160816; b=hGEh4syL41usg9qfpqBywt28NZbwvaL3vW3Bu0i1nm4WDU4FtMnUn3qRxzAMDQA7xa Fdj9A6I+7ag7Qr/1GeOD/wWE9e/gRl9MDfzJZNkoI5vSP0nSQ64PzER7+uJDqLicQwHS CDaf/tzzZ51kIsRRI2+xd4xEY8AuRIU+GMXWvNbkmpWqzEadgy3RjWa0LFiiOcxAEsM5 OZaM09rAR9AB7gr6GxrWufcV04oxS2K/lNL8lDGhpjzlCDtp1lG1DPR4b6LuslVI3CFI QJHVKmZwkr8pBecbU5SqBta91GumBtZItCZXidJM72O1Oc5UuAo9WpWCggftdEYoLIlo MKrQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=2MShUkLRXgihV+mrZ8b/fMziegbt90LPoeRiCfwuUtk=; b=UKRFN0TeFoK1OFee1oaaPTabhX4vRPmYLiNpfquJrRe+ob9Xb006UnIPih2aLLYfOC UsIQidqhsvv+XTszvQoJSR7X1wClLduL+9ukMR89i4biH1GU9PbtCScHVWkv7SEHKleR DicVZhKPSpZx2TwFwFbPy1Gce4TjXcFVvLEiYVK/rcZ33RnvRgZbdX9wkNhkqmNV6slm tUkRm6NTk3LQZyqE8kq8qJxxlYv56C7AxXpsGNkuvLe2ngy5TGiFoEbmElUm+bTqaJJ0 Gm7gLIDG8Vv+ksUKKyHXB+OF116PnwGkydkjYEMwmKEfZ1LsNu+jhvPxy7GZWgSYa4wE tq5w== 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id y9si4978426eju.209.2019.11.15.05.37.28; Fri, 15 Nov 2019 05:37:53 -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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727528AbfKONg2 (ORCPT + 99 others); Fri, 15 Nov 2019 08:36:28 -0500 Received: from mx2.suse.de ([195.135.220.15]:41646 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1727329AbfKONg2 (ORCPT ); Fri, 15 Nov 2019 08:36:28 -0500 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.220.254]) by mx1.suse.de (Postfix) with ESMTP id 993A2B210; Fri, 15 Nov 2019 13:36:26 +0000 (UTC) Date: Fri, 15 Nov 2019 14:36:25 +0100 From: Michal Hocko To: Shaokun Zhang Cc: linux-kernel@vger.kernel.org, yuqi jin , Andrew Morton , Mike Rapoport , Paul Burton , Michael Ellerman , Anshuman Khandual , netdev@vger.kernel.org Subject: Re: [PATCH v3] lib: optimize cpumask_local_spread() Message-ID: <20191115133625.GD29990@dhcp22.suse.cz> References: <1573091048-10595-1-git-send-email-zhangshaokun@hisilicon.com> <20191108103102.GF15658@dhcp22.suse.cz> <20191112115630.GD2763@dhcp22.suse.cz> <00856999-739f-fd73-eddd-d71e4e94962e@hisilicon.com> <20191114144317.GJ20866@dhcp22.suse.cz> <9af13fea-95a6-30cb-2c0e-770aa649a549@hisilicon.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <9af13fea-95a6-30cb-2c0e-770aa649a549@hisilicon.com> User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri 15-11-19 17:09:13, Shaokun Zhang wrote: [...] > Oh, my mistake, for the previous instance, I don't list all IRQs and > just choose one IRQ from one NUMA node. You can see that the IRQ > number is not consistent :-). > IRQ from 345 to 368 will be bound to CPU cores which are in NUMA node2 > and each IRQ is corresponding to one core. > This is quite confusing then. I would suggest providing all IRQ used for the device with the specific node affinity to see the difference in the setup. -- Michal Hocko SUSE Labs