From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-5.3 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id BE507C433DB for ; Wed, 10 Mar 2021 07:00:29 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 6EDCA64FE8 for ; Wed, 10 Mar 2021 07:00:29 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229810AbhCJG76 (ORCPT ); Wed, 10 Mar 2021 01:59:58 -0500 Received: from vmi485042.contaboserver.net ([161.97.139.209]:54908 "EHLO gentwo.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229441AbhCJG7x (ORCPT ); Wed, 10 Mar 2021 01:59:53 -0500 Received: by gentwo.de (Postfix, from userid 1001) id D6410B005CF; Wed, 10 Mar 2021 07:59:51 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by gentwo.de (Postfix) with ESMTP id D3C5EB0058D; Wed, 10 Mar 2021 07:59:51 +0100 (CET) Date: Wed, 10 Mar 2021 07:59:51 +0100 (CET) From: Christoph Lameter To: Linus Torvalds cc: kernel test robot , Jann Horn , David Rientjes , Joonsoo Kim , Pekka Enberg , Andrew Morton , LKML , lkp@lists.01.org, kernel test robot , "Huang, Ying" , Feng Tang , zhengjun.xing@intel.com Subject: Re: [mm, slub] 8ff60eb052: stress-ng.rawpkt.ops_per_sec -47.9% regression In-Reply-To: Message-ID: References: <20210301080404.GF12822@xsang-OptiPlex-9020> User-Agent: Alpine 2.22 (DEB 394 2020-01-19) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, 9 Mar 2021, Linus Torvalds wrote: > So when you wrote: > > However, the current code accidentally stops looking at the partial list > completely in that case. Especially on kernels without CONFIG_NUMA set, > this means that get_partial() fails and new_slab_objects() falls back to > new_slab(), allocating new pages. This could lead to an unnecessary > increase in memory fragmentation. > > it really looks like this might well have been very intentional > indeed. Or at least very beneficial for _some_ loads. > > Comments? Yes the thought was that adding an additional page when contention is there on the page objects will increase possible concurrency while avoiding locks and increase the ability to allocate / free concurrently from a multitude of objects.