2005-11-08 01:19:07 +03:00
/*
* linux / fs / pnode . c
*
* ( C ) Copyright IBM Corporation 2005.
* Released under GPL v2 .
* Author : Ram Pai ( linuxram @ us . ibm . com )
*
*/
2006-12-08 13:37:56 +03:00
# include <linux/mnt_namespace.h>
2005-11-08 01:19:07 +03:00
# include <linux/mount.h>
# include <linux/fs.h>
2008-03-22 22:48:17 +03:00
# include "internal.h"
2005-11-08 01:19:07 +03:00
# include "pnode.h"
2005-11-08 01:19:33 +03:00
/* return the next shared peer mount of @p */
static inline struct vfsmount * next_peer ( struct vfsmount * p )
{
return list_entry ( p - > mnt_share . next , struct vfsmount , mnt_share ) ;
}
2005-11-08 01:21:01 +03:00
static inline struct vfsmount * first_slave ( struct vfsmount * p )
{
return list_entry ( p - > mnt_slave_list . next , struct vfsmount , mnt_slave ) ;
}
static inline struct vfsmount * next_slave ( struct vfsmount * p )
{
return list_entry ( p - > mnt_slave . next , struct vfsmount , mnt_slave ) ;
}
2008-03-27 15:06:26 +03:00
/*
* Return true if path is reachable from root
*
* namespace_sem is held , and mnt is attached
*/
static bool is_path_reachable ( struct vfsmount * mnt , struct dentry * dentry ,
const struct path * root )
{
while ( mnt ! = root - > mnt & & mnt - > mnt_parent ! = mnt ) {
dentry = mnt - > mnt_mountpoint ;
mnt = mnt - > mnt_parent ;
}
return mnt = = root - > mnt & & is_subdir ( dentry , root - > dentry ) ;
}
static struct vfsmount * get_peer_under_root ( struct vfsmount * mnt ,
struct mnt_namespace * ns ,
const struct path * root )
{
struct vfsmount * m = mnt ;
do {
/* Check the namespace first for optimization */
if ( m - > mnt_ns = = ns & & is_path_reachable ( m , m - > mnt_root , root ) )
return m ;
m = next_peer ( m ) ;
} while ( m ! = mnt ) ;
return NULL ;
}
/*
* Get ID of closest dominating peer group having a representative
* under the given root .
*
* Caller must hold namespace_sem
*/
int get_dominating_id ( struct vfsmount * mnt , const struct path * root )
{
struct vfsmount * m ;
for ( m = mnt - > mnt_master ; m ! = NULL ; m = m - > mnt_master ) {
struct vfsmount * d = get_peer_under_root ( m , mnt - > mnt_ns , root ) ;
if ( d )
return d - > mnt_group_id ;
}
return 0 ;
}
2005-11-08 01:20:48 +03:00
static int do_make_slave ( struct vfsmount * mnt )
{
struct vfsmount * peer_mnt = mnt , * master = mnt - > mnt_master ;
struct vfsmount * slave_mnt ;
/*
* slave ' mnt ' to a peer mount that has the
2010-01-16 21:28:47 +03:00
* same root dentry . If none is available then
2005-11-08 01:20:48 +03:00
* slave it to anything that is available .
*/
while ( ( peer_mnt = next_peer ( peer_mnt ) ) ! = mnt & &
peer_mnt - > mnt_root ! = mnt - > mnt_root ) ;
if ( peer_mnt = = mnt ) {
peer_mnt = next_peer ( mnt ) ;
if ( peer_mnt = = mnt )
peer_mnt = NULL ;
}
2008-03-27 15:06:23 +03:00
if ( IS_MNT_SHARED ( mnt ) & & list_empty ( & mnt - > mnt_share ) )
mnt_release_group_id ( mnt ) ;
2005-11-08 01:20:48 +03:00
list_del_init ( & mnt - > mnt_share ) ;
2008-03-27 15:06:23 +03:00
mnt - > mnt_group_id = 0 ;
2005-11-08 01:20:48 +03:00
if ( peer_mnt )
master = peer_mnt ;
if ( master ) {
list_for_each_entry ( slave_mnt , & mnt - > mnt_slave_list , mnt_slave )
slave_mnt - > mnt_master = master ;
2006-06-26 11:24:40 +04:00
list_move ( & mnt - > mnt_slave , & master - > mnt_slave_list ) ;
2005-11-08 01:20:48 +03:00
list_splice ( & mnt - > mnt_slave_list , master - > mnt_slave_list . prev ) ;
INIT_LIST_HEAD ( & mnt - > mnt_slave_list ) ;
} else {
struct list_head * p = & mnt - > mnt_slave_list ;
while ( ! list_empty ( p ) ) {
Introduce a handy list_first_entry macro
There are many places in the kernel where the construction like
foo = list_entry(head->next, struct foo_struct, list);
are used.
The code might look more descriptive and neat if using the macro
list_first_entry(head, type, member) \
list_entry((head)->next, type, member)
Here is the macro itself and the examples of its usage in the generic code.
If it will turn out to be useful, I can prepare the set of patches to
inject in into arch-specific code, drivers, networking, etc.
Signed-off-by: Pavel Emelianov <xemul@openvz.org>
Signed-off-by: Kirill Korotaev <dev@openvz.org>
Cc: Randy Dunlap <randy.dunlap@oracle.com>
Cc: Andi Kleen <andi@firstfloor.org>
Cc: Zach Brown <zach.brown@oracle.com>
Cc: Davide Libenzi <davidel@xmailserver.org>
Cc: John McCutchan <ttb@tentacle.dhs.org>
Cc: Thomas Gleixner <tglx@linutronix.de>
Cc: Ingo Molnar <mingo@elte.hu>
Cc: john stultz <johnstul@us.ibm.com>
Cc: Ram Pai <linuxram@us.ibm.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2007-05-08 11:30:19 +04:00
slave_mnt = list_first_entry ( p ,
2005-11-08 01:20:48 +03:00
struct vfsmount , mnt_slave ) ;
list_del_init ( & slave_mnt - > mnt_slave ) ;
slave_mnt - > mnt_master = NULL ;
}
}
mnt - > mnt_master = master ;
CLEAR_MNT_SHARED ( mnt ) ;
return 0 ;
}
fs: brlock vfsmount_lock
fs: brlock vfsmount_lock
Use a brlock for the vfsmount lock. It must be taken for write whenever
modifying the mount hash or associated fields, and may be taken for read when
performing mount hash lookups.
A new lock is added for the mnt-id allocator, so it doesn't need to take
the heavy vfsmount write-lock.
The number of atomics should remain the same for fastpath rlock cases, though
code would be slightly slower due to per-cpu access. Scalability is not not be
much improved in common cases yet, due to other locks (ie. dcache_lock) getting
in the way. However path lookups crossing mountpoints should be one case where
scalability is improved (currently requiring the global lock).
The slowpath is slower due to use of brlock. On a 64 core, 64 socket, 32 node
Altix system (high latency to remote nodes), a simple umount microbenchmark
(mount --bind mnt mnt2 ; umount mnt2 loop 1000 times), before this patch it
took 6.8s, afterwards took 7.1s, about 5% slower.
Cc: Al Viro <viro@ZenIV.linux.org.uk>
Signed-off-by: Nick Piggin <npiggin@kernel.dk>
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
2010-08-17 22:37:39 +04:00
/*
* vfsmount lock must be held for write
*/
2005-11-08 01:19:07 +03:00
void change_mnt_propagation ( struct vfsmount * mnt , int type )
{
2005-11-08 01:19:33 +03:00
if ( type = = MS_SHARED ) {
2005-11-08 01:19:50 +03:00
set_mnt_shared ( mnt ) ;
2005-11-08 01:20:48 +03:00
return ;
}
do_make_slave ( mnt ) ;
if ( type ! = MS_SLAVE ) {
list_del_init ( & mnt - > mnt_slave ) ;
mnt - > mnt_master = NULL ;
2005-11-08 01:21:20 +03:00
if ( type = = MS_UNBINDABLE )
mnt - > mnt_flags | = MNT_UNBINDABLE ;
2008-02-06 12:36:32 +03:00
else
mnt - > mnt_flags & = ~ MNT_UNBINDABLE ;
2005-11-08 01:19:33 +03:00
}
2005-11-08 01:19:07 +03:00
}
2005-11-08 01:19:50 +03:00
/*
* get the next mount in the propagation tree .
* @ m : the mount seen last
* @ origin : the original mount from where the tree walk initiated
2010-01-16 21:28:47 +03:00
*
* Note that peer groups form contiguous segments of slave lists .
* We rely on that in get_source ( ) to be able to find out if
* vfsmount found while iterating with propagation_next ( ) is
* a peer of one we ' d found earlier .
2005-11-08 01:19:50 +03:00
*/
static struct vfsmount * propagation_next ( struct vfsmount * m ,
struct vfsmount * origin )
{
2005-11-08 01:21:01 +03:00
/* are there any slaves of this mount? */
if ( ! IS_MNT_NEW ( m ) & & ! list_empty ( & m - > mnt_slave_list ) )
return first_slave ( m ) ;
while ( 1 ) {
struct vfsmount * next ;
struct vfsmount * master = m - > mnt_master ;
2006-01-08 12:03:19 +03:00
if ( master = = origin - > mnt_master ) {
2005-11-08 01:21:01 +03:00
next = next_peer ( m ) ;
return ( ( next = = origin ) ? NULL : next ) ;
} else if ( m - > mnt_slave . next ! = & master - > mnt_slave_list )
return next_slave ( m ) ;
/* back at master */
m = master ;
}
}
/*
* return the source mount to be used for cloning
*
* @ dest the current destination mount
* @ last_dest the last seen destination mount
* @ last_src the last seen source mount
* @ type return CL_SLAVE if the new mount has to be
* cloned as a slave .
*/
static struct vfsmount * get_source ( struct vfsmount * dest ,
struct vfsmount * last_dest ,
struct vfsmount * last_src ,
int * type )
{
struct vfsmount * p_last_src = NULL ;
struct vfsmount * p_last_dest = NULL ;
while ( last_dest ! = dest - > mnt_master ) {
p_last_dest = last_dest ;
p_last_src = last_src ;
last_dest = last_dest - > mnt_master ;
last_src = last_src - > mnt_master ;
}
if ( p_last_dest ) {
do {
p_last_dest = next_peer ( p_last_dest ) ;
} while ( IS_MNT_NEW ( p_last_dest ) ) ;
2010-01-16 21:28:47 +03:00
/* is that a peer of the earlier? */
if ( dest = = p_last_dest ) {
* type = CL_MAKE_SHARED ;
return p_last_src ;
}
2005-11-08 01:21:01 +03:00
}
2010-01-16 21:28:47 +03:00
/* slave of the earlier, then */
* type = CL_SLAVE ;
/* beginning of peer group among the slaves? */
if ( IS_MNT_SHARED ( dest ) )
* type | = CL_MAKE_SHARED ;
return last_src ;
2005-11-08 01:19:50 +03:00
}
/*
* mount ' source_mnt ' under the destination ' dest_mnt ' at
* dentry ' dest_dentry ' . And propagate that mount to
* all the peer and slave mounts of ' dest_mnt ' .
* Link all the new mounts into a propagation tree headed at
* source_mnt . Also link all the new mounts using - > mnt_list
* headed at source_mnt ' s - > mnt_list
*
* @ dest_mnt : destination mount .
* @ dest_dentry : destination dentry .
* @ source_mnt : source mount .
* @ tree_list : list of heads of trees to be attached .
*/
int propagate_mnt ( struct vfsmount * dest_mnt , struct dentry * dest_dentry ,
struct vfsmount * source_mnt , struct list_head * tree_list )
{
struct vfsmount * m , * child ;
int ret = 0 ;
struct vfsmount * prev_dest_mnt = dest_mnt ;
struct vfsmount * prev_src_mnt = source_mnt ;
LIST_HEAD ( tmp_list ) ;
LIST_HEAD ( umount_list ) ;
for ( m = propagation_next ( dest_mnt , dest_mnt ) ; m ;
m = propagation_next ( m , dest_mnt ) ) {
2005-11-08 01:21:01 +03:00
int type ;
struct vfsmount * source ;
2005-11-08 01:19:50 +03:00
if ( IS_MNT_NEW ( m ) )
continue ;
2005-11-08 01:21:01 +03:00
source = get_source ( m , prev_dest_mnt , prev_src_mnt , & type ) ;
2005-11-08 01:19:50 +03:00
2005-11-08 01:21:01 +03:00
if ( ! ( child = copy_tree ( source , source - > mnt_root , type ) ) ) {
2005-11-08 01:19:50 +03:00
ret = - ENOMEM ;
list_splice ( tree_list , tmp_list . prev ) ;
goto out ;
}
if ( is_subdir ( dest_dentry , m - > mnt_root ) ) {
mnt_set_mountpoint ( m , dest_dentry , child ) ;
list_add_tail ( & child - > mnt_hash , tree_list ) ;
} else {
/*
* This can happen if the parent mount was bind mounted
* on some subdirectory of a shared / slave mount .
*/
list_add_tail ( & child - > mnt_hash , & tmp_list ) ;
}
prev_dest_mnt = m ;
prev_src_mnt = child ;
}
out :
fs: brlock vfsmount_lock
fs: brlock vfsmount_lock
Use a brlock for the vfsmount lock. It must be taken for write whenever
modifying the mount hash or associated fields, and may be taken for read when
performing mount hash lookups.
A new lock is added for the mnt-id allocator, so it doesn't need to take
the heavy vfsmount write-lock.
The number of atomics should remain the same for fastpath rlock cases, though
code would be slightly slower due to per-cpu access. Scalability is not not be
much improved in common cases yet, due to other locks (ie. dcache_lock) getting
in the way. However path lookups crossing mountpoints should be one case where
scalability is improved (currently requiring the global lock).
The slowpath is slower due to use of brlock. On a 64 core, 64 socket, 32 node
Altix system (high latency to remote nodes), a simple umount microbenchmark
(mount --bind mnt mnt2 ; umount mnt2 loop 1000 times), before this patch it
took 6.8s, afterwards took 7.1s, about 5% slower.
Cc: Al Viro <viro@ZenIV.linux.org.uk>
Signed-off-by: Nick Piggin <npiggin@kernel.dk>
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
2010-08-17 22:37:39 +04:00
br_write_lock ( vfsmount_lock ) ;
2005-11-08 01:19:50 +03:00
while ( ! list_empty ( & tmp_list ) ) {
2008-03-24 07:16:03 +03:00
child = list_first_entry ( & tmp_list , struct vfsmount , mnt_hash ) ;
2005-11-08 01:20:17 +03:00
umount_tree ( child , 0 , & umount_list ) ;
2005-11-08 01:19:50 +03:00
}
fs: brlock vfsmount_lock
fs: brlock vfsmount_lock
Use a brlock for the vfsmount lock. It must be taken for write whenever
modifying the mount hash or associated fields, and may be taken for read when
performing mount hash lookups.
A new lock is added for the mnt-id allocator, so it doesn't need to take
the heavy vfsmount write-lock.
The number of atomics should remain the same for fastpath rlock cases, though
code would be slightly slower due to per-cpu access. Scalability is not not be
much improved in common cases yet, due to other locks (ie. dcache_lock) getting
in the way. However path lookups crossing mountpoints should be one case where
scalability is improved (currently requiring the global lock).
The slowpath is slower due to use of brlock. On a 64 core, 64 socket, 32 node
Altix system (high latency to remote nodes), a simple umount microbenchmark
(mount --bind mnt mnt2 ; umount mnt2 loop 1000 times), before this patch it
took 6.8s, afterwards took 7.1s, about 5% slower.
Cc: Al Viro <viro@ZenIV.linux.org.uk>
Signed-off-by: Nick Piggin <npiggin@kernel.dk>
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
2010-08-17 22:37:39 +04:00
br_write_unlock ( vfsmount_lock ) ;
2005-11-08 01:19:50 +03:00
release_mounts ( & umount_list ) ;
return ret ;
}
2005-11-08 01:20:17 +03:00
/*
* return true if the refcount is greater than count
*/
static inline int do_refcount_check ( struct vfsmount * mnt , int count )
{
fs: scale mntget/mntput
The problem that this patch aims to fix is vfsmount refcounting scalability.
We need to take a reference on the vfsmount for every successful path lookup,
which often go to the same mount point.
The fundamental difficulty is that a "simple" reference count can never be made
scalable, because any time a reference is dropped, we must check whether that
was the last reference. To do that requires communication with all other CPUs
that may have taken a reference count.
We can make refcounts more scalable in a couple of ways, involving keeping
distributed counters, and checking for the global-zero condition less
frequently.
- check the global sum once every interval (this will delay zero detection
for some interval, so it's probably a showstopper for vfsmounts).
- keep a local count and only taking the global sum when local reaches 0 (this
is difficult for vfsmounts, because we can't hold preempt off for the life of
a reference, so a counter would need to be per-thread or tied strongly to a
particular CPU which requires more locking).
- keep a local difference of increments and decrements, which allows us to sum
the total difference and hence find the refcount when summing all CPUs. Then,
keep a single integer "long" refcount for slow and long lasting references,
and only take the global sum of local counters when the long refcount is 0.
This last scheme is what I implemented here. Attached mounts and process root
and working directory references are "long" references, and everything else is
a short reference.
This allows scalable vfsmount references during path walking over mounted
subtrees and unattached (lazy umounted) mounts with processes still running
in them.
This results in one fewer atomic op in the fastpath: mntget is now just a
per-CPU inc, rather than an atomic inc; and mntput just requires a spinlock
and non-atomic decrement in the common case. However code is otherwise bigger
and heavier, so single threaded performance is basically a wash.
Signed-off-by: Nick Piggin <npiggin@kernel.dk>
2011-01-07 09:50:11 +03:00
int mycount = mnt_get_count ( mnt ) - mnt - > mnt_ghosts ;
2005-11-08 01:20:17 +03:00
return ( mycount > count ) ;
}
/*
* check if the mount ' mnt ' can be unmounted successfully .
* @ mnt : the mount to be checked for unmount
* NOTE : unmounting ' mnt ' would naturally propagate to all
* other mounts its parent propagates to .
* Check if any of these mounts that * * do not have submounts * *
* have more references than ' refcnt ' . If so return busy .
fs: brlock vfsmount_lock
fs: brlock vfsmount_lock
Use a brlock for the vfsmount lock. It must be taken for write whenever
modifying the mount hash or associated fields, and may be taken for read when
performing mount hash lookups.
A new lock is added for the mnt-id allocator, so it doesn't need to take
the heavy vfsmount write-lock.
The number of atomics should remain the same for fastpath rlock cases, though
code would be slightly slower due to per-cpu access. Scalability is not not be
much improved in common cases yet, due to other locks (ie. dcache_lock) getting
in the way. However path lookups crossing mountpoints should be one case where
scalability is improved (currently requiring the global lock).
The slowpath is slower due to use of brlock. On a 64 core, 64 socket, 32 node
Altix system (high latency to remote nodes), a simple umount microbenchmark
(mount --bind mnt mnt2 ; umount mnt2 loop 1000 times), before this patch it
took 6.8s, afterwards took 7.1s, about 5% slower.
Cc: Al Viro <viro@ZenIV.linux.org.uk>
Signed-off-by: Nick Piggin <npiggin@kernel.dk>
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
2010-08-17 22:37:39 +04:00
*
fs: scale mntget/mntput
The problem that this patch aims to fix is vfsmount refcounting scalability.
We need to take a reference on the vfsmount for every successful path lookup,
which often go to the same mount point.
The fundamental difficulty is that a "simple" reference count can never be made
scalable, because any time a reference is dropped, we must check whether that
was the last reference. To do that requires communication with all other CPUs
that may have taken a reference count.
We can make refcounts more scalable in a couple of ways, involving keeping
distributed counters, and checking for the global-zero condition less
frequently.
- check the global sum once every interval (this will delay zero detection
for some interval, so it's probably a showstopper for vfsmounts).
- keep a local count and only taking the global sum when local reaches 0 (this
is difficult for vfsmounts, because we can't hold preempt off for the life of
a reference, so a counter would need to be per-thread or tied strongly to a
particular CPU which requires more locking).
- keep a local difference of increments and decrements, which allows us to sum
the total difference and hence find the refcount when summing all CPUs. Then,
keep a single integer "long" refcount for slow and long lasting references,
and only take the global sum of local counters when the long refcount is 0.
This last scheme is what I implemented here. Attached mounts and process root
and working directory references are "long" references, and everything else is
a short reference.
This allows scalable vfsmount references during path walking over mounted
subtrees and unattached (lazy umounted) mounts with processes still running
in them.
This results in one fewer atomic op in the fastpath: mntget is now just a
per-CPU inc, rather than an atomic inc; and mntput just requires a spinlock
and non-atomic decrement in the common case. However code is otherwise bigger
and heavier, so single threaded performance is basically a wash.
Signed-off-by: Nick Piggin <npiggin@kernel.dk>
2011-01-07 09:50:11 +03:00
* vfsmount lock must be held for write
2005-11-08 01:20:17 +03:00
*/
int propagate_mount_busy ( struct vfsmount * mnt , int refcnt )
{
struct vfsmount * m , * child ;
struct vfsmount * parent = mnt - > mnt_parent ;
int ret = 0 ;
if ( mnt = = parent )
return do_refcount_check ( mnt , refcnt ) ;
/*
* quickly check if the current mount can be unmounted .
* If not , we don ' t have to go checking for all other
* mounts
*/
if ( ! list_empty ( & mnt - > mnt_mounts ) | | do_refcount_check ( mnt , refcnt ) )
return 1 ;
for ( m = propagation_next ( parent , parent ) ; m ;
m = propagation_next ( m , parent ) ) {
child = __lookup_mnt ( m , mnt - > mnt_mountpoint , 0 ) ;
if ( child & & list_empty ( & child - > mnt_mounts ) & &
( ret = do_refcount_check ( child , 1 ) ) )
break ;
}
return ret ;
}
/*
* NOTE : unmounting ' mnt ' naturally propagates to all other mounts its
* parent propagates to .
*/
static void __propagate_umount ( struct vfsmount * mnt )
{
struct vfsmount * parent = mnt - > mnt_parent ;
struct vfsmount * m ;
BUG_ON ( parent = = mnt ) ;
for ( m = propagation_next ( parent , parent ) ; m ;
m = propagation_next ( m , parent ) ) {
struct vfsmount * child = __lookup_mnt ( m ,
mnt - > mnt_mountpoint , 0 ) ;
/*
* umount the child only if the child has no
* other children
*/
2006-06-26 11:24:40 +04:00
if ( child & & list_empty ( & child - > mnt_mounts ) )
list_move_tail ( & child - > mnt_hash , & mnt - > mnt_hash ) ;
2005-11-08 01:20:17 +03:00
}
}
/*
* collect all mounts that receive propagation from the mount in @ list ,
* and return these additional mounts in the same list .
* @ list : the list of mounts to be unmounted .
fs: brlock vfsmount_lock
fs: brlock vfsmount_lock
Use a brlock for the vfsmount lock. It must be taken for write whenever
modifying the mount hash or associated fields, and may be taken for read when
performing mount hash lookups.
A new lock is added for the mnt-id allocator, so it doesn't need to take
the heavy vfsmount write-lock.
The number of atomics should remain the same for fastpath rlock cases, though
code would be slightly slower due to per-cpu access. Scalability is not not be
much improved in common cases yet, due to other locks (ie. dcache_lock) getting
in the way. However path lookups crossing mountpoints should be one case where
scalability is improved (currently requiring the global lock).
The slowpath is slower due to use of brlock. On a 64 core, 64 socket, 32 node
Altix system (high latency to remote nodes), a simple umount microbenchmark
(mount --bind mnt mnt2 ; umount mnt2 loop 1000 times), before this patch it
took 6.8s, afterwards took 7.1s, about 5% slower.
Cc: Al Viro <viro@ZenIV.linux.org.uk>
Signed-off-by: Nick Piggin <npiggin@kernel.dk>
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
2010-08-17 22:37:39 +04:00
*
* vfsmount lock must be held for write
2005-11-08 01:20:17 +03:00
*/
int propagate_umount ( struct list_head * list )
{
struct vfsmount * mnt ;
list_for_each_entry ( mnt , list , mnt_hash )
__propagate_umount ( mnt ) ;
return 0 ;
}