Received: by 2002:a25:e74b:0:0:0:0:0 with SMTP id e72csp2549338ybh; Fri, 24 Jul 2020 16:12:33 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxkW+xsFZ79tKoRtAEyBjMlrEPcjAKtyNRcka2S3qFhZ5OzwFabIeudLqD7eW/Ycq4/7oQV X-Received: by 2002:a17:906:6b95:: with SMTP id l21mr11674473ejr.32.1595632353521; Fri, 24 Jul 2020 16:12:33 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1595632353; cv=none; d=google.com; s=arc-20160816; b=fadGrrAIb1cxWz49RMaWxu/DnVHBUFHxlqtJjAeUJz4tR28wh2YZGWTPAb0TfctH/k 7O6XCMXRadh2DXTXWie0ibw6cam3NGTWspQKJD3QoJXQZ5Wx2B3yRMqz/R+gO9zbVM1N NIqqO8xWeQolLXtKmIwYwhXjsqXvA6H2mvAvqmhOcxH10mNV16Gk/F0LtQBTlBpcMxB5 oPUy9YmVLCPlf70hXqshfv6j63OPIgD+bezFbXYwZJ0FUu0PH7R/JxwgbCCMSAt0nQAG QRJ218oO1G/IZme2uytChOoKXIfbX8pRATEzXPxbcelWnwGZ2NgPtONOjABgmtCbv0yu iEpw== 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:organization:from:references:cc:to:subject:ironport-sdr :ironport-sdr; bh=Yj0DQ6JY+y5X2ajCKN8V4fhyoT8D8d9bepKK/6dDCAk=; b=ymyfTS6CryvkdHvoyAfqfRAZHIOX2GgycZ9GLGEJHvcwcN+oqdtfb4RbqwdboM3SCM cg2srDh+Ge4QvoyE0VGUc2zQm7BlbSfk7nb0vbGqaTN960QU2nIogEae0mk6GJY1epfr YN+fUuKgYF6dhonU08/A0Lv4vJM1INxRlsD4ZcDxlLSJDin08vrDOlIap4uFQLF/BsyC krg/Cd0TIyurm5Kn2ImeXO8Qpn7TMsjwv0p2p6xRIiameEXvf7DpmhhsQj6J+ozW9//E sKrKCgUWRW7FvhDPo1GZP7tP4UGyzqLaj99I4RX1g6ModdW5HbzsHtwe73HWD7OiZNqC W2Gg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id x23si1328267ejy.571.2020.07.24.16.12.06; Fri, 24 Jul 2020 16:12:33 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726613AbgGXXMA (ORCPT + 99 others); Fri, 24 Jul 2020 19:12:00 -0400 Received: from mga04.intel.com ([192.55.52.120]:19091 "EHLO mga04.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726438AbgGXXMA (ORCPT ); Fri, 24 Jul 2020 19:12:00 -0400 IronPort-SDR: kdQYQhAbn4+6ZIGa9GhlgW6/AM3D4jAfJ3VEG/nWoQpiDwA+6B4iZt3+2K+zWelYOVVXBsZ/Um PItmgp4aXcyw== X-IronPort-AV: E=McAfee;i="6000,8403,9692"; a="148281972" X-IronPort-AV: E=Sophos;i="5.75,392,1589266800"; d="scan'208";a="148281972" X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga006.jf.intel.com ([10.7.209.51]) by fmsmga104.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 24 Jul 2020 16:11:58 -0700 IronPort-SDR: 22DXrr07uwr7NEldS6kJ7cOEQhwSjvWNXbGYq91IJGf27iqRbDgPlUxDncA6tVLjyye/YZ8/qQ 1ioPmEbssuDg== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.75,392,1589266800"; d="scan'208";a="289132518" Received: from jekeller-mobl1.amr.corp.intel.com (HELO [10.254.52.44]) ([10.254.52.44]) by orsmga006.jf.intel.com with ESMTP; 24 Jul 2020 16:11:57 -0700 Subject: Re: [RFC 2/7] ath10k: Add support to process rx packet in thread To: Rakesh Pillai , 'Rajkumar Manoharan' Cc: ath10k@lists.infradead.org, linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org, kvalo@codeaurora.org, johannes@sipsolutions.net, davem@davemloft.net, kuba@kernel.org, netdev@vger.kernel.org, dianders@chromium.org, evgreen@chromium.org, linux-wireless-owner@vger.kernel.org References: <1595351666-28193-1-git-send-email-pillair@codeaurora.org> <1595351666-28193-3-git-send-email-pillair@codeaurora.org> <13573549c277b34d4c87c471ff1a7060@codeaurora.org> <003001d6611e$9afa0cc0$d0ee2640$@codeaurora.org> From: Jacob Keller Organization: Intel Corporation Message-ID: <0d9baad4-fba7-d362-41b7-f0b37446c5ef@intel.com> Date: Fri, 24 Jul 2020 16:11:57 -0700 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.0.1 MIME-Version: 1.0 In-Reply-To: <003001d6611e$9afa0cc0$d0ee2640$@codeaurora.org> Content-Type: text/plain; charset=utf-8 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 On 7/23/2020 11:25 AM, Rakesh Pillai wrote: > Hi Rajkumar, > In linux, the IRQs are directed to the first core which is booted. > I see that all the IRQs are getting routed to CORE0 even if its heavily > loaded. > You should be able to configure the initial IRQ setup so that they don't all go on CPU 0 when you create the IRQ. That obviously doesn't help the case of wanting scheduler to dynamically move the processing around to other CPUs though.