| [Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] |
On Fri, 2003-07-18 at 06:03, Cahill, Ben M wrote:
> Hi all,
>
> I was looking through the "ogfs-redesign" doc, along with some of the memexp and memexpd code ... there seem to be some discrepancies, but I wanted to run them by the list before making changes to the redesign doc.
>
> It looks to me that memexpd is not a "lock server", but merely a "storage server". The memexp lock module can use either DMEP (SCSI hardware-based) or memexpd (server memory/diskstore) interchangeably to store/load lock/LVP info. I can't see that memexpd does anything more than store/load sorts of functions, though. It seems to have no idea of lock states, etc. ... it just serves (load/store) raw information.
>
> It looks to me like all the lock management, and cluster management, is done by the memexp lock modules, on a distributed basis, and not through a central "lock server". It looks like each memexp module can communicate with its peers directly, rather than via a "lock server".
>
> This was a bit of a surprise to see this ... I would like to get a sanity check if anyone would be willing to take a look.
The worst thing in "memexp" is that it need a centre server.(except
using hardware dmep)
Hence there is a single-point-failure.
> -- Ben --
>
> Opinions are mine, not Intel's
--
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}
-------------------------------------------------------
This SF.net email is sponsored by: VM Ware
With VMware you can run multiple operating systems on a single machine.
WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines at the
same time. Free trial click here: http://www.vmware.com/wl/offer/345/0
_______________________________________________
Opengfs-devel mailing list
Opengfs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opengfs-devel