On 11/17/2015 05:17 PM, Nathan Zimmer wrote:
When running the SPECint_rate gcc on some very large boxes it was noticed
that the system was spending lots of time in mpol_shared_policy_lookup.
The gamess benchmark can also show it and is what I mostly used to chase
down the issue since the setup
On 11/17/2015 05:17 PM, Nathan Zimmer wrote:
When running the SPECint_rate gcc on some very large boxes it was noticed
that the system was spending lots of time in mpol_shared_policy_lookup.
The gamess benchmark can also show it and is what I mostly used to chase
down the issue since the setup
On 11/18/2015 09:05 PM, Nathan Zimmer wrote:
On 11/18/2015 07:50 AM, Vlastimil Babka wrote:
At first glance it seems that RCU would be a good fit here and achieve even
better lookup scalability, have you considered it?
Originally that was my plan but when I saw how good the results were
On 11/18/2015 09:05 PM, Nathan Zimmer wrote:
On 11/18/2015 07:50 AM, Vlastimil Babka wrote:
At first glance it seems that RCU would be a good fit here and achieve even
better lookup scalability, have you considered it?
Originally that was my plan but when I saw how good the results were
On 11/17/2015 05:17 PM, Nathan Zimmer wrote:
> When running the SPECint_rate gcc on some very large boxes it was noticed
> that the system was spending lots of time in mpol_shared_policy_lookup.
> The gamess benchmark can also show it and is what I mostly used to chase
> down the issue since the
On 11/17/2015 05:17 PM, Nathan Zimmer wrote:
> When running the SPECint_rate gcc on some very large boxes it was noticed
> that the system was spending lots of time in mpol_shared_policy_lookup.
> The gamess benchmark can also show it and is what I mostly used to chase
> down the issue since the
6 matches
Mail list logo
