On Mon, 2008-02-18 at 17:10 +0100, Miklos Szeredi wrote:
>
> > + /*
> > + * We don't have to hold all of the locks at the
> > + * same time here because we know that we're the
> > + * last reference to mnt and that no new writers
> > + * can come in.
> > + */
> > +
On Mon, 2008-02-18 at 17:10 +0100, Miklos Szeredi wrote:
+ /*
+ * We don't have to hold all of the locks at the
+ * same time here because we know that we're the
+ * last reference to mnt and that no new writers
+ * can come in.
+ */
+
> @@ -327,7 +514,30 @@ static struct vfsmount *clone_mnt(struct
>
> static inline void __mntput(struct vfsmount *mnt)
> {
> + int cpu;
> struct super_block *sb = mnt->mnt_sb;
> + /*
> + * We don't have to hold all of the locks at the
> + * same time here because we know
@@ -327,7 +514,30 @@ static struct vfsmount *clone_mnt(struct
static inline void __mntput(struct vfsmount *mnt)
{
+ int cpu;
struct super_block *sb = mnt-mnt_sb;
+ /*
+ * We don't have to hold all of the locks at the
+ * same time here because we know that
This is the real meat of the entire series. It actually
implements the tracking of the number of writers to a mount.
However, it causes scalability problems because there can be
hundreds of cpus doing open()/close() on files on the same mnt at
the same time. Even an atomic_t in the mnt has
This is the real meat of the entire series. It actually
implements the tracking of the number of writers to a mount.
However, it causes scalability problems because there can be
hundreds of cpus doing open()/close() on files on the same mnt at
the same time. Even an atomic_t in the mnt has
This is the real meat of the entire series. It actually
implements the tracking of the number of writers to a mount.
However, it causes scalability problems because there can be
hundreds of cpus doing open()/close() on files on the same mnt at
the same time. Even an atomic_t in the mnt has
This is the real meat of the entire series. It actually
implements the tracking of the number of writers to a mount.
However, it causes scalability problems because there can be
hundreds of cpus doing open()/close() on files on the same mnt at
the same time. Even an atomic_t in the mnt has
8 matches
Mail list logo
