search for: executionresourceinfo

...ryInfo could be extended with information about various "special" memory regions such as local, shared, etc. memory typical on accelerators. This should tie into the address space mechanism somehow. - TargetExecutionEngineInfo (probably need a better name) will contain a list of ExecutionResourceInfo objects, such as threads, cores, modules, sockets, etc. For example, for a Bulldozer-based system, we would have a set of cores contained in a module, a set of modules contained in a socket and so on. - Each ExecutionResourceInfo object would contain a name to identify the grouping (&quot...

...with information about various >  "special" memory regions such as local, shared, etc. memory typical on >  accelerators.  This should tie into the address space mechanism >  somehow. > > - TargetExecutionEngineInfo (probably need a better name) will contain a >  list of ExecutionResourceInfo objects, such as threads, cores, >  modules, sockets, etc.  For example, for a Bulldozer-based system, we >  would have a set of cores contained in a module, a set of modules >  contained in a socket and so on. > > - Each ExecutionResourceInfo object would contain a name to identify...

...ryInfo could be extended with information about various "special" memory regions such as local, shared, etc. memory typical on accelerators. This should tie into the address space mechanism somehow. - TargetExecutionEngineInfo (probably need a better name) will contain a list of ExecutionResourceInfo objects, such as threads, cores, modules, sockets, etc. For example, for a Bulldozer-based system, we would have a set of cores contained in a module, a set of modules contained in a socket and so on. - Each ExecutionResourceInfo object would contain a name to identify the grouping (&quot...