RE: [Opendlm-devel] Checkins to OGFS and ODLM

Actually that is not entirely true.  One of the big culprits is the CCCP
module.  The timer functionality is completely broken and winds up
sending an ACK every clock tick, even when both nodes are sitting idle
doing nothing.  As a result it chews up memory and CPU ("cat
/proc/slabinfo" and look for cccp).  We have a fix for this, which
removes the "timer cache" and utilizes a single timer that turns on and
off properly.  In addition, our throughput went up and our soak tests
didn't die after 24 hours anymore. =20

We have a collection of other fixes that we will be submitting in
another week or so, once we move past our beta deadline.  These fixes
include the cccp timer, cccp duplicate packet issue (might be the cause
of your dir_proc crash), deadlock fixes, migration works again (albeit
performance is horrible), startup/shutdown cleanups, and other misc
fixes. =20

Thanks again Ben for checking in our first patch.  Hopefully we will be
able to fix things over here so we can check-in the second patch (after
the community accepts it of course ;) ).=20

Best Regards,
Don
=20
-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of Aneesh
Kumar KV
Sent: Friday, April 02, 2004 8:52 AM
To: [email protected]
Cc: [email protected]
Subject: Re: [Opendlm-devel] Checkins to OGFS and ODLM

Cahill, Ben M wrote:

>
>Does anyone know why there is *so much LAN traffic* with OpenDLM?  This
>doesn't seem right.  It should be more efficient (less traffic) than
>memexp, at least when a lock is not immediately available (memexp just
>keeps spinning, but OpenDLM should not need to do that, should it?)
....
>
>
>...  But my LAN LEDs keep lighting up *very actively* long after any
>filesystem activity is complete, and it takes longer to do filesystem
>stuff with OpenDLM (vs. memexp).  Hmmm, I'm hoping that there's a
pretty
>serious breach of logic in the OpenDLM code that we can clean up.
> =20
>

If you look at openDLM list archive you will find a smillar discussion=20
regarding openDLM and lan traffic. IIRC it is the locking architecture=20
of OpenDLM the culprit.

-aneesh


--=20
ph: 603-884-5742




-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=3D1470&alloc_id=3D3638&op=3Dcli=
ck
_______________________________________________
Opendlm-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opendlm-devel





-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click