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>
2013-03-22 15:08:05 +04:00
# include <linux/nsproxy.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 */
2011-11-25 08:56:26 +04:00
static inline struct mount * next_peer ( struct mount * p )
2005-11-08 01:19:33 +03:00
{
2011-11-25 09:22:05 +04:00
return list_entry ( p - > mnt_share . next , struct mount , mnt_share ) ;
2005-11-08 01:19:33 +03:00
}
2011-11-25 08:56:26 +04:00
static inline struct mount * first_slave ( struct mount * p )
2005-11-08 01:21:01 +03:00
{
2011-11-25 09:22:05 +04:00
return list_entry ( p - > mnt_slave_list . next , struct mount , mnt_slave ) ;
2005-11-08 01:21:01 +03:00
}
2011-11-25 08:56:26 +04:00
static inline struct mount * next_slave ( struct mount * p )
2005-11-08 01:21:01 +03:00
{
2011-11-25 09:22:05 +04:00
return list_entry ( p - > mnt_slave . next , struct mount , mnt_slave ) ;
2005-11-08 01:21:01 +03:00
}
2011-11-25 08:35:54 +04:00
static struct mount * get_peer_under_root ( struct mount * mnt ,
struct mnt_namespace * ns ,
const struct path * root )
2008-03-27 15:06:26 +03:00
{
2011-11-25 08:35:54 +04:00
struct mount * m = mnt ;
2008-03-27 15:06:26 +03:00
do {
/* Check the namespace first for optimization */
2011-11-25 09:46:35 +04:00
if ( m - > mnt_ns = = ns & & is_path_reachable ( m , m - > mnt . mnt_root , root ) )
2011-11-25 08:35:54 +04:00
return m ;
2008-03-27 15:06:26 +03:00
2011-11-25 08:56:26 +04:00
m = next_peer ( m ) ;
2011-11-25 08:35:54 +04:00
} while ( m ! = mnt ) ;
2008-03-27 15:06:26 +03:00
return NULL ;
}
/*
* Get ID of closest dominating peer group having a representative
* under the given root .
*
* Caller must hold namespace_sem
*/
2011-11-25 08:35:54 +04:00
int get_dominating_id ( struct mount * mnt , const struct path * root )
2008-03-27 15:06:26 +03:00
{
2011-11-25 08:35:54 +04:00
struct mount * m ;
2008-03-27 15:06:26 +03:00
2011-11-25 09:10:28 +04:00
for ( m = mnt - > mnt_master ; m ! = NULL ; m = m - > mnt_master ) {
2011-11-25 09:46:35 +04:00
struct mount * d = get_peer_under_root ( m , mnt - > mnt_ns , root ) ;
2008-03-27 15:06:26 +03:00
if ( d )
2011-11-25 09:50:41 +04:00
return d - > mnt_group_id ;
2008-03-27 15:06:26 +03:00
}
return 0 ;
}
2011-11-25 08:35:54 +04:00
static int do_make_slave ( struct mount * mnt )
2005-11-08 01:20:48 +03:00
{
2011-11-25 09:10:28 +04:00
struct mount * peer_mnt = mnt , * master = mnt - > mnt_master ;
2011-11-25 09:07:16 +04:00
struct mount * slave_mnt ;
2005-11-08 01:20:48 +03:00
/*
* 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 .
*/
2011-11-25 08:56:26 +04:00
while ( ( peer_mnt = next_peer ( peer_mnt ) ) ! = mnt & &
2011-11-25 08:35:54 +04:00
peer_mnt - > mnt . mnt_root ! = mnt - > mnt . mnt_root ) ;
2005-11-08 01:20:48 +03:00
if ( peer_mnt = = mnt ) {
2011-11-25 08:56:26 +04:00
peer_mnt = next_peer ( mnt ) ;
2005-11-08 01:20:48 +03:00
if ( peer_mnt = = mnt )
peer_mnt = NULL ;
}
2013-05-10 16:04:11 +04:00
if ( mnt - > mnt_group_id & & IS_MNT_SHARED ( mnt ) & &
list_empty ( & mnt - > mnt_share ) )
2011-11-25 08:35:54 +04:00
mnt_release_group_id ( mnt ) ;
2008-03-27 15:06:23 +03:00
2011-11-25 09:22:05 +04:00
list_del_init ( & mnt - > mnt_share ) ;
2011-11-25 09:50:41 +04:00
mnt - > mnt_group_id = 0 ;
2005-11-08 01:20:48 +03:00
if ( peer_mnt )
master = peer_mnt ;
if ( master ) {
2011-11-25 09:22:05 +04:00
list_for_each_entry ( slave_mnt , & mnt - > mnt_slave_list , mnt_slave )
2011-11-25 09:10:28 +04:00
slave_mnt - > mnt_master = master ;
2011-11-25 09:22:05 +04:00
list_move ( & mnt - > mnt_slave , & master - > mnt_slave_list ) ;
list_splice ( & mnt - > mnt_slave_list , master - > mnt_slave_list . prev ) ;
INIT_LIST_HEAD ( & mnt - > mnt_slave_list ) ;
2005-11-08 01:20:48 +03:00
} else {
2011-11-25 09:22:05 +04:00
struct list_head * p = & mnt - > mnt_slave_list ;
2005-11-08 01:20:48 +03:00
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 ,
2011-11-25 09:22:05 +04:00
struct mount , mnt_slave ) ;
list_del_init ( & slave_mnt - > mnt_slave ) ;
2005-11-08 01:20:48 +03:00
slave_mnt - > mnt_master = NULL ;
}
}
2011-11-25 09:10:28 +04:00
mnt - > mnt_master = master ;
2011-11-25 10:05:37 +04:00
CLEAR_MNT_SHARED ( mnt ) ;
2005-11-08 01:20:48 +03:00
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
*/
2011-11-25 05:43:10 +04:00
void change_mnt_propagation ( struct mount * mnt , int type )
2005-11-08 01:19:07 +03:00
{
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 ;
}
2011-11-25 08:35:54 +04:00
do_make_slave ( mnt ) ;
2005-11-08 01:20:48 +03:00
if ( type ! = MS_SLAVE ) {
2011-11-25 09:22:05 +04:00
list_del_init ( & mnt - > mnt_slave ) ;
2011-11-25 09:07:16 +04:00
mnt - > mnt_master = NULL ;
2005-11-08 01:21:20 +03:00
if ( type = = MS_UNBINDABLE )
2011-11-25 05:43:10 +04:00
mnt - > mnt . mnt_flags | = MNT_UNBINDABLE ;
2008-02-06 12:36:32 +03:00
else
2011-11-25 05:43:10 +04:00
mnt - > 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
*/
2011-11-25 08:56:26 +04:00
static struct mount * propagation_next ( struct mount * m ,
struct mount * origin )
2005-11-08 01:19:50 +03:00
{
2005-11-08 01:21:01 +03:00
/* are there any slaves of this mount? */
2011-11-25 09:46:35 +04:00
if ( ! IS_MNT_NEW ( m ) & & ! list_empty ( & m - > mnt_slave_list ) )
2005-11-08 01:21:01 +03:00
return first_slave ( m ) ;
while ( 1 ) {
2011-11-25 09:10:28 +04:00
struct mount * master = m - > mnt_master ;
2005-11-08 01:21:01 +03:00
2011-11-25 09:10:28 +04:00
if ( master = = origin - > mnt_master ) {
2011-11-25 08:56:26 +04:00
struct mount * next = next_peer ( m ) ;
return ( next = = origin ) ? NULL : next ;
2011-11-25 09:22:05 +04:00
} else if ( m - > mnt_slave . next ! = & master - > mnt_slave_list )
2005-11-08 01:21:01 +03:00
return next_slave ( m ) ;
/* back at master */
m = master ;
}
}
smarter propagate_mnt()
The current mainline has copies propagated to *all* nodes, then
tears down the copies we made for nodes that do not contain
counterparts of the desired mountpoint. That sets the right
propagation graph for the copies (at teardown time we move
the slaves of removed node to a surviving peer or directly
to master), but we end up paying a fairly steep price in
useless allocations. It's fairly easy to create a situation
where N calls of mount(2) create exactly N bindings, with
O(N^2) vfsmounts allocated and freed in process.
Fortunately, it is possible to avoid those allocations/freeings.
The trick is to create copies in the right order and find which
one would've eventually become a master with the current algorithm.
It turns out to be possible in O(nodes getting propagation) time
and with no extra allocations at all.
One part is that we need to make sure that eventual master will be
created before its slaves, so we need to walk the propagation
tree in a different order - by peer groups. And iterate through
the peers before dealing with the next group.
Another thing is finding the (earlier) copy that will be a master
of one we are about to create; to do that we are (temporary) marking
the masters of mountpoints we are attaching the copies to.
Either we are in a peer of the last mountpoint we'd dealt with,
or we have the following situation: we are attaching to mountpoint M,
the last copy S_0 had been attached to M_0 and there are sequences
S_0...S_n, M_0...M_n such that S_{i+1} is a master of S_{i},
S_{i} mounted on M{i} and we need to create a slave of the first S_{k}
such that M is getting propagation from M_{k}. It means that the master
of M_{k} will be among the sequence of masters of M. On the
other hand, the nearest marked node in that sequence will either
be the master of M_{k} or the master of M_{k-1} (the latter -
in the case if M_{k-1} is a slave of something M gets propagation
from, but in a wrong peer group).
So we go through the sequence of masters of M until we find
a marked one (P). Let N be the one before it. Then we go through
the sequence of masters of S_0 until we find one (say, S) mounted
on a node D that has P as master and check if D is a peer of N.
If it is, S will be the master of new copy, if not - the master of S
will be.
That's it for the hard part; the rest is fairly simple. Iterator
is in next_group(), handling of one prospective mountpoint is
propagate_one().
It seems to survive all tests and gives a noticably better performance
than the current mainline for setups that are seriously using shared
subtrees.
Cc: stable@vger.kernel.org
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
2014-02-27 18:35:45 +04:00
static struct mount * next_group ( struct mount * m , struct mount * origin )
2005-11-08 01:21:01 +03:00
{
smarter propagate_mnt()
The current mainline has copies propagated to *all* nodes, then
tears down the copies we made for nodes that do not contain
counterparts of the desired mountpoint. That sets the right
propagation graph for the copies (at teardown time we move
the slaves of removed node to a surviving peer or directly
to master), but we end up paying a fairly steep price in
useless allocations. It's fairly easy to create a situation
where N calls of mount(2) create exactly N bindings, with
O(N^2) vfsmounts allocated and freed in process.
Fortunately, it is possible to avoid those allocations/freeings.
The trick is to create copies in the right order and find which
one would've eventually become a master with the current algorithm.
It turns out to be possible in O(nodes getting propagation) time
and with no extra allocations at all.
One part is that we need to make sure that eventual master will be
created before its slaves, so we need to walk the propagation
tree in a different order - by peer groups. And iterate through
the peers before dealing with the next group.
Another thing is finding the (earlier) copy that will be a master
of one we are about to create; to do that we are (temporary) marking
the masters of mountpoints we are attaching the copies to.
Either we are in a peer of the last mountpoint we'd dealt with,
or we have the following situation: we are attaching to mountpoint M,
the last copy S_0 had been attached to M_0 and there are sequences
S_0...S_n, M_0...M_n such that S_{i+1} is a master of S_{i},
S_{i} mounted on M{i} and we need to create a slave of the first S_{k}
such that M is getting propagation from M_{k}. It means that the master
of M_{k} will be among the sequence of masters of M. On the
other hand, the nearest marked node in that sequence will either
be the master of M_{k} or the master of M_{k-1} (the latter -
in the case if M_{k-1} is a slave of something M gets propagation
from, but in a wrong peer group).
So we go through the sequence of masters of M until we find
a marked one (P). Let N be the one before it. Then we go through
the sequence of masters of S_0 until we find one (say, S) mounted
on a node D that has P as master and check if D is a peer of N.
If it is, S will be the master of new copy, if not - the master of S
will be.
That's it for the hard part; the rest is fairly simple. Iterator
is in next_group(), handling of one prospective mountpoint is
propagate_one().
It seems to survive all tests and gives a noticably better performance
than the current mainline for setups that are seriously using shared
subtrees.
Cc: stable@vger.kernel.org
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
2014-02-27 18:35:45 +04:00
while ( 1 ) {
while ( 1 ) {
struct mount * next ;
if ( ! IS_MNT_NEW ( m ) & & ! list_empty ( & m - > mnt_slave_list ) )
return first_slave ( m ) ;
next = next_peer ( m ) ;
if ( m - > mnt_group_id = = origin - > mnt_group_id ) {
if ( next = = origin )
return NULL ;
} else if ( m - > mnt_slave . next ! = & next - > mnt_slave )
break ;
m = next ;
}
/* m is the last peer */
while ( 1 ) {
struct mount * master = m - > mnt_master ;
if ( m - > mnt_slave . next ! = & master - > mnt_slave_list )
return next_slave ( m ) ;
m = next_peer ( master ) ;
if ( master - > mnt_group_id = = origin - > mnt_group_id )
break ;
if ( master - > mnt_slave . next = = & m - > mnt_slave )
break ;
m = master ;
}
if ( m = = origin )
return NULL ;
2005-11-08 01:21:01 +03:00
}
smarter propagate_mnt()
The current mainline has copies propagated to *all* nodes, then
tears down the copies we made for nodes that do not contain
counterparts of the desired mountpoint. That sets the right
propagation graph for the copies (at teardown time we move
the slaves of removed node to a surviving peer or directly
to master), but we end up paying a fairly steep price in
useless allocations. It's fairly easy to create a situation
where N calls of mount(2) create exactly N bindings, with
O(N^2) vfsmounts allocated and freed in process.
Fortunately, it is possible to avoid those allocations/freeings.
The trick is to create copies in the right order and find which
one would've eventually become a master with the current algorithm.
It turns out to be possible in O(nodes getting propagation) time
and with no extra allocations at all.
One part is that we need to make sure that eventual master will be
created before its slaves, so we need to walk the propagation
tree in a different order - by peer groups. And iterate through
the peers before dealing with the next group.
Another thing is finding the (earlier) copy that will be a master
of one we are about to create; to do that we are (temporary) marking
the masters of mountpoints we are attaching the copies to.
Either we are in a peer of the last mountpoint we'd dealt with,
or we have the following situation: we are attaching to mountpoint M,
the last copy S_0 had been attached to M_0 and there are sequences
S_0...S_n, M_0...M_n such that S_{i+1} is a master of S_{i},
S_{i} mounted on M{i} and we need to create a slave of the first S_{k}
such that M is getting propagation from M_{k}. It means that the master
of M_{k} will be among the sequence of masters of M. On the
other hand, the nearest marked node in that sequence will either
be the master of M_{k} or the master of M_{k-1} (the latter -
in the case if M_{k-1} is a slave of something M gets propagation
from, but in a wrong peer group).
So we go through the sequence of masters of M until we find
a marked one (P). Let N be the one before it. Then we go through
the sequence of masters of S_0 until we find one (say, S) mounted
on a node D that has P as master and check if D is a peer of N.
If it is, S will be the master of new copy, if not - the master of S
will be.
That's it for the hard part; the rest is fairly simple. Iterator
is in next_group(), handling of one prospective mountpoint is
propagate_one().
It seems to survive all tests and gives a noticably better performance
than the current mainline for setups that are seriously using shared
subtrees.
Cc: stable@vger.kernel.org
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
2014-02-27 18:35:45 +04:00
}
2005-11-08 01:21:01 +03:00
smarter propagate_mnt()
The current mainline has copies propagated to *all* nodes, then
tears down the copies we made for nodes that do not contain
counterparts of the desired mountpoint. That sets the right
propagation graph for the copies (at teardown time we move
the slaves of removed node to a surviving peer or directly
to master), but we end up paying a fairly steep price in
useless allocations. It's fairly easy to create a situation
where N calls of mount(2) create exactly N bindings, with
O(N^2) vfsmounts allocated and freed in process.
Fortunately, it is possible to avoid those allocations/freeings.
The trick is to create copies in the right order and find which
one would've eventually become a master with the current algorithm.
It turns out to be possible in O(nodes getting propagation) time
and with no extra allocations at all.
One part is that we need to make sure that eventual master will be
created before its slaves, so we need to walk the propagation
tree in a different order - by peer groups. And iterate through
the peers before dealing with the next group.
Another thing is finding the (earlier) copy that will be a master
of one we are about to create; to do that we are (temporary) marking
the masters of mountpoints we are attaching the copies to.
Either we are in a peer of the last mountpoint we'd dealt with,
or we have the following situation: we are attaching to mountpoint M,
the last copy S_0 had been attached to M_0 and there are sequences
S_0...S_n, M_0...M_n such that S_{i+1} is a master of S_{i},
S_{i} mounted on M{i} and we need to create a slave of the first S_{k}
such that M is getting propagation from M_{k}. It means that the master
of M_{k} will be among the sequence of masters of M. On the
other hand, the nearest marked node in that sequence will either
be the master of M_{k} or the master of M_{k-1} (the latter -
in the case if M_{k-1} is a slave of something M gets propagation
from, but in a wrong peer group).
So we go through the sequence of masters of M until we find
a marked one (P). Let N be the one before it. Then we go through
the sequence of masters of S_0 until we find one (say, S) mounted
on a node D that has P as master and check if D is a peer of N.
If it is, S will be the master of new copy, if not - the master of S
will be.
That's it for the hard part; the rest is fairly simple. Iterator
is in next_group(), handling of one prospective mountpoint is
propagate_one().
It seems to survive all tests and gives a noticably better performance
than the current mainline for setups that are seriously using shared
subtrees.
Cc: stable@vger.kernel.org
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
2014-02-27 18:35:45 +04:00
/* all accesses are serialized by namespace_sem */
static struct user_namespace * user_ns ;
2016-05-05 17:29:29 +03:00
static struct mount * last_dest , * first_source , * last_source , * dest_master ;
smarter propagate_mnt()
The current mainline has copies propagated to *all* nodes, then
tears down the copies we made for nodes that do not contain
counterparts of the desired mountpoint. That sets the right
propagation graph for the copies (at teardown time we move
the slaves of removed node to a surviving peer or directly
to master), but we end up paying a fairly steep price in
useless allocations. It's fairly easy to create a situation
where N calls of mount(2) create exactly N bindings, with
O(N^2) vfsmounts allocated and freed in process.
Fortunately, it is possible to avoid those allocations/freeings.
The trick is to create copies in the right order and find which
one would've eventually become a master with the current algorithm.
It turns out to be possible in O(nodes getting propagation) time
and with no extra allocations at all.
One part is that we need to make sure that eventual master will be
created before its slaves, so we need to walk the propagation
tree in a different order - by peer groups. And iterate through
the peers before dealing with the next group.
Another thing is finding the (earlier) copy that will be a master
of one we are about to create; to do that we are (temporary) marking
the masters of mountpoints we are attaching the copies to.
Either we are in a peer of the last mountpoint we'd dealt with,
or we have the following situation: we are attaching to mountpoint M,
the last copy S_0 had been attached to M_0 and there are sequences
S_0...S_n, M_0...M_n such that S_{i+1} is a master of S_{i},
S_{i} mounted on M{i} and we need to create a slave of the first S_{k}
such that M is getting propagation from M_{k}. It means that the master
of M_{k} will be among the sequence of masters of M. On the
other hand, the nearest marked node in that sequence will either
be the master of M_{k} or the master of M_{k-1} (the latter -
in the case if M_{k-1} is a slave of something M gets propagation
from, but in a wrong peer group).
So we go through the sequence of masters of M until we find
a marked one (P). Let N be the one before it. Then we go through
the sequence of masters of S_0 until we find one (say, S) mounted
on a node D that has P as master and check if D is a peer of N.
If it is, S will be the master of new copy, if not - the master of S
will be.
That's it for the hard part; the rest is fairly simple. Iterator
is in next_group(), handling of one prospective mountpoint is
propagate_one().
It seems to survive all tests and gives a noticably better performance
than the current mainline for setups that are seriously using shared
subtrees.
Cc: stable@vger.kernel.org
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
2014-02-27 18:35:45 +04:00
static struct mountpoint * mp ;
static struct hlist_head * list ;
2016-02-16 22:45:33 +03:00
static inline bool peers ( struct mount * m1 , struct mount * m2 )
{
return m1 - > mnt_group_id = = m2 - > mnt_group_id & & m1 - > mnt_group_id ;
}
smarter propagate_mnt()
The current mainline has copies propagated to *all* nodes, then
tears down the copies we made for nodes that do not contain
counterparts of the desired mountpoint. That sets the right
propagation graph for the copies (at teardown time we move
the slaves of removed node to a surviving peer or directly
to master), but we end up paying a fairly steep price in
useless allocations. It's fairly easy to create a situation
where N calls of mount(2) create exactly N bindings, with
O(N^2) vfsmounts allocated and freed in process.
Fortunately, it is possible to avoid those allocations/freeings.
The trick is to create copies in the right order and find which
one would've eventually become a master with the current algorithm.
It turns out to be possible in O(nodes getting propagation) time
and with no extra allocations at all.
One part is that we need to make sure that eventual master will be
created before its slaves, so we need to walk the propagation
tree in a different order - by peer groups. And iterate through
the peers before dealing with the next group.
Another thing is finding the (earlier) copy that will be a master
of one we are about to create; to do that we are (temporary) marking
the masters of mountpoints we are attaching the copies to.
Either we are in a peer of the last mountpoint we'd dealt with,
or we have the following situation: we are attaching to mountpoint M,
the last copy S_0 had been attached to M_0 and there are sequences
S_0...S_n, M_0...M_n such that S_{i+1} is a master of S_{i},
S_{i} mounted on M{i} and we need to create a slave of the first S_{k}
such that M is getting propagation from M_{k}. It means that the master
of M_{k} will be among the sequence of masters of M. On the
other hand, the nearest marked node in that sequence will either
be the master of M_{k} or the master of M_{k-1} (the latter -
in the case if M_{k-1} is a slave of something M gets propagation
from, but in a wrong peer group).
So we go through the sequence of masters of M until we find
a marked one (P). Let N be the one before it. Then we go through
the sequence of masters of S_0 until we find one (say, S) mounted
on a node D that has P as master and check if D is a peer of N.
If it is, S will be the master of new copy, if not - the master of S
will be.
That's it for the hard part; the rest is fairly simple. Iterator
is in next_group(), handling of one prospective mountpoint is
propagate_one().
It seems to survive all tests and gives a noticably better performance
than the current mainline for setups that are seriously using shared
subtrees.
Cc: stable@vger.kernel.org
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
2014-02-27 18:35:45 +04:00
static int propagate_one ( struct mount * m )
{
struct mount * child ;
int type ;
/* skip ones added by this propagate_mnt() */
if ( IS_MNT_NEW ( m ) )
return 0 ;
/* skip if mountpoint isn't covered by it */
if ( ! is_subdir ( mp - > m_dentry , m - > mnt . mnt_root ) )
return 0 ;
2016-02-16 22:45:33 +03:00
if ( peers ( m , last_dest ) ) {
smarter propagate_mnt()
The current mainline has copies propagated to *all* nodes, then
tears down the copies we made for nodes that do not contain
counterparts of the desired mountpoint. That sets the right
propagation graph for the copies (at teardown time we move
the slaves of removed node to a surviving peer or directly
to master), but we end up paying a fairly steep price in
useless allocations. It's fairly easy to create a situation
where N calls of mount(2) create exactly N bindings, with
O(N^2) vfsmounts allocated and freed in process.
Fortunately, it is possible to avoid those allocations/freeings.
The trick is to create copies in the right order and find which
one would've eventually become a master with the current algorithm.
It turns out to be possible in O(nodes getting propagation) time
and with no extra allocations at all.
One part is that we need to make sure that eventual master will be
created before its slaves, so we need to walk the propagation
tree in a different order - by peer groups. And iterate through
the peers before dealing with the next group.
Another thing is finding the (earlier) copy that will be a master
of one we are about to create; to do that we are (temporary) marking
the masters of mountpoints we are attaching the copies to.
Either we are in a peer of the last mountpoint we'd dealt with,
or we have the following situation: we are attaching to mountpoint M,
the last copy S_0 had been attached to M_0 and there are sequences
S_0...S_n, M_0...M_n such that S_{i+1} is a master of S_{i},
S_{i} mounted on M{i} and we need to create a slave of the first S_{k}
such that M is getting propagation from M_{k}. It means that the master
of M_{k} will be among the sequence of masters of M. On the
other hand, the nearest marked node in that sequence will either
be the master of M_{k} or the master of M_{k-1} (the latter -
in the case if M_{k-1} is a slave of something M gets propagation
from, but in a wrong peer group).
So we go through the sequence of masters of M until we find
a marked one (P). Let N be the one before it. Then we go through
the sequence of masters of S_0 until we find one (say, S) mounted
on a node D that has P as master and check if D is a peer of N.
If it is, S will be the master of new copy, if not - the master of S
will be.
That's it for the hard part; the rest is fairly simple. Iterator
is in next_group(), handling of one prospective mountpoint is
propagate_one().
It seems to survive all tests and gives a noticably better performance
than the current mainline for setups that are seriously using shared
subtrees.
Cc: stable@vger.kernel.org
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
2014-02-27 18:35:45 +04:00
type = CL_MAKE_SHARED ;
} else {
struct mount * n , * p ;
2016-05-05 17:29:29 +03:00
bool done ;
smarter propagate_mnt()
The current mainline has copies propagated to *all* nodes, then
tears down the copies we made for nodes that do not contain
counterparts of the desired mountpoint. That sets the right
propagation graph for the copies (at teardown time we move
the slaves of removed node to a surviving peer or directly
to master), but we end up paying a fairly steep price in
useless allocations. It's fairly easy to create a situation
where N calls of mount(2) create exactly N bindings, with
O(N^2) vfsmounts allocated and freed in process.
Fortunately, it is possible to avoid those allocations/freeings.
The trick is to create copies in the right order and find which
one would've eventually become a master with the current algorithm.
It turns out to be possible in O(nodes getting propagation) time
and with no extra allocations at all.
One part is that we need to make sure that eventual master will be
created before its slaves, so we need to walk the propagation
tree in a different order - by peer groups. And iterate through
the peers before dealing with the next group.
Another thing is finding the (earlier) copy that will be a master
of one we are about to create; to do that we are (temporary) marking
the masters of mountpoints we are attaching the copies to.
Either we are in a peer of the last mountpoint we'd dealt with,
or we have the following situation: we are attaching to mountpoint M,
the last copy S_0 had been attached to M_0 and there are sequences
S_0...S_n, M_0...M_n such that S_{i+1} is a master of S_{i},
S_{i} mounted on M{i} and we need to create a slave of the first S_{k}
such that M is getting propagation from M_{k}. It means that the master
of M_{k} will be among the sequence of masters of M. On the
other hand, the nearest marked node in that sequence will either
be the master of M_{k} or the master of M_{k-1} (the latter -
in the case if M_{k-1} is a slave of something M gets propagation
from, but in a wrong peer group).
So we go through the sequence of masters of M until we find
a marked one (P). Let N be the one before it. Then we go through
the sequence of masters of S_0 until we find one (say, S) mounted
on a node D that has P as master and check if D is a peer of N.
If it is, S will be the master of new copy, if not - the master of S
will be.
That's it for the hard part; the rest is fairly simple. Iterator
is in next_group(), handling of one prospective mountpoint is
propagate_one().
It seems to survive all tests and gives a noticably better performance
than the current mainline for setups that are seriously using shared
subtrees.
Cc: stable@vger.kernel.org
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
2014-02-27 18:35:45 +04:00
for ( n = m ; ; n = p ) {
p = n - > mnt_master ;
2016-05-05 17:29:29 +03:00
if ( p = = dest_master | | IS_MNT_MARKED ( p ) )
smarter propagate_mnt()
The current mainline has copies propagated to *all* nodes, then
tears down the copies we made for nodes that do not contain
counterparts of the desired mountpoint. That sets the right
propagation graph for the copies (at teardown time we move
the slaves of removed node to a surviving peer or directly
to master), but we end up paying a fairly steep price in
useless allocations. It's fairly easy to create a situation
where N calls of mount(2) create exactly N bindings, with
O(N^2) vfsmounts allocated and freed in process.
Fortunately, it is possible to avoid those allocations/freeings.
The trick is to create copies in the right order and find which
one would've eventually become a master with the current algorithm.
It turns out to be possible in O(nodes getting propagation) time
and with no extra allocations at all.
One part is that we need to make sure that eventual master will be
created before its slaves, so we need to walk the propagation
tree in a different order - by peer groups. And iterate through
the peers before dealing with the next group.
Another thing is finding the (earlier) copy that will be a master
of one we are about to create; to do that we are (temporary) marking
the masters of mountpoints we are attaching the copies to.
Either we are in a peer of the last mountpoint we'd dealt with,
or we have the following situation: we are attaching to mountpoint M,
the last copy S_0 had been attached to M_0 and there are sequences
S_0...S_n, M_0...M_n such that S_{i+1} is a master of S_{i},
S_{i} mounted on M{i} and we need to create a slave of the first S_{k}
such that M is getting propagation from M_{k}. It means that the master
of M_{k} will be among the sequence of masters of M. On the
other hand, the nearest marked node in that sequence will either
be the master of M_{k} or the master of M_{k-1} (the latter -
in the case if M_{k-1} is a slave of something M gets propagation
from, but in a wrong peer group).
So we go through the sequence of masters of M until we find
a marked one (P). Let N be the one before it. Then we go through
the sequence of masters of S_0 until we find one (say, S) mounted
on a node D that has P as master and check if D is a peer of N.
If it is, S will be the master of new copy, if not - the master of S
will be.
That's it for the hard part; the rest is fairly simple. Iterator
is in next_group(), handling of one prospective mountpoint is
propagate_one().
It seems to survive all tests and gives a noticably better performance
than the current mainline for setups that are seriously using shared
subtrees.
Cc: stable@vger.kernel.org
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
2014-02-27 18:35:45 +04:00
break ;
2010-01-16 21:28:47 +03:00
}
2016-05-05 17:29:29 +03:00
do {
struct mount * parent = last_source - > mnt_parent ;
if ( last_source = = first_source )
break ;
done = parent - > mnt_master = = p ;
if ( done & & peers ( n , parent ) )
break ;
last_source = last_source - > mnt_master ;
} while ( ! done ) ;
smarter propagate_mnt()
The current mainline has copies propagated to *all* nodes, then
tears down the copies we made for nodes that do not contain
counterparts of the desired mountpoint. That sets the right
propagation graph for the copies (at teardown time we move
the slaves of removed node to a surviving peer or directly
to master), but we end up paying a fairly steep price in
useless allocations. It's fairly easy to create a situation
where N calls of mount(2) create exactly N bindings, with
O(N^2) vfsmounts allocated and freed in process.
Fortunately, it is possible to avoid those allocations/freeings.
The trick is to create copies in the right order and find which
one would've eventually become a master with the current algorithm.
It turns out to be possible in O(nodes getting propagation) time
and with no extra allocations at all.
One part is that we need to make sure that eventual master will be
created before its slaves, so we need to walk the propagation
tree in a different order - by peer groups. And iterate through
the peers before dealing with the next group.
Another thing is finding the (earlier) copy that will be a master
of one we are about to create; to do that we are (temporary) marking
the masters of mountpoints we are attaching the copies to.
Either we are in a peer of the last mountpoint we'd dealt with,
or we have the following situation: we are attaching to mountpoint M,
the last copy S_0 had been attached to M_0 and there are sequences
S_0...S_n, M_0...M_n such that S_{i+1} is a master of S_{i},
S_{i} mounted on M{i} and we need to create a slave of the first S_{k}
such that M is getting propagation from M_{k}. It means that the master
of M_{k} will be among the sequence of masters of M. On the
other hand, the nearest marked node in that sequence will either
be the master of M_{k} or the master of M_{k-1} (the latter -
in the case if M_{k-1} is a slave of something M gets propagation
from, but in a wrong peer group).
So we go through the sequence of masters of M until we find
a marked one (P). Let N be the one before it. Then we go through
the sequence of masters of S_0 until we find one (say, S) mounted
on a node D that has P as master and check if D is a peer of N.
If it is, S will be the master of new copy, if not - the master of S
will be.
That's it for the hard part; the rest is fairly simple. Iterator
is in next_group(), handling of one prospective mountpoint is
propagate_one().
It seems to survive all tests and gives a noticably better performance
than the current mainline for setups that are seriously using shared
subtrees.
Cc: stable@vger.kernel.org
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
2014-02-27 18:35:45 +04:00
type = CL_SLAVE ;
/* beginning of peer group among the slaves? */
if ( IS_MNT_SHARED ( m ) )
type | = CL_MAKE_SHARED ;
2005-11-08 01:21:01 +03:00
}
smarter propagate_mnt()
The current mainline has copies propagated to *all* nodes, then
tears down the copies we made for nodes that do not contain
counterparts of the desired mountpoint. That sets the right
propagation graph for the copies (at teardown time we move
the slaves of removed node to a surviving peer or directly
to master), but we end up paying a fairly steep price in
useless allocations. It's fairly easy to create a situation
where N calls of mount(2) create exactly N bindings, with
O(N^2) vfsmounts allocated and freed in process.
Fortunately, it is possible to avoid those allocations/freeings.
The trick is to create copies in the right order and find which
one would've eventually become a master with the current algorithm.
It turns out to be possible in O(nodes getting propagation) time
and with no extra allocations at all.
One part is that we need to make sure that eventual master will be
created before its slaves, so we need to walk the propagation
tree in a different order - by peer groups. And iterate through
the peers before dealing with the next group.
Another thing is finding the (earlier) copy that will be a master
of one we are about to create; to do that we are (temporary) marking
the masters of mountpoints we are attaching the copies to.
Either we are in a peer of the last mountpoint we'd dealt with,
or we have the following situation: we are attaching to mountpoint M,
the last copy S_0 had been attached to M_0 and there are sequences
S_0...S_n, M_0...M_n such that S_{i+1} is a master of S_{i},
S_{i} mounted on M{i} and we need to create a slave of the first S_{k}
such that M is getting propagation from M_{k}. It means that the master
of M_{k} will be among the sequence of masters of M. On the
other hand, the nearest marked node in that sequence will either
be the master of M_{k} or the master of M_{k-1} (the latter -
in the case if M_{k-1} is a slave of something M gets propagation
from, but in a wrong peer group).
So we go through the sequence of masters of M until we find
a marked one (P). Let N be the one before it. Then we go through
the sequence of masters of S_0 until we find one (say, S) mounted
on a node D that has P as master and check if D is a peer of N.
If it is, S will be the master of new copy, if not - the master of S
will be.
That's it for the hard part; the rest is fairly simple. Iterator
is in next_group(), handling of one prospective mountpoint is
propagate_one().
It seems to survive all tests and gives a noticably better performance
than the current mainline for setups that are seriously using shared
subtrees.
Cc: stable@vger.kernel.org
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
2014-02-27 18:35:45 +04:00
/* Notice when we are propagating across user namespaces */
if ( m - > mnt_ns - > user_ns ! = user_ns )
type | = CL_UNPRIVILEGED ;
child = copy_tree ( last_source , last_source - > mnt . mnt_root , type ) ;
if ( IS_ERR ( child ) )
return PTR_ERR ( child ) ;
2014-10-08 03:22:52 +04:00
child - > mnt . mnt_flags & = ~ MNT_LOCKED ;
smarter propagate_mnt()
The current mainline has copies propagated to *all* nodes, then
tears down the copies we made for nodes that do not contain
counterparts of the desired mountpoint. That sets the right
propagation graph for the copies (at teardown time we move
the slaves of removed node to a surviving peer or directly
to master), but we end up paying a fairly steep price in
useless allocations. It's fairly easy to create a situation
where N calls of mount(2) create exactly N bindings, with
O(N^2) vfsmounts allocated and freed in process.
Fortunately, it is possible to avoid those allocations/freeings.
The trick is to create copies in the right order and find which
one would've eventually become a master with the current algorithm.
It turns out to be possible in O(nodes getting propagation) time
and with no extra allocations at all.
One part is that we need to make sure that eventual master will be
created before its slaves, so we need to walk the propagation
tree in a different order - by peer groups. And iterate through
the peers before dealing with the next group.
Another thing is finding the (earlier) copy that will be a master
of one we are about to create; to do that we are (temporary) marking
the masters of mountpoints we are attaching the copies to.
Either we are in a peer of the last mountpoint we'd dealt with,
or we have the following situation: we are attaching to mountpoint M,
the last copy S_0 had been attached to M_0 and there are sequences
S_0...S_n, M_0...M_n such that S_{i+1} is a master of S_{i},
S_{i} mounted on M{i} and we need to create a slave of the first S_{k}
such that M is getting propagation from M_{k}. It means that the master
of M_{k} will be among the sequence of masters of M. On the
other hand, the nearest marked node in that sequence will either
be the master of M_{k} or the master of M_{k-1} (the latter -
in the case if M_{k-1} is a slave of something M gets propagation
from, but in a wrong peer group).
So we go through the sequence of masters of M until we find
a marked one (P). Let N be the one before it. Then we go through
the sequence of masters of S_0 until we find one (say, S) mounted
on a node D that has P as master and check if D is a peer of N.
If it is, S will be the master of new copy, if not - the master of S
will be.
That's it for the hard part; the rest is fairly simple. Iterator
is in next_group(), handling of one prospective mountpoint is
propagate_one().
It seems to survive all tests and gives a noticably better performance
than the current mainline for setups that are seriously using shared
subtrees.
Cc: stable@vger.kernel.org
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
2014-02-27 18:35:45 +04:00
mnt_set_mountpoint ( m , mp , child ) ;
last_dest = m ;
last_source = child ;
if ( m - > mnt_master ! = dest_master ) {
read_seqlock_excl ( & mount_lock ) ;
SET_MNT_MARK ( m - > mnt_master ) ;
read_sequnlock_excl ( & mount_lock ) ;
}
hlist_add_head ( & child - > mnt_hash , list ) ;
2016-09-28 08:27:17 +03:00
return count_mounts ( m - > mnt_ns , child ) ;
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 .
*/
2013-03-15 18:53:28 +04:00
int propagate_mnt ( struct mount * dest_mnt , struct mountpoint * dest_mp ,
2014-03-21 05:10:51 +04:00
struct mount * source_mnt , struct hlist_head * tree_list )
2005-11-08 01:19:50 +03:00
{
smarter propagate_mnt()
The current mainline has copies propagated to *all* nodes, then
tears down the copies we made for nodes that do not contain
counterparts of the desired mountpoint. That sets the right
propagation graph for the copies (at teardown time we move
the slaves of removed node to a surviving peer or directly
to master), but we end up paying a fairly steep price in
useless allocations. It's fairly easy to create a situation
where N calls of mount(2) create exactly N bindings, with
O(N^2) vfsmounts allocated and freed in process.
Fortunately, it is possible to avoid those allocations/freeings.
The trick is to create copies in the right order and find which
one would've eventually become a master with the current algorithm.
It turns out to be possible in O(nodes getting propagation) time
and with no extra allocations at all.
One part is that we need to make sure that eventual master will be
created before its slaves, so we need to walk the propagation
tree in a different order - by peer groups. And iterate through
the peers before dealing with the next group.
Another thing is finding the (earlier) copy that will be a master
of one we are about to create; to do that we are (temporary) marking
the masters of mountpoints we are attaching the copies to.
Either we are in a peer of the last mountpoint we'd dealt with,
or we have the following situation: we are attaching to mountpoint M,
the last copy S_0 had been attached to M_0 and there are sequences
S_0...S_n, M_0...M_n such that S_{i+1} is a master of S_{i},
S_{i} mounted on M{i} and we need to create a slave of the first S_{k}
such that M is getting propagation from M_{k}. It means that the master
of M_{k} will be among the sequence of masters of M. On the
other hand, the nearest marked node in that sequence will either
be the master of M_{k} or the master of M_{k-1} (the latter -
in the case if M_{k-1} is a slave of something M gets propagation
from, but in a wrong peer group).
So we go through the sequence of masters of M until we find
a marked one (P). Let N be the one before it. Then we go through
the sequence of masters of S_0 until we find one (say, S) mounted
on a node D that has P as master and check if D is a peer of N.
If it is, S will be the master of new copy, if not - the master of S
will be.
That's it for the hard part; the rest is fairly simple. Iterator
is in next_group(), handling of one prospective mountpoint is
propagate_one().
It seems to survive all tests and gives a noticably better performance
than the current mainline for setups that are seriously using shared
subtrees.
Cc: stable@vger.kernel.org
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
2014-02-27 18:35:45 +04:00
struct mount * m , * n ;
2005-11-08 01:19:50 +03:00
int ret = 0 ;
2013-03-22 15:08:05 +04:00
smarter propagate_mnt()
The current mainline has copies propagated to *all* nodes, then
tears down the copies we made for nodes that do not contain
counterparts of the desired mountpoint. That sets the right
propagation graph for the copies (at teardown time we move
the slaves of removed node to a surviving peer or directly
to master), but we end up paying a fairly steep price in
useless allocations. It's fairly easy to create a situation
where N calls of mount(2) create exactly N bindings, with
O(N^2) vfsmounts allocated and freed in process.
Fortunately, it is possible to avoid those allocations/freeings.
The trick is to create copies in the right order and find which
one would've eventually become a master with the current algorithm.
It turns out to be possible in O(nodes getting propagation) time
and with no extra allocations at all.
One part is that we need to make sure that eventual master will be
created before its slaves, so we need to walk the propagation
tree in a different order - by peer groups. And iterate through
the peers before dealing with the next group.
Another thing is finding the (earlier) copy that will be a master
of one we are about to create; to do that we are (temporary) marking
the masters of mountpoints we are attaching the copies to.
Either we are in a peer of the last mountpoint we'd dealt with,
or we have the following situation: we are attaching to mountpoint M,
the last copy S_0 had been attached to M_0 and there are sequences
S_0...S_n, M_0...M_n such that S_{i+1} is a master of S_{i},
S_{i} mounted on M{i} and we need to create a slave of the first S_{k}
such that M is getting propagation from M_{k}. It means that the master
of M_{k} will be among the sequence of masters of M. On the
other hand, the nearest marked node in that sequence will either
be the master of M_{k} or the master of M_{k-1} (the latter -
in the case if M_{k-1} is a slave of something M gets propagation
from, but in a wrong peer group).
So we go through the sequence of masters of M until we find
a marked one (P). Let N be the one before it. Then we go through
the sequence of masters of S_0 until we find one (say, S) mounted
on a node D that has P as master and check if D is a peer of N.
If it is, S will be the master of new copy, if not - the master of S
will be.
That's it for the hard part; the rest is fairly simple. Iterator
is in next_group(), handling of one prospective mountpoint is
propagate_one().
It seems to survive all tests and gives a noticably better performance
than the current mainline for setups that are seriously using shared
subtrees.
Cc: stable@vger.kernel.org
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
2014-02-27 18:35:45 +04:00
/*
* we don ' t want to bother passing tons of arguments to
* propagate_one ( ) ; everything is serialized by namespace_sem ,
* so globals will do just fine .
*/
user_ns = current - > nsproxy - > mnt_ns - > user_ns ;
last_dest = dest_mnt ;
2016-05-05 17:29:29 +03:00
first_source = source_mnt ;
smarter propagate_mnt()
The current mainline has copies propagated to *all* nodes, then
tears down the copies we made for nodes that do not contain
counterparts of the desired mountpoint. That sets the right
propagation graph for the copies (at teardown time we move
the slaves of removed node to a surviving peer or directly
to master), but we end up paying a fairly steep price in
useless allocations. It's fairly easy to create a situation
where N calls of mount(2) create exactly N bindings, with
O(N^2) vfsmounts allocated and freed in process.
Fortunately, it is possible to avoid those allocations/freeings.
The trick is to create copies in the right order and find which
one would've eventually become a master with the current algorithm.
It turns out to be possible in O(nodes getting propagation) time
and with no extra allocations at all.
One part is that we need to make sure that eventual master will be
created before its slaves, so we need to walk the propagation
tree in a different order - by peer groups. And iterate through
the peers before dealing with the next group.
Another thing is finding the (earlier) copy that will be a master
of one we are about to create; to do that we are (temporary) marking
the masters of mountpoints we are attaching the copies to.
Either we are in a peer of the last mountpoint we'd dealt with,
or we have the following situation: we are attaching to mountpoint M,
the last copy S_0 had been attached to M_0 and there are sequences
S_0...S_n, M_0...M_n such that S_{i+1} is a master of S_{i},
S_{i} mounted on M{i} and we need to create a slave of the first S_{k}
such that M is getting propagation from M_{k}. It means that the master
of M_{k} will be among the sequence of masters of M. On the
other hand, the nearest marked node in that sequence will either
be the master of M_{k} or the master of M_{k-1} (the latter -
in the case if M_{k-1} is a slave of something M gets propagation
from, but in a wrong peer group).
So we go through the sequence of masters of M until we find
a marked one (P). Let N be the one before it. Then we go through
the sequence of masters of S_0 until we find one (say, S) mounted
on a node D that has P as master and check if D is a peer of N.
If it is, S will be the master of new copy, if not - the master of S
will be.
That's it for the hard part; the rest is fairly simple. Iterator
is in next_group(), handling of one prospective mountpoint is
propagate_one().
It seems to survive all tests and gives a noticably better performance
than the current mainline for setups that are seriously using shared
subtrees.
Cc: stable@vger.kernel.org
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
2014-02-27 18:35:45 +04:00
last_source = source_mnt ;
mp = dest_mp ;
list = tree_list ;
dest_master = dest_mnt - > mnt_master ;
/* all peers of dest_mnt, except dest_mnt itself */
for ( n = next_peer ( dest_mnt ) ; n ! = dest_mnt ; n = next_peer ( n ) ) {
ret = propagate_one ( n ) ;
if ( ret )
2005-11-08 01:19:50 +03:00
goto out ;
smarter propagate_mnt()
The current mainline has copies propagated to *all* nodes, then
tears down the copies we made for nodes that do not contain
counterparts of the desired mountpoint. That sets the right
propagation graph for the copies (at teardown time we move
the slaves of removed node to a surviving peer or directly
to master), but we end up paying a fairly steep price in
useless allocations. It's fairly easy to create a situation
where N calls of mount(2) create exactly N bindings, with
O(N^2) vfsmounts allocated and freed in process.
Fortunately, it is possible to avoid those allocations/freeings.
The trick is to create copies in the right order and find which
one would've eventually become a master with the current algorithm.
It turns out to be possible in O(nodes getting propagation) time
and with no extra allocations at all.
One part is that we need to make sure that eventual master will be
created before its slaves, so we need to walk the propagation
tree in a different order - by peer groups. And iterate through
the peers before dealing with the next group.
Another thing is finding the (earlier) copy that will be a master
of one we are about to create; to do that we are (temporary) marking
the masters of mountpoints we are attaching the copies to.
Either we are in a peer of the last mountpoint we'd dealt with,
or we have the following situation: we are attaching to mountpoint M,
the last copy S_0 had been attached to M_0 and there are sequences
S_0...S_n, M_0...M_n such that S_{i+1} is a master of S_{i},
S_{i} mounted on M{i} and we need to create a slave of the first S_{k}
such that M is getting propagation from M_{k}. It means that the master
of M_{k} will be among the sequence of masters of M. On the
other hand, the nearest marked node in that sequence will either
be the master of M_{k} or the master of M_{k-1} (the latter -
in the case if M_{k-1} is a slave of something M gets propagation
from, but in a wrong peer group).
So we go through the sequence of masters of M until we find
a marked one (P). Let N be the one before it. Then we go through
the sequence of masters of S_0 until we find one (say, S) mounted
on a node D that has P as master and check if D is a peer of N.
If it is, S will be the master of new copy, if not - the master of S
will be.
That's it for the hard part; the rest is fairly simple. Iterator
is in next_group(), handling of one prospective mountpoint is
propagate_one().
It seems to survive all tests and gives a noticably better performance
than the current mainline for setups that are seriously using shared
subtrees.
Cc: stable@vger.kernel.org
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
2014-02-27 18:35:45 +04:00
}
2005-11-08 01:19:50 +03:00
smarter propagate_mnt()
The current mainline has copies propagated to *all* nodes, then
tears down the copies we made for nodes that do not contain
counterparts of the desired mountpoint. That sets the right
propagation graph for the copies (at teardown time we move
the slaves of removed node to a surviving peer or directly
to master), but we end up paying a fairly steep price in
useless allocations. It's fairly easy to create a situation
where N calls of mount(2) create exactly N bindings, with
O(N^2) vfsmounts allocated and freed in process.
Fortunately, it is possible to avoid those allocations/freeings.
The trick is to create copies in the right order and find which
one would've eventually become a master with the current algorithm.
It turns out to be possible in O(nodes getting propagation) time
and with no extra allocations at all.
One part is that we need to make sure that eventual master will be
created before its slaves, so we need to walk the propagation
tree in a different order - by peer groups. And iterate through
the peers before dealing with the next group.
Another thing is finding the (earlier) copy that will be a master
of one we are about to create; to do that we are (temporary) marking
the masters of mountpoints we are attaching the copies to.
Either we are in a peer of the last mountpoint we'd dealt with,
or we have the following situation: we are attaching to mountpoint M,
the last copy S_0 had been attached to M_0 and there are sequences
S_0...S_n, M_0...M_n such that S_{i+1} is a master of S_{i},
S_{i} mounted on M{i} and we need to create a slave of the first S_{k}
such that M is getting propagation from M_{k}. It means that the master
of M_{k} will be among the sequence of masters of M. On the
other hand, the nearest marked node in that sequence will either
be the master of M_{k} or the master of M_{k-1} (the latter -
in the case if M_{k-1} is a slave of something M gets propagation
from, but in a wrong peer group).
So we go through the sequence of masters of M until we find
a marked one (P). Let N be the one before it. Then we go through
the sequence of masters of S_0 until we find one (say, S) mounted
on a node D that has P as master and check if D is a peer of N.
If it is, S will be the master of new copy, if not - the master of S
will be.
That's it for the hard part; the rest is fairly simple. Iterator
is in next_group(), handling of one prospective mountpoint is
propagate_one().
It seems to survive all tests and gives a noticably better performance
than the current mainline for setups that are seriously using shared
subtrees.
Cc: stable@vger.kernel.org
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
2014-02-27 18:35:45 +04:00
/* all slave groups */
for ( m = next_group ( dest_mnt , dest_mnt ) ; m ;
m = next_group ( m , dest_mnt ) ) {
/* everything in that slave group */
n = m ;
do {
ret = propagate_one ( n ) ;
if ( ret )
goto out ;
n = next_peer ( n ) ;
} while ( n ! = m ) ;
2005-11-08 01:19:50 +03:00
}
out :
smarter propagate_mnt()
The current mainline has copies propagated to *all* nodes, then
tears down the copies we made for nodes that do not contain
counterparts of the desired mountpoint. That sets the right
propagation graph for the copies (at teardown time we move
the slaves of removed node to a surviving peer or directly
to master), but we end up paying a fairly steep price in
useless allocations. It's fairly easy to create a situation
where N calls of mount(2) create exactly N bindings, with
O(N^2) vfsmounts allocated and freed in process.
Fortunately, it is possible to avoid those allocations/freeings.
The trick is to create copies in the right order and find which
one would've eventually become a master with the current algorithm.
It turns out to be possible in O(nodes getting propagation) time
and with no extra allocations at all.
One part is that we need to make sure that eventual master will be
created before its slaves, so we need to walk the propagation
tree in a different order - by peer groups. And iterate through
the peers before dealing with the next group.
Another thing is finding the (earlier) copy that will be a master
of one we are about to create; to do that we are (temporary) marking
the masters of mountpoints we are attaching the copies to.
Either we are in a peer of the last mountpoint we'd dealt with,
or we have the following situation: we are attaching to mountpoint M,
the last copy S_0 had been attached to M_0 and there are sequences
S_0...S_n, M_0...M_n such that S_{i+1} is a master of S_{i},
S_{i} mounted on M{i} and we need to create a slave of the first S_{k}
such that M is getting propagation from M_{k}. It means that the master
of M_{k} will be among the sequence of masters of M. On the
other hand, the nearest marked node in that sequence will either
be the master of M_{k} or the master of M_{k-1} (the latter -
in the case if M_{k-1} is a slave of something M gets propagation
from, but in a wrong peer group).
So we go through the sequence of masters of M until we find
a marked one (P). Let N be the one before it. Then we go through
the sequence of masters of S_0 until we find one (say, S) mounted
on a node D that has P as master and check if D is a peer of N.
If it is, S will be the master of new copy, if not - the master of S
will be.
That's it for the hard part; the rest is fairly simple. Iterator
is in next_group(), handling of one prospective mountpoint is
propagate_one().
It seems to survive all tests and gives a noticably better performance
than the current mainline for setups that are seriously using shared
subtrees.
Cc: stable@vger.kernel.org
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
2014-02-27 18:35:45 +04:00
read_seqlock_excl ( & mount_lock ) ;
hlist_for_each_entry ( n , tree_list , mnt_hash ) {
m = n - > mnt_parent ;
if ( m - > mnt_master ! = dest_mnt - > mnt_master )
CLEAR_MNT_MARK ( m - > mnt_master ) ;
2005-11-08 01:19:50 +03:00
}
smarter propagate_mnt()
The current mainline has copies propagated to *all* nodes, then
tears down the copies we made for nodes that do not contain
counterparts of the desired mountpoint. That sets the right
propagation graph for the copies (at teardown time we move
the slaves of removed node to a surviving peer or directly
to master), but we end up paying a fairly steep price in
useless allocations. It's fairly easy to create a situation
where N calls of mount(2) create exactly N bindings, with
O(N^2) vfsmounts allocated and freed in process.
Fortunately, it is possible to avoid those allocations/freeings.
The trick is to create copies in the right order and find which
one would've eventually become a master with the current algorithm.
It turns out to be possible in O(nodes getting propagation) time
and with no extra allocations at all.
One part is that we need to make sure that eventual master will be
created before its slaves, so we need to walk the propagation
tree in a different order - by peer groups. And iterate through
the peers before dealing with the next group.
Another thing is finding the (earlier) copy that will be a master
of one we are about to create; to do that we are (temporary) marking
the masters of mountpoints we are attaching the copies to.
Either we are in a peer of the last mountpoint we'd dealt with,
or we have the following situation: we are attaching to mountpoint M,
the last copy S_0 had been attached to M_0 and there are sequences
S_0...S_n, M_0...M_n such that S_{i+1} is a master of S_{i},
S_{i} mounted on M{i} and we need to create a slave of the first S_{k}
such that M is getting propagation from M_{k}. It means that the master
of M_{k} will be among the sequence of masters of M. On the
other hand, the nearest marked node in that sequence will either
be the master of M_{k} or the master of M_{k-1} (the latter -
in the case if M_{k-1} is a slave of something M gets propagation
from, but in a wrong peer group).
So we go through the sequence of masters of M until we find
a marked one (P). Let N be the one before it. Then we go through
the sequence of masters of S_0 until we find one (say, S) mounted
on a node D that has P as master and check if D is a peer of N.
If it is, S will be the master of new copy, if not - the master of S
will be.
That's it for the hard part; the rest is fairly simple. Iterator
is in next_group(), handling of one prospective mountpoint is
propagate_one().
It seems to survive all tests and gives a noticably better performance
than the current mainline for setups that are seriously using shared
subtrees.
Cc: stable@vger.kernel.org
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
2014-02-27 18:35:45 +04:00
read_sequnlock_excl ( & mount_lock ) ;
2005-11-08 01:19:50 +03:00
return ret ;
}
2005-11-08 01:20:17 +03:00
/*
* return true if the refcount is greater than count
*/
2011-11-25 06:35:16 +04:00
static inline int do_refcount_check ( struct mount * mnt , int count )
2005-11-08 01:20:17 +03:00
{
2013-09-29 07:10:55 +04:00
return mnt_get_count ( mnt ) > count ;
2005-11-08 01:20:17 +03:00
}
/*
* 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
*/
2011-11-25 06:35:16 +04:00
int propagate_mount_busy ( struct mount * mnt , int refcnt )
2005-11-08 01:20:17 +03:00
{
2011-11-25 08:56:26 +04:00
struct mount * m , * child ;
2011-11-25 07:19:58 +04:00
struct mount * parent = mnt - > mnt_parent ;
2005-11-08 01:20:17 +03:00
int ret = 0 ;
2011-11-25 07:19:58 +04:00
if ( mnt = = parent )
2005-11-08 01:20:17 +03:00
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
*/
2011-11-25 08:24:33 +04:00
if ( ! list_empty ( & mnt - > mnt_mounts ) | | do_refcount_check ( mnt , refcnt ) )
2005-11-08 01:20:17 +03:00
return 1 ;
2011-11-25 08:56:26 +04:00
for ( m = propagation_next ( parent , parent ) ; m ;
m = propagation_next ( m , parent ) ) {
2013-10-02 00:11:26 +04:00
child = __lookup_mnt_last ( & m - > mnt , mnt - > mnt_mountpoint ) ;
2011-11-25 08:24:33 +04:00
if ( child & & list_empty ( & child - > mnt_mounts ) & &
2011-11-25 06:35:16 +04:00
( ret = do_refcount_check ( child , 1 ) ) )
2005-11-08 01:20:17 +03:00
break ;
}
return ret ;
}
2015-01-03 14:39:35 +03:00
/*
* Clear MNT_LOCKED when it can be shown to be safe .
*
* mount_lock lock must be held for write
*/
void propagate_mount_unlock ( struct mount * mnt )
{
struct mount * parent = mnt - > mnt_parent ;
struct mount * m , * child ;
BUG_ON ( parent = = mnt ) ;
for ( m = propagation_next ( parent , parent ) ; m ;
m = propagation_next ( m , parent ) ) {
child = __lookup_mnt_last ( & m - > mnt , mnt - > mnt_mountpoint ) ;
if ( child )
child - > mnt . mnt_flags & = ~ MNT_LOCKED ;
}
}
2015-01-05 22:38:04 +03:00
/*
* Mark all mounts that the MNT_LOCKED logic will allow to be unmounted .
*/
static void mark_umount_candidates ( struct mount * mnt )
{
struct mount * parent = mnt - > mnt_parent ;
struct mount * m ;
BUG_ON ( parent = = mnt ) ;
for ( m = propagation_next ( parent , parent ) ; m ;
m = propagation_next ( m , parent ) ) {
struct mount * child = __lookup_mnt_last ( & m - > mnt ,
mnt - > mnt_mountpoint ) ;
if ( child & & ( ! IS_MNT_LOCKED ( child ) | | IS_MNT_MARKED ( m ) ) ) {
SET_MNT_MARK ( child ) ;
}
}
}
2005-11-08 01:20:17 +03:00
/*
* NOTE : unmounting ' mnt ' naturally propagates to all other mounts its
* parent propagates to .
*/
2011-11-25 03:25:28 +04:00
static void __propagate_umount ( struct mount * mnt )
2005-11-08 01:20:17 +03:00
{
2011-11-25 07:19:58 +04:00
struct mount * parent = mnt - > mnt_parent ;
2011-11-25 08:56:26 +04:00
struct mount * m ;
2005-11-08 01:20:17 +03:00
2011-11-25 07:19:58 +04:00
BUG_ON ( parent = = mnt ) ;
2005-11-08 01:20:17 +03:00
2011-11-25 08:56:26 +04:00
for ( m = propagation_next ( parent , parent ) ; m ;
m = propagation_next ( m , parent ) ) {
2005-11-08 01:20:17 +03:00
2013-10-02 00:11:26 +04:00
struct mount * child = __lookup_mnt_last ( & m - > mnt ,
mnt - > mnt_mountpoint ) ;
2005-11-08 01:20:17 +03:00
/*
2015-01-05 22:38:04 +03:00
* umount the child only if the child has no children
* and the child is marked safe to unmount .
2005-11-08 01:20:17 +03:00
*/
2015-01-05 22:38:04 +03:00
if ( ! child | | ! IS_MNT_MARKED ( child ) )
continue ;
CLEAR_MNT_MARK ( child ) ;
if ( list_empty ( & child - > mnt_mounts ) ) {
2014-08-18 23:09:26 +04:00
list_del_init ( & child - > mnt_child ) ;
2014-12-23 03:30:08 +03:00
child - > mnt . mnt_flags | = MNT_UMOUNT ;
2014-12-18 22:10:48 +03:00
list_move_tail ( & child - > mnt_list , & mnt - > mnt_list ) ;
2014-03-21 05:10:51 +04:00
}
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
*/
2014-12-18 22:10:48 +03:00
int propagate_umount ( struct list_head * list )
2005-11-08 01:20:17 +03:00
{
2011-11-25 03:25:28 +04:00
struct mount * mnt ;
2005-11-08 01:20:17 +03:00
2015-01-05 22:38:04 +03:00
list_for_each_entry_reverse ( mnt , list , mnt_list )
mark_umount_candidates ( mnt ) ;
2014-12-18 22:10:48 +03:00
list_for_each_entry ( mnt , list , mnt_list )
2005-11-08 01:20:17 +03:00
__propagate_umount ( mnt ) ;
return 0 ;
}