- 2012年 4月 30日 5 次提交
-
-
由 Silas Boyd-Wickizer 提交于
-
由 Silas Boyd-Wickizer 提交于
-
由 Silas Boyd-Wickizer 提交于
-
由 Silas Boyd-Wickizer 提交于
-
- 2012年 4月 29日 8 次提交
-
-
由 Austin Clements 提交于
-
由 Silas Boyd-Wickizer 提交于
-
由 Silas Boyd-Wickizer 提交于
-
由 Silas Boyd-Wickizer 提交于
-
由 Silas Boyd-Wickizer 提交于
-
由 Silas Boyd-Wickizer 提交于
-
由 Silas Boyd-Wickizer 提交于
-
由 Silas Boyd-Wickizer 提交于
-
- 2012年 4月 28日 27 次提交
-
-
由 Silas Boyd-Wickizer 提交于
-
由 Silas Boyd-Wickizer 提交于
Load indirect array on demand and flush only on iupdate.
-
由 Silas Boyd-Wickizer 提交于
-
由 Silas Boyd-Wickizer 提交于
-
由 Silas Boyd-Wickizer 提交于
-
由 Silas Boyd-Wickizer 提交于
-
由 Silas Boyd-Wickizer 提交于
-
由 Austin Clements 提交于
This eliminates all reports of unexpected sharing except a few cases of honest-to-goodness memory reuse.
-
由 Austin Clements 提交于
-
由 Austin Clements 提交于
-
由 Austin Clements 提交于
Mostly to make sure what I just did works.
-
由 Austin Clements 提交于
This works by lazily allocating a lock's klockstat structure when the lock is first acquired.
-
由 Austin Clements 提交于
These safety policies help ensure that an accessor does not migrate CPUs while accessing a percpu variable. The "cli" safety policy only allows percpu variables to be accessed when interrupts are disabled. The "internal" safety policy leaves it up to the caller. Not surprisingly, most current percpu variables use internal.
-
由 Austin Clements 提交于
These locks can be statically constructed in the .data segment, since the constructor is constexpr. Currently this only works for locks that aren't tracked by lockstat.
-
由 Silas Boyd-Wickizer 提交于
-
由 Silas Boyd-Wickizer 提交于
-
由 Silas Boyd-Wickizer 提交于
-
由 Silas Boyd-Wickizer 提交于
-
由 Silas Boyd-Wickizer 提交于
-
由 Silas Boyd-Wickizer 提交于
-
由 Silas Boyd-Wickizer 提交于
-
由 Austin Clements 提交于
-
由 Austin Clements 提交于
-
由 Austin Clements 提交于
Like the find method of standard containers, this returns an iterator to the requested key.
-
由 Silas Boyd-Wickizer 提交于
-
由 Silas Boyd-Wickizer 提交于
-