Thread (58 messages) 58 messages, 6 authors, 2012-03-12

Re: [PATCH 5/9] writeback: introduce the pageout work

From: Andrew Morton <akpm@linux-foundation.org>
Date: 2012-03-01 19:42:04
Also in: lkml

On Thu, 1 Mar 2012 12:04:04 +0100
Jan Kara [off-list ref] wrote:
quoted
iirc, the way I "grabbed" the page was to actually lock it, with
[try_]_lock_page().  And unlock it again way over within the writeback
thread.  I forget why I did it this way, rather than get_page() or
whatever.  Locking the page is a good way of preventing anyone else
from futzing with it.  It also pins the inode, which perhaps meant that
with careful management, I could avoid the igrab()/iput() horrors
discussed above.
  I think using get_page() might be a good way to go.
get_page() doesn't pin the inode - truncate() will still detach it
from the address_space().

--
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/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
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