Kyle Moffett wrote:Sure, tie yourself to a Linux-specific mechanism that may or may not work over things like NFS. That's much worse. Right, tie yourself to process-shared mutexes which historically weren't available on Linux. That's much better than an option that's been stable for a decade. How is that better? There is literally no improvement, since the first check will (almost) always fail. The evidence is that more than half the time, this avoids the sleep. That means it has zero cost, since the yield is no heavier than a sleep would be, and has a possible benefit, since the first sleep may be too long. The problem is that if the estimate is too short, pre-emption will result in a huge performance drop. If the estimate is too long, there will be some wasted CPU. What was the claimed benefit of doing this again? Your standards for "optimal" are totally unrealistic. In his case, it was optimal. Using platform-specific optimizations would have meant more development and test time for minimal benefit. Sleeping first would have had some performance cost and no benefit. In his case, sched_yield was optimal. Really. DS --
| david | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Bart Van Assche | Integration of SCST in the mainstream Linux kernel |
| Greg KH | [GIT PATCH] driver core patches against 2.6.24 |
| Heiko Carstens | Re: -mm merge plans for 2.6.23 -- sys_fallocate |
git: | |
| David Miller | Re: [GIT]: Networking |
| Jarek Poplawski | [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Gerrit Renker | [PATCH 05/37] dccp: Cleanup routines for feature negotiation |
| Lennert Buytenhek | [PATCH 16/39] mv643xx_eth: get rid of ETH_/ethernet_/eth_ prefixes |
