On Sat, 31 Oct 2009, Rik van Riel wrote: > On 10/31/2009 04:11 PM, Pavel Machek wrote: > > > But we can't guarantee that enough memory will be ready in the > > reserves. So if realtime task relies on it, it is broken, and will > > fail to meet its deadlines from time to time. > > Any realtime task that does networking (which may be the > majority of realtime tasks) relies on the kernel memory > allocator. What is realtime in this scenario? There are no guarantees that reclaim wont have to occur. There are no guarantees anymore and therefore you cannot really call this realtime. Is realtime anything more than: "I want to have my patches merged"? Give some criteria as to what realtime is please. I am all for decreasing kernel latencies. But some of this work is adding bloat and increasing overhead. -- To unsubscribe from this list: send the line "unsubscribe kernel-testers" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
