[openib-general] RE: [PATCH][kdapl] fix spin_lock_irqsave/spi n_unlock_irqrestore i mplementation

[Itamar Rabenstein]

I am not saying that we need it in OpenIb code because it was in SF code 
I said that in OpenIb implementation we need it the same as in SF we need
it.
we must have this lock because for example :
if the same evd will be a CM evd for 2 ep's
each one on different Thread both can try to add an event to the evd in the
same time
there for we need to lock the evd when we take an empty event from one list
(empty list) 
and to unlock it after we add the event to the second list (waiting events
list)
the lock is in one function and the unlock in the second function.

so we need in out OpenIb code and also SF code need it (;-)

 Itamar

> -----Original Message-----
> From: Tom Duffy [mailto:tduffy at sun.com]
> Sent: Thursday, May 19, 2005 11:09 PM
> To: Itamar Rabenstein
> Cc: James Lentini; openib-general
> Subject: Re: [openib-general] RE: [PATCH][kdapl] fix
> spin_lock_irqsave/spin_unlock_irqrestore i mplementation
> 
> 
> On Wed, 2005-05-18 at 22:44 +0300, Itamar Rabenstein wrote:
> > "evd producer locking" is something that we need in openib kdapl
> >  as it was in Source Forge implementation.
> 
> This is not a good excuse.  OpenIB kdapl is a totally different beast
> from the sourceforge implementation and will differ over time.
> 
> -tduffy
>