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 Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 31808C433EF for ; Sat, 22 Jan 2022 00:20:01 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230099AbiAVAUA (ORCPT ); Fri, 21 Jan 2022 19:20:00 -0500 Received: from us-smtp-delivery-124.mimecast.com ([170.10.133.124]:32390 "EHLO us-smtp-delivery-124.mimecast.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230077AbiAVAT7 (ORCPT ); Fri, 21 Jan 2022 19:19:59 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1642810799; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=GMUPM7z8T0P0fxrHUAdQgpd+RxzjamFtu1dSEn4iyiU=; b=arCMFDRQydrqq0BPJPi44jZVigDKD+Z2FzthVS/Ab3m7Tu1Bo3rpqCBsR35ardttrBPUDe ftxpmWUCwkpwWfI5bpUXDz7xoMwpELWEa57Szmc7WNKLrX/Gt9svyAtRT2mrKzHIpj9dsK wQEVK2m+z9vmBqx0kRCry6CJt1Y9aVQ= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-592-z_10NKtlMsiII9O1Mw9HWQ-1; Fri, 21 Jan 2022 19:19:53 -0500 X-MC-Unique: z_10NKtlMsiII9O1Mw9HWQ-1 Received: from smtp.corp.redhat.com (int-mx04.intmail.prod.int.phx2.redhat.com [10.5.11.14]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 580E91083F6D; Sat, 22 Jan 2022 00:19:52 +0000 (UTC) Received: from p1g2 (unknown [10.2.16.224]) by smtp.corp.redhat.com (Postfix) with ESMTPS id A0EFF5F90E; Sat, 22 Jan 2022 00:19:51 +0000 (UTC) Date: Fri, 21 Jan 2022 18:19:49 -0600 From: Scott Wood To: Jonathan Derrick Cc: Lorenzo Pieralisi , linux-pci@vger.kernel.org, Paul McKenney , Bjorn Helgaas Subject: Re: [PATCH v2] PCI: vmd: Add indirection layer to vmd irq lists Message-ID: References: <1572527333-6212-1-git-send-email-jonathan.derrick@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1572527333-6212-1-git-send-email-jonathan.derrick@intel.com> X-Scanned-By: MIMEDefang 2.79 on 10.5.11.14 Precedence: bulk List-ID: X-Mailing-List: linux-pci@vger.kernel.org [resent with Jonathan's current address] On Thu, Oct 31, 2019 at 07:08:53AM -0600, Jon Derrick wrote: > With CONFIG_MAXSMP and CONFIG_PROVE_LOCKING, the size of an srcu_struct can > grow quite large. In one compilation instance it produced a 74KiB data > structure. These are embedded in the vmd_irq_list struct, and a N=64 allocation > can exceed MAX_ORDER, violating reclaim rules. [snip] > --- > Added Paul to make him aware of srcu_struct size with these options > > v1->v2: > Squashed the revert into this commit > changed n=1 kcalloc to kzalloc > > drivers/pci/controller/vmd.c | 47 ++++++++++++++++++++++---------------------- > 1 file changed, 24 insertions(+), 23 deletions(-) Has there been any progress on this? We're seeing a similar problem in a PREEMPT_RT kernel with MAXSMP. -Scott