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 X-Spam-Level: X-Spam-Status: No, score=-5.8 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,NICE_REPLY_A,SPF_HELO_NONE, SPF_PASS,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 1D975C433E4 for ; Fri, 24 Jul 2020 23:12:06 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 00EF520737 for ; Fri, 24 Jul 2020 23:12:05 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726576AbgGXXMA (ORCPT ); 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-wireless-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-wireless@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.