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;
Date:   Tue, 21 Apr 2020 15:57:07 +0000 (UTC)
From:   Christopher Lameter <cl@linux.com>
To:     =?GB2312?B?1dS+/L/8?= <bernard@vivo.com>
cc:     Pekka Enberg <penberg@kernel.org>,
        David Rientjes <rientjes@google.com>,
        Joonsoo Kim <iamjoonsoo.kim@lge.com>,
        Andrew Morton <akpm@linux-foundation.org>, linux-mm@kvack.org,
        linux-kernel@vger.kernel.org, kernel@vivo.com
Subject: Re:Re:Re: [PATCH] kmalloc_index optimization(add kmalloc max size
 check)
In-Reply-To: <AIQAfAC4CMyxqzOp-AElwKpD.3.1587437629306.Hmail.bernard@vivo.com>
Message-ID: <alpine.DEB.2.21.2004211556370.5249@www.lameter.com>
References: <AIQAfAC4CMyxqzOp-AElwKpD.3.1587437629306.Hmail.bernard@vivo.com>
User-Agent: Alpine 2.21 (DEB 202 2017-01-01)
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="531401748-1821483078-1587484627=:5249"
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

--531401748-1821483078-1587484627=:5249
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8BIT

On Tue, 21 Apr 2020, 赵军奎 wrote:

> >You could modify that to check for KMALLOC_MAX_SIZE with some more
> >conditionals but then kmalloc_index) is written so that the compiler gets
> >constant folding right.
> For this point, I am afraid i didn`t catch your idea.
> I am not sure how to modify it....
> Is there some similar code implementation in the kernel？

No. That is where you creativity and ingenuity come in. Otherwise you need
to leave it alone.

--531401748-1821483078-1587484627=:5249--