On Wed, 27 Jun 2012 11:09:31 +0900 Minchan Kim <minchan@xxxxxxxxxx> wrote: > On 06/27/2012 10:15 AM, Andrew Morton wrote: > > >> Considering mlock and CPU pinning > >> > of realtime thread is very rare, it might be rather expensive solution. > >> > Unfortunately, I have no idea better than you suggested. :( > >> > > >> > And looking 8891d6da17, mlock's lru_add_drain_all isn't must. > >> > If it's really bother us, couldn't we remove it? > > "grep lru_add_drain_all mm/*.c". They're all problematic. > > > Yeb but I'm not sure such system modeling is good. > Potentially, It could make problem once we use workqueue of other CPU. whut? My suggestion is that we switch lru_add_drain_all() to on_each_cpu() and delete schedule_on_each_cpu(). No workqueues. -- 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/ . Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>