Received: by 2002:a25:ad19:0:0:0:0:0 with SMTP id y25csp11828349ybi; Fri, 26 Jul 2019 00:13:11 -0700 (PDT) X-Google-Smtp-Source: APXvYqzHghTtZWUtYowwNwJ1rl3ObAd3Fzv1lTSxqC9jSv1PxFQj9nxqrVrKAHkTdpCPTOS348RK X-Received: by 2002:a17:902:ff10:: with SMTP id f16mr578372plj.141.1564125191410; Fri, 26 Jul 2019 00:13:11 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1564125191; cv=none; d=google.com; s=arc-20160816; b=cnEu304XeWW6Mp9uoqL4gvipda1V6yu2zRVm+ZpwGbhtgXKJnLUNEnxBtVPsQ2SwIU ppNNejdvOhBq/0xXSB0zVPkFxE+IwpbMBYVubC9doW/UHNMECyp02EgRsVqSeqyLSEHB 36IDLY28j63ksDokoEhj8VfjeMlRsVyb90OY+y5UUitRwdQyT+jXlcZyKRIhaLtz6lak CZnG1E45Nejb6b5WgDrWj1ha/805izTdiN10/RzCYSffAvYb1kw+FCFDBEAmdNuNFEz/ IyVTosS0Xiss6/jpyhrD3OXr7sIHmz3jjhH+veyuhDIQ4SLk/7TDBAj/qSvC8m7qrNsN /2FQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=koV8TZtvh5Af0mlYUbrI4qx/vVEMZE0IQJlFV0qXbtc=; b=Abq6AcCmg0GcFxneQRQCVYCimzd6/5Azt1hqL4arGRNDwXmANk/60skJ9ohT3Ytros VnadW2V0ex9YmsxrHp0Q8CzQ/gzl/4NCfgLkkXENpFXfrmWADSzjejVtNB4DrMLFeX+j QysPaD/htbX5+AASSTNiCnEGWWDRwjkI0cjNdG4O2saxIIExEe+TYXI6CNDeuNoJa2p6 MZAO+GCrT+YpvwJmdg73xC6e7enb5zZtV2LBGESCaR+jIdanGWAC3jCZpFYzLCznJlN7 +y50FePVzRAh6sgO1opnS/bffWQAEXfA7njXKyGlqGRI8XsQkQa/Zh78Z+GVm6XYfZ/+ ARTA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id 73si21300055pld.221.2019.07.26.00.12.54; Fri, 26 Jul 2019 00:13:11 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1725981AbfGZHMW (ORCPT + 99 others); Fri, 26 Jul 2019 03:12:22 -0400 Received: from mx2.suse.de ([195.135.220.15]:43508 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1725864AbfGZHMV (ORCPT ); Fri, 26 Jul 2019 03:12:21 -0400 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.220.254]) by mx1.suse.de (Postfix) with ESMTP id 40D9DB11C; Fri, 26 Jul 2019 07:12:20 +0000 (UTC) Date: Fri, 26 Jul 2019 09:12:19 +0200 From: Michal Hocko To: Pengfei Li Cc: Qian Cai , Andrew Morton , mgorman@techsingularity.net, vbabka@suse.cz, aryabinin@virtuozzo.com, osalvador@suse.de, rostedt@goodmis.org, mingo@redhat.com, pavel.tatashin@microsoft.com, rppt@linux.ibm.com, linux-kernel@vger.kernel.org, linux-mm@kvack.org Subject: Re: [PATCH 00/10] make "order" unsigned int Message-ID: <20190726071219.GC6142@dhcp22.suse.cz> References: <20190725184253.21160-1-lpf.vector@gmail.com> <1564080768.11067.22.camel@lca.pw> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri 26-07-19 07:48:36, Pengfei Li wrote: [...] > For the benefit, "order" may be negative, which is confusing and weird. order = -1 has a special meaning. > There is no good reason not to do this since it can be avoided. "This is good because we can do it" doesn't really sound like a convincing argument to me. I would understand if this reduced a generated code, made an overall code readability much better or something along those lines. Also we only use MAX_ORDER range of values so I could argue that a smaller data type (e.g. short) should be sufficient for this data type. Please note that _any_ change, alebit seemingly small, can introduce a subtle bug. Also each patch requires a man power to review so you have to understand that "just because we can" is not a strong motivation for people to spend their time on such a patch. -- Michal Hocko SUSE Labs