From: Scott Wood <swood@redhat.com>
To: Jon Derrick <jonathan.derrick@intel.com>
Cc: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
linux-pci@vger.kernel.org, Paul McKenney <paulmck@kernel.org>,
Bjorn Helgaas <helgaas@kernel.org>
Subject: Re: [PATCH v2] PCI: vmd: Add indirection layer to vmd irq lists
Date: Fri, 21 Jan 2022 18:03:33 -0600 [thread overview]
Message-ID: <YetJ1ZYMVOEkblAM@p1g2> (raw)
In-Reply-To: <1572527333-6212-1-git-send-email-jonathan.derrick@intel.com>
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
next prev parent reply other threads:[~2022-01-22 0:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-31 13:08 [PATCH v2] PCI: vmd: Add indirection layer to vmd irq lists Jon Derrick
2019-10-31 23:11 ` Paul E. McKenney
2019-11-06 16:25 ` Derrick, Jonathan
2020-02-28 11:10 ` Lorenzo Pieralisi
2020-02-28 14:34 ` Paul E. McKenney
2020-02-28 16:36 ` Derrick, Jonathan
2022-01-22 0:03 ` Scott Wood [this message]
2022-01-22 0:22 ` Paul E. McKenney
2022-01-22 0:19 ` Scott Wood
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YetJ1ZYMVOEkblAM@p1g2 \
--to=swood@redhat.com \
--cc=helgaas@kernel.org \
--cc=jonathan.derrick@intel.com \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=paulmck@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).