Thread (20 messages) 20 messages, 5 authors, 2012-06-29

Re: needed lru_add_drain_all() change

From: Andrew Morton <akpm@linux-foundation.org>
Date: 2012-06-27 05:11:14

On Wed, 27 Jun 2012 11:09:31 +0900 Minchan Kim [off-list ref] wrote:
On 06/27/2012 10:15 AM, Andrew Morton wrote:
quoted
quoted
Considering mlock and CPU pinning
quoted
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@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help