[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20190228064350.zqq6gl6l4pxlj45x@wunner.de>
Date: Thu, 28 Feb 2019 07:43:50 +0100
From: Lukas Wunner <lukas@...ner.de>
To: Alex_Gagniuc@...lteam.com
Cc: mr.nuke.me@...il.com, helgaas@...nel.org, Austin.Bolen@...l.com,
Shyam.Iyer@...l.com, bhelgaas@...gle.com,
rafael.j.wysocki@...el.com, keith.busch@...el.com,
poza@...eaurora.org, mika.westerberg@...ux.intel.com,
fred@...dlawl.com, linux-kernel@...r.kernel.org,
linux-pci@...r.kernel.org
Subject: Re: [PATCH v2] PCI: pciehp: Report degraded links via link bandwidth
notification
On Wed, Feb 27, 2019 at 08:21:58PM +0000, Alex_Gagniuc@...lteam.com wrote:
> On 2/24/19 8:29 PM, Lukas Wunner wrote:
> > On Fri, Dec 07, 2018 at 12:20:00PM -0600, Alexandru Gagniuc wrote:
> > > Q: Why is this unconditionally compiled in?
> > > A: The symmetrical check in pci probe() is also always compiled in.
> >
> > Hm, it looks like the convention is to provide a separate Kconfig entry
> > for each port service.
>
> Does the convention still make sense in light of the symmetry reason?
I don't know. In the past we had OpenWRT/LEDE folks complain that
the PCI core is hogging too much memory on their space-constrained
Mips routers, so they #ifdef'ed a lot of x86-specific stuff in
quirks.c. In the same vein they could argue that they'd like to
disable unneeded PCIe services. That space argument and possibly
the reduction of attack surface on Linux firewalls is the only
justification I can come up with for a separate Kconfig option for
bandwidth notification.
Thanks,
Lukas
Powered by blists - more mailing lists