* Rob Hussey <robjhussey@gmail.com> wrote:pipe-test is a very stable workload, and is thus quite sensitive to the associativity of the CPU cache. Even killing the task and repeating the same test isnt enough to get rid of the systematic skew that this can cause. I've seen divergence of up to 10% in pipe-test. One way to test it is to run pipe-test, then to stop it, then to "ssh localhost" (this in itself uses up a couple of pipe objects and file objects and changes the cache layout picture), then run pipe-test again, then again "ssh localhost", etc. Via this trick one can often see cache-layout artifacts. How much 'skew' does pipe-test have on your system if you try this manually? Ingo -
| Greg Kroah-Hartman | [PATCH 005/196] Chinese: add translation of SubmittingDrivers |
| Christian Kujau | 2.6.20.4: NETDEV WATCHDOG and lockups |
| Tarkan Erimer | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Jack Steiner | Re: [patch] my mmu notifiers |
git: | |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
| Arjan van de Ven | Re: [GIT]: Networking |
| Jarek Poplawski | [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Jens Axboe | Re: [BUG] New Kernel Bugs |
| YAMAMOTO Takashi | removing VOPs |
| Lennart Augustsson | Re: FreeBSD 5/6/7 kernel emulator for NetBSD 2.x |
| Daniel Carosone | Re: direct I/O |
| Brian Buhrow | Re: /sbin/reboot and secmodel |
