Apply Lukas' corrections
This commit is contained in:
@@ -24,7 +24,7 @@ Although this can be a complex task, it is possible to implement this in future
|
||||
A less impactful inaccuracy results from the scheduling of the applications threads in the new simplified core models.
|
||||
While an application can spawn a arbitrary number of threads, the platform may not be able to process them all in parallel.
|
||||
Currently, the new trace player does not take this into account and runs all threads in parallel.
|
||||
This, however, could be prevented by recording used processor cores on the initial system and using this information to better match the scheduling.
|
||||
This deviation could be prevented by recording used processor cores on the initial system and using this information to better match the scheduling.
|
||||
|
||||
Another inaccuracy can be caused by the hyperthreading of some of today's processors:
|
||||
While hyperthreading enables the parallel processing of two pipelines in a processor core, those threads do share the same first level cache.
|
||||
|
||||
Reference in New Issue
Block a user