Received: by 2002:a05:6a10:6744:0:0:0:0 with SMTP id w4csp5866056pxu; Thu, 22 Oct 2020 13:06:31 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxdaveam+ym0QA/bhqkvvmwi/u8rrx6xB7F1jHAEXzQBHFAWT+xs+ORsXMsthdMJ/SF5Wsx X-Received: by 2002:a17:906:c1c3:: with SMTP id bw3mr3841160ejb.126.1603397191716; Thu, 22 Oct 2020 13:06:31 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1603397191; cv=none; d=google.com; s=arc-20160816; b=Jmhs+DJh5EDDurt6lRcKxP8iI59B6IxWMRITVfZEzV2wJ90Q9Co+U1848XWFPy/szI G+QL+M/jbZHx75NSH4lIBuGINnMnU738UEOtNpdHZbyZNlIpj5T/Wkf2Kxn4+eJbxT+R ObYFedhazhjz+82dzQ/Yh2vnsQa78o0RCje2e5OJu/xE9IuALznOde2lfSdPDWe+scXG nyjUxH+m1WIUesT9cFdRNxdDaFJYCLq0dt/zJY4dmWFXbqt/BHCXb2m3yrqWFzAmj1Z6 NT9mWaE+Whd65HANiACYUmGv5MBwjlpq6tkUSBGfyAqyWmCPF3QuEUyBFecc0kr8Sd4k 7sHw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:mime-version:content-transfer-encoding :content-language:accept-language:in-reply-to:references:message-id :date:thread-index:thread-topic:subject:cc:to:from; bh=1S8chdmp6ZJZzwqIyBXEN5xwaoYkZytii9duVU+QplE=; b=Q25nIYP7qJWx6QGriL9Y9gJZOtJoT95DhkMkX3uYrZVblyKEbz291RVR5+chn60DW/ 1pJsF6lxi+6BuHNwatmJq2uAzEyUjJtiVk/EZw8DbkD7JiBonhKP0GlSI316iXZSxbD4 9l/vEySuMstXL/QBD9odSmtui4T14MV2kXl3v9oZpk6thAr1dLR/8iKk9E/0/708Ia1r UGu27Y096XvgDCdHXAjTqsVUG2Ql4IdMJH1KaU5nszW1yJredamLhrOQp+f4e+p8j6W1 FlQqXE5kfZarWYkaIeR06a5EjOjSjqJ3RcVk7shLObUvyjAE1NJiMuVx0Xyx7MR5ua1y ptkg== 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id a12si1682857ejv.55.2020.10.22.13.06.08; Thu, 22 Oct 2020 13:06:31 -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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2896328AbgJVKJm convert rfc822-to-8bit (ORCPT + 99 others); Thu, 22 Oct 2020 06:09:42 -0400 Received: from smtp.h3c.com ([60.191.123.56]:60880 "EHLO h3cspam01-ex.h3c.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2896284AbgJVKJm (ORCPT ); Thu, 22 Oct 2020 06:09:42 -0400 Received: from DAG2EX02-BASE.srv.huawei-3com.com ([10.8.0.65]) by h3cspam01-ex.h3c.com with ESMTPS id 09MA8w1e086358 (version=TLSv1.2 cipher=AES256-GCM-SHA384 bits=256 verify=FAIL); Thu, 22 Oct 2020 18:08:58 +0800 (GMT-8) (envelope-from tian.xianting@h3c.com) Received: from DAG2EX03-BASE.srv.huawei-3com.com (10.8.0.66) by DAG2EX02-BASE.srv.huawei-3com.com (10.8.0.65) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2106.2; Thu, 22 Oct 2020 18:09:01 +0800 Received: from DAG2EX03-BASE.srv.huawei-3com.com ([fe80::5d18:e01c:bbbd:c074]) by DAG2EX03-BASE.srv.huawei-3com.com ([fe80::5d18:e01c:bbbd:c074%7]) with mapi id 15.01.2106.002; Thu, 22 Oct 2020 18:09:01 +0800 From: Tianxianting To: Finn Thain CC: "kashyap.desai@broadcom.com" , "sumit.saxena@broadcom.com" , "shivasharan.srikanteshwara@broadcom.com" , "jejb@linux.ibm.com" , "martin.petersen@oracle.com" , "megaraidlinux.pdl@broadcom.com" , "linux-scsi@vger.kernel.org" , "linux-kernel@vger.kernel.org" Subject: RE: [PATCH] scsi: megaraid_sas: use spin_lock() in hard IRQ Thread-Topic: [PATCH] scsi: megaraid_sas: use spin_lock() in hard IRQ Thread-Index: AQHWp3ceROYVx1Vy20ukToM9T7xND6miYAoAgACPazD//4KKAIAA9PNA Date: Thu, 22 Oct 2020 10:09:00 +0000 Message-ID: <89c5cb05cb844939ae684db0077f675f@h3c.com> References: <20201021064502.35469-1-tian.xianting@h3c.com> <9923f28dd2b34499a17c53e8fa33f1ca@h3c.com> In-Reply-To: Accept-Language: en-US Content-Language: zh-CN X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.99.141.128] x-sender-location: DAG2 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 8BIT MIME-Version: 1.0 X-DNSRBL: X-MAIL: h3cspam01-ex.h3c.com 09MA8w1e086358 Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Yes, thanks I see, If we add this patch, we need to get all cpu arch that support nested interrupts. -----Original Message----- From: Finn Thain [mailto:fthain@telegraphics.com.au] Sent: Thursday, October 22, 2020 11:29 AM To: tianxianting (RD) Cc: kashyap.desai@broadcom.com; sumit.saxena@broadcom.com; shivasharan.srikanteshwara@broadcom.com; jejb@linux.ibm.com; martin.petersen@oracle.com; megaraidlinux.pdl@broadcom.com; linux-scsi@vger.kernel.org; linux-kernel@vger.kernel.org Subject: RE: [PATCH] scsi: megaraid_sas: use spin_lock() in hard IRQ On Thu, 22 Oct 2020, Tianxianting wrote: > Do you mean Megasas raid can be used in m68k arch? m68k is one example of an architecture on which the unstated assumptions in your patch would be invalid. Does this help to clarify what I wrote? If Megasas raid did work on m68k, I'm sure it could potentially benefit from the theoretical performance improvement from your patch. So perhaps you would consider adding support for slower CPUs like m68k.