From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
"Rafael J . Wysocki" <rafael.j.wysocki@intel.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Jonathan Cameron <Jonathan.Cameron@huawei.com>,
Lukas Wunner <lukas@wunner.de>,
Chris Chiu <chris.chiu@canonical.com>,
Alexander Motin <mav@ixsystems.com>,
Nicholas Johnson <nicholas.johnson-opensource@outlook.com.au>,
linux-pci@vger.kernel.org
Subject: Re: [PATCH v4 1/2] PCI: Take other bus devices into account when distributing resources
Date: Thu, 5 Jan 2023 15:43:29 +0200 [thread overview]
Message-ID: <Y7bUAaxt6viswdXV@black.fi.intel.com> (raw)
In-Reply-To: <Y7aUa/xVSEXUiovm@black.fi.intel.com>
Hi,
On Thu, Jan 05, 2023 at 11:12:11AM +0200, Mika Westerberg wrote:
> > What happens in a topology like this:
> >
> > 10:00.0 non-hotplug bridge to [bus 20-3f]
> > 10:01.0 non-hotplug bridge to [bus 40]
> > 20:00.0 hotplug bridge
> > 40:00.0 NIC
> >
> > where we're distributing space on "bus" 10, hotplug_bridges == 0 and
> > normal_bridges == 2? Do we give half the extra space to bus 20 and
> > the other half to bus 40, even though we could tell up front that bus
> > 20 is the only place that can actually use any extra space?
>
> Yes we split it into half.
Forgot to reply also that would it make sense here to look at below the
non-hotplug bridges and if we find hotplug bridges, distribute the space
equally between those or something like that?
next prev parent reply other threads:[~2023-01-05 13:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-04 9:16 [PATCH v4 0/2] PCI: distribute resources for root buses Mika Westerberg
2023-01-04 9:16 ` [PATCH v4 1/2] PCI: Take other bus devices into account when distributing resources Mika Westerberg
2023-01-04 22:48 ` Bjorn Helgaas
2023-01-05 9:12 ` Mika Westerberg
2023-01-05 13:43 ` Mika Westerberg [this message]
2023-01-05 17:04 ` Bjorn Helgaas
2023-01-09 11:11 ` Mika Westerberg
2023-01-09 18:27 ` Alexander Motin
2023-01-10 10:07 ` Mika Westerberg
2023-01-09 19:33 ` Alexander Motin
2023-01-10 9:54 ` Mika Westerberg
2023-01-04 9:16 ` [PATCH v4 2/2] PCI: Distribute available resources for root buses too Mika Westerberg
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=Y7bUAaxt6viswdXV@black.fi.intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=bhelgaas@google.com \
--cc=chris.chiu@canonical.com \
--cc=helgaas@kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=mav@ixsystems.com \
--cc=nicholas.johnson-opensource@outlook.com.au \
--cc=rafael.j.wysocki@intel.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.