]> pilppa.com Git - linux-2.6-omap-h63xx.git/commit
mm: document tree_lock->zone.lock lockorder
authorNick Piggin <npiggin@suse.de>
Wed, 17 Oct 2007 06:26:02 +0000 (23:26 -0700)
committerLinus Torvalds <torvalds@woody.linux-foundation.org>
Wed, 17 Oct 2007 15:42:46 +0000 (08:42 -0700)
commit7a4050791b23c55a451974027d41d72a9b78039b
treef3956a04f24a2406276804124853535a59c0cbc1
parentd773ed6b856a96bd6d18b6e04455e3ced0876da4
mm: document tree_lock->zone.lock lockorder

zone->lock is quite an "inner" lock and mostly constrained to page alloc as
well, so like slab locks, it probably isn't something that is critically
important to document here.  However unlike slab locks, zone lock could be
used more widely in future, and page_alloc.c might possibly have more
business to do tricky things with pagecache than does slab.  So...  I don't
think it hurts to document it.

Signed-off-by: Nick Piggin <npiggin@suse.de>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
mm/filemap.c
mm/rmap.c