On Tue, 2012-05-15 at 00:33 -0400, KOSAKI Motohiro wrote: > > 3. Thera are several places which already have migrate mlocked pages but it's okay because > > it's done under user's control while compaction/khugepagd doesn't. > > I disagree. CPUSETS are used from admins. realtime _application_ is written > by application developers. ok, they are often overwrapped or the same. but it's > not exactly true. memory hotplug has similar situation. I'm not exactly sure I get what you're saying, but with the current scheme of things its impossible to run an RT app properly without the administrator knowing wrf he's doing. So the fact that cpusets are admin only doesn't matter, he'd better know about the rt apps and its requirements. This very much includes crap like THP (which, as stated, is unavailable for PREEMPT_RT) since that is under administrator control. CMA and other allocation based compaction much less so though. > Moreover, Think mix up rt-app and non-rt-migrate_pages-user-app situation. RT > app still be faced minor page fault and it's not expected from rt-app > developers. It would be if they'd listened to what I've been telling them for ages. Anyway.. taking faults isn't the problem for RT, taking indeterministic time to satisfy them is, and disk IO is completely off the charts indeterministic. Minor faults much less so. There is a very big difference between very fast and real-time, they've got very little to do with one another. That said, the way page migration currently works isn't ideal from a determinism pov, the migration PTE can be present for a basically indeterminate amount of time. So yes, page migration is a 'serious' problem, but only because the way its implemented is sub-optimal. -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxx. For more info on Linux MM, see: http://www.linux-mm.org/ . Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/ Don't email: <a href