lkml.org 
[lkml]   [2019]   [Jun]   [19]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH v6 1/4] PCI: Consider alignment of hot-added bridges when distributing available resources
On Wed, Jun 19, 2019 at 01:40:50PM +0000, Nicholas Johnson wrote:
> At least I have found out that git send-email uses terrible
> encoding and adds the patch as an attachment

This must be configurable somehow because many people use git
send-email to send plain-text patches.

> On Sat, Jun 15, 2019 at 02:56:36PM -0500, Bjorn Helgaas wrote:
> > On Wed, May 22, 2019 at 02:30:44PM +0000, Nicholas Johnson wrote:

> > > + * The alignment of this bridge is yet to be considered, hence it must
> > > + * be done now before extending its bridge window. A single bridge
> > > + * might not be able to occupy the whole parent region if the alignment
> > > + * differs - for example, an external GPU at the end of a Thunderbolt
> > > + * daisy chain.
> >
> > The example seems needlessly specific. There isn't anything GPU- or
> > Thunderbolt-specific about this, is there?
> >
> > Bridge windows can be aligned to any multiple of 1MB. But a device
> > BAR must be aligned on its size, so any BAR larger than 1MB should be
> > able to cause this, e.g.,
> >
> > [mem 0x100000-0x3fffff] (bridge A 3MB window)
> > [mem 0x200000-0x3fffff] (bridge B 2MB window)
> > [mem 0x200000-0x3fffff] (device 2MB BAR)
> >
> > Bridge B *could* occupy the the entire 3MB parent region, but it
> > doesn't need to. But you say it "might not be *able* to", so maybe
> > you're thinking of something different?
>
> Under some circumstances it may be possible to occupy the entire region,
> but not always. If the start address of the entire parent region is not
> aligned to the boundary required by the child then the start address of
> the child needs to be bumped up to the next boundary, leaving some
> unused space. In Mika's take on this, he suggested that I just remove
> this comment. I agreed. Does this solve the issue in your mind?

"The alignment of this bridge ..." sentence might be useful. But I
don't think the "A single bridge ..." sentence makes sense. Even if
the parent region isn't sufficiently aligned for descendents of the
child, the child's window *could* start at the parent's start address.
Then some space routed to the child's secondary would be unused.

Maybe when you said the bridge "might not be able to occupy" you meant
that not all the space would be usable by descendants of the child. I
certainly agree with that. I read it as "the child's window might not
be able to consume the whole parent window", which is not true.

> > > - * are on this bus. We will distribute the additional available
> > > + * are on this bus. We will distribute the additional available
> >
> > This whitespace change is pointless and distracting.
>
> Okay. I will read this as "remove it".

Yes, please. We always try to minimize the size of a patch, so it's
worthwhile to read the patch before sending it.

> > Moving this "single bridge" case up makes sense, and I think it could
> > be done by a separate patch preceding this one. Mika, I remember some
> > discussion about this case, but I can't remember if there's some
> > reason you didn't do this initially.
> >
> > The current code is:
> >
> > for_each_pci_bridge(dev, bus)
> > # compute hotplug_bridges, normal_bridges
> >
> > for_each_pci_bridge(dev, bus)
> > # compute remaining_io, etc
> >
> > if (hotplug_bridges + normal_bridges == 1)
> > # handle single bridge case
> >
> > for_each_pci_bridge(dev, bus)
> > # use remaining_io, etc here
> >
> > AFAICT the single bridge case has no dependency on the remaining_io
> > computation.
>
> If you want another patch then please explicitly request it with how you
> want it to be done.

Yes, please make it a separate patch. The advantages are:

- each patch becomes smaller
- each patch is easier to review by itself
- if the series causes a problem, bisection gives a more specific
result
- if we need to revert a patch, we may be able to keep the other
patches

> > > + if (!hotplug_bridges)
> > > return;
> >
> > I like the addition of this early return when there are no hotplug
> > bridges. The following loop is a no-op if there are no hotplug
> > bridges, so it doesn't *fix* anything, but it does make it more
> > obvious that we don't even have to bother with the loop at all, and
> > it makes the "Here hotplug_bridges is always != 0" comment
> > unnecessary.
>
> It fixes the division by zero on the next line of code, but I love to
> shoot two birds with one stone. Moving the div64_ul calls out of the
> loop is the price for the simplification of the loop.
>
> > I think this could be done in a separate patch before this one, too.
> > Anything we can do to simplify these patches is a win because the code
> > is so complicated.
>
> Again, please provide guidance on what exactly you wish to be separated,
> and whether the patch should be before or after the other preliminary
> patch to move the loop up by one.
>
> My initial interpretation is that you want me to add the following in
> Mika's code before his equivalent loop as a two line patch:
>
> if (!hotplug_bridges)
> return;
>
> Should I take out the following comment at the same time?
> "Here hotplug_bridges is always != 0."

Yes, please make this a separate patch that adds the
"if (!hotplug_bridges)" and removes the comment. It doesn't really
matter whether this is before or after the other preliminary patch,
since they are unrelated.

Bjorn

\
 
 \ /
  Last update: 2019-06-19 23:54    [W:0.045 / U:2.724 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site