From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from m12-15.163.com ([220.181.12.15]:34053 "EHLO m12-15.163.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726554AbeIKOhJ (ORCPT ); Tue, 11 Sep 2018 10:37:09 -0400 Subject: Re: Affinity managed interrupts vs non-managed interrupts To: Christoph Hellwig , Thomas Gleixner Cc: Kashyap Desai , Ming Lei , Sumit Saxena , Ming Lei , Linux Kernel Mailing List , Shivasharan Srikanteshwara , linux-block , Dou Liyang References: <602cee6381b9f435a938bbaf852d07f9@mail.gmail.com> <66256272c020be186becdd7a3f049302@mail.gmail.com> <20180911091354.GA9898@lst.de> From: Dou Liyang Message-ID: <876cd3e2-7519-eab9-7da6-2a672256365e@163.com> Date: Tue, 11 Sep 2018 17:38:19 +0800 MIME-Version: 1.0 In-Reply-To: <20180911091354.GA9898@lst.de> Content-Type: text/plain; charset=gbk; format=flowed Sender: linux-block-owner@vger.kernel.org List-Id: linux-block@vger.kernel.org Hi, At 09/11/2018 05:13 PM, Christoph Hellwig wrote: > On Thu, Sep 06, 2018 at 01:46:46PM +0200, Thomas Gleixner wrote: >> >> I think the right solution for these pre/post vectors is to _NOT_ mark >> them managed and leave them as regular interrupts which can be affinity >> controlled and also can move freely on hotplug. > > Yes, agreed. Marking the pre/post vector as managed was a mistake > (and I don't think it even was intentional, at least on my part). > Got it ! And, I am trying to fix this by: -Don't set affinity for pre/post vectors in irq_create_affinity_masks(). -And do not setup the desc->affinity of pre/post vectors in alloc_msi_entry(). So, the affinity in alloc_descs() will be NULL, and the interrupt won't be marked as IRQD_AFFINITY_MANAGED. Is it OK? and I will show the codes after testing it. Thanks, dou