Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754919AbbK3U4C (ORCPT ); Mon, 30 Nov 2015 15:56:02 -0500 Received: from g2t4623.austin.hp.com ([15.73.212.78]:48976 "EHLO g2t4623.austin.hp.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754141AbbK3U4A (ORCPT ); Mon, 30 Nov 2015 15:56:00 -0500 Message-ID: <565CB7DD.6010003@hpe.com> Date: Mon, 30 Nov 2015 15:55:57 -0500 From: Waiman Long User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.12) Gecko/20130109 Thunderbird/10.0.12 MIME-Version: 1.0 To: Ling Ma CC: Peter Zijlstra , mingo@redhat.com, linux-kernel@vger.kernel.org, Ling Subject: Re: Improve spinlock performance by moving work to one core References: <563B8E85.6090104@hpe.com> <563CE5A6.8080409@hpe.com> <56560691.8000702@hpe.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 789 Lines: 26 On 11/30/2015 01:17 AM, Ling Ma wrote: > Any comments, the patch is acceptable ? > > Thanks > Ling > > Ling, The core idea of your current patch hasn't changed from your previous patch. My comment is that you should not attempt to sell it as a replacement of the current spinlock mechanism. I just don't see that will happen given the change in API semantics. Also, I think there are probably cases that your patch cannot be applied. So treat it as a separate synchronization mechanism that can be useful in some scenarios. Cheers, Longman -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/