Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932206AbcJMXiM (ORCPT ); Thu, 13 Oct 2016 19:38:12 -0400 Received: from mail-pf0-f194.google.com ([209.85.192.194]:35287 "EHLO mail-pf0-f194.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756109AbcJMXhq (ORCPT ); Thu, 13 Oct 2016 19:37:46 -0400 Date: Thu, 13 Oct 2016 19:37:22 -0400 From: Tejun Heo To: zijun_hu Cc: akpm@linux-foundation.org, zijun_hu@htc.com, linux-mm@kvack.org, linux-kernel@vger.kernel.org, cl@linux.com Subject: Re: [RFC v2 PATCH] mm/percpu.c: simplify grouping CPU algorithm Message-ID: <20161013233722.GF32534@mtj.duckdns.org> References: <701fa92a-026b-f30b-833c-a5e61eab6549@zoho.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <701fa92a-026b-f30b-833c-a5e61eab6549@zoho.com> User-Agent: Mutt/1.7.0 (2016-08-17) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 651 Lines: 18 Hello, Zijun. On Tue, Oct 11, 2016 at 08:48:45PM +0800, zijun_hu wrote: > compared with the original algorithm theoretically and practically, the > new one educes the same grouping results, besides, it is more effective, > simpler and easier to understand. If the original code wasn't broken and the new code produces the same output, I'd really not mess with this code. There simply is no upside to messing with this code. It's run once during boot and never a noticeable contributor of boot overhead. Maybe the new code is a bit simpler and more efficient but the actual benefit is so small that any risk would outweigh it. Thanks. -- tejun