On Thu, Dec 06, 2018 at 03:09:21PM -0800, Dave Hansen wrote:
> On 12/6/18 2:39 PM, Jerome Glisse wrote:
> > No if the 4 sockets are connect in a ring fashion ie:
> > Socket0 - Socket1
> > | |
> > Socket3 - Socket2
> >
> > Then you have 4 links:
> > link0: socket0 socket1
> > link1: socket1 socket2
> > link3: socket2 socket3
> > link4: socket3 socket0
> >
> > I do not see how their can be an explosion of link directory, worse
> > case is as many link directories as they are bus for a CPU/device/
> > target.
>
> This looks great. But, we don't _have_ this kind of information for any
> system that I know about or any system available in the near future.
We do not have it in any standard way, it is out there in either
device driver database, application data base, special platform
OEM blob burried somewhere in the firmware ...
I want to solve the kernel side of the problem ie how to expose
this to userspace. How the kernel get that information is an
orthogonal problem. For now my intention is to have device driver
register and create the links and bridges that are not enumerated
by standard firmware.
>
> We basically have two different world views:
> 1. The system is described point-to-point. A connects to B @
> 100GB/s. B connects to C at 50GB/s. Thus, C->A should be
> 50GB/s.
> * Less information to convey
> * Potentially less precise if the properties are not perfectly
> additive. If A->B=10ns and B->C=20ns, A->C might be >30ns.
> * Costs must be calculated instead of being explicitly specified
> 2. The system is described endpoint-to-endpoint. A->B @ 100GB/s
> B->C @ 50GB/s, A->C @ 50GB/s.
> * A *lot* more information to convey O(N^2)?
> * Potentially more precise.
> * Costs are explicitly specified, not calculated
>
> These patches are really tied to world view #1. But, the HMAT is really
> tied to world view #1.
^#2
Note that they are also the bridge object in my proposal. So in my
proposal you in #1 you have:
link0: A <-> B with 100GB/s and 10ns latency
link1: B <-> C with 50GB/s and 20ns latency
Now if A can reach C through B then you have bridges (bridge are uni-
directional unlike link that are bi-directional thought that finer
point can be discuss this is what allow any kind of directed graph to
be represented):
bridge2: link0 -> link1
bridge3: link1 -> link0
You can also associated properties to bridge (but it is not mandatory).
So you can say that bridge2 and bridge3 have a latency of 50ns and if
the addition of latency is enough then you do not specificy it in bridge.
It is a rule that a path latency is the sum of its individual link
latency. For bandwidth it is the minimum bandwidth ie what ever is the
bottleneck for the path.
> I know you're not a fan of the HMAT. But it is the firmware reality
> that we are stuck with, until something better shows up. I just don't
> see a way to convert it into what you have described here.
Like i said i am not targetting HMAT system i am targeting system that
rely today on database spread between driver and application. I want to
move that knowledge in driver first so that they can teach the core
kernel and register thing in the core. Providing a standard firmware
way to provide this information is a different problem (they are some
loose standard on non ACPI platform AFAIK).
> I'm starting to think that, no matter if the HMAT or some other approach
> gets adopted, we shouldn't be exposing this level of gunk to userspace
> at *all* since it requires adopting one of the world views.
I do not see this as exclusive. Yes they are HMAT system "soon" to arrive
but we already have the more extended view which is just buried under a
pile of different pieces. I do not see any exclusion between the 2. If
HMAT is good enough for a whole class of system fine but there is also
a whole class of system and users that do not fit in that paradigm hence
my proposal.
Cheers,
Jérôme
