[ogfs-dev]Re: [Opendlm-devel] Making progress on mounting with ODLM lock module

[Stanley Wang <stanley.wang@xxxxxxxxxxxxxxxxxx>]

> Stanley's removal of a call to release_mount_lock() yesterday got me
> thinking about the internal (to lock module) MOUNT lock.  I'm thinking
> right now that we don't need it; memexp used an internal MOUNT lock to
> determine whether a node was first-to-mount (see ogfs-memexp doc).
As I understood, the mount lock is used to make sure that there is only
one node is doing the mount work in a same time. It serialize all mount
request. Please have a check.

Best Regards,
Stan

>   But
> we're using deadman locks to do the same.  I don't think we need the
> (redundant/useless?) MOUNT lock, so I commented out the
> grab_mount_lock() and release_mount_lock() implementations.  We can
> think about that a little more before totally removing those functions.

> -- Ben --
> 
> 
> 
> -------------------------------------------------------
> SF.Net is sponsored by: Speed Start Your Linux Apps Now.
> Build and deploy apps & Web services for Linux with
> a free DVD software kit from IBM. Click Now!
> http://ads.osdn.com/?ad_id56&alloc_id438&opk
> _______________________________________________
> Opendlm-devel mailing list
> Opendlm-devel@xxxxxxxxxxxxxxxxxxxxx
> https://lists.sourceforge.net/lists/listinfo/opendlm-devel
-- 
Opinions expressed are those of the author and do not represent Intel
Corporation
"gpg --recv-keys --keyserver wwwkeys.pgp.net E1390A7F"
{E1390A7F:3AD1 1B0C 2019 E183 0CFF  55E8 369A 8B75 E139 0A7F}



-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
_______________________________________________
Opengfs-devel mailing list
Opengfs-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/opengfs-devel