From: Matthew Wilcox <willy@xxxxxxxxxxxxx> Date: 2020-04-21 19:18:49 To: 1587089010-110083-1-git-send-email-bernard@xxxxxxxx Cc: Christoph Lameter <cl@xxxxxxxxx>,Pekka Enberg <penberg@xxxxxxxxxx>,David Rientjes <rientjes@xxxxxxxxxx>,Joonsoo Kim <iamjoonsoo.kim@xxxxxxx>,Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>,linux-mm@xxxxxxxxx,linux-kernel@xxxxxxxxxxxxxxx,opensource.kernel@xxxxxxxx,Bernard Zhao <bernard@xxxxxxxx> Subject: Re: [PATCH V2] kmalloc_index optimization(code size & runtime stable)>On Mon, Apr 20, 2020 at 08:25:01PM -0700, Bernard Zhao wrote: >> kmalloc_index inline function code size optimization and runtime >> performance stability optimization. After optimization, the function >> kmalloc_index is more stable, the size will never affecte the function`s >> execution efficiency. > >Please stop posting this patch until it's faster *for small sizes*. >As I explained last time you posted it, it's not an optimisation. > >> size time/Per 100 million times >> old fun new fun with optimise >> 8 203777 241934 >> 16 245611 409278 >> 32 236384 408419 >> 64 275499 447732 >> 128 354909 416439 > >^^^^ these are the important cases that need to be fast. > Sure, i just received some kbuild compiler error mails and prompt me to do something? I don`t know why this happened, so i update the patch again. Regards, Bernard
