On Tue, 20 May 2008, MA QING A wrote:The test I used is a performance test, not a latency test. An RTOS (Real-time Operating System) will sacrifice performance to achieve determinism (low latencies). Several key features to an RT system usually come with a performance cost. A non RT system will perform 99% of the time faster than an RTOS. But all it takes is that one time to miss a deadline to make an RT system crash. An RTOS may be slightly slower, but it will not have those outliers that a normal desktop system would have. So getting back to your question. Hackbench runs a bunch of stuff and times how long it took to do so. It stresses the system quite a bit. The lower the number the better. Given that hackbench is not checking for latency, but only shear perforance, it is expected that hackbench will run better on a non RT system. Now, a test like cyclictest that measures latencies will show the benefits of realtime. The kernel with the RT patch can measure 65 microsecond latencies for response times even while running hackbench. The vanilla kernel would measure a few milliseconds response times running the same test. -- Steve --
| Greg KH | [GIT PATCH] driver core patches against 2.6.24 |
| debian developer | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Greg Kroah-Hartman | [patch 00/40] 2.6.23-stable review, driver (sans network) changes |
| Roland Dreier | Re: Integration of SCST in the mainstream Linux kernel |
git: | |
| Gerrit Renker | [PATCH 03/37] dccp: List management for new feature negotiation |
| Arjan van de Ven | Re: [GIT]: Networking |
| David Miller | Re: [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Natalie Protasevich | [BUG] New Kernel Bugs |
