RE: Need for a new spinlock API?

[GAggarwal@IN.Safenet-inc.com]

[-- Attachment #1: Type: text/plain, Size: 1457 bytes --]

Yaa Rajat... I think that will work if datastructure is shared only among
process context thread and one ISR routine.But in case the datastructure is
shared among multiple interrupt context routines say in IRQ handler A and
Tasklet B then you need to use spin_lock_irqsave() routine in IRQ context
too.

--
Gaurav



-----Original Message-----
From: Rajat Jain [mailto:rajat.noida.india@gmail.com]
Sent: Wednesday, April 04, 2007 10:40 AM
To: GAggarwal@in.safenet-inc.com
Cc: kernelnewbies@nl.linux.org; linux-newbie@vger.kernel.org
Subject: Re: Need for a new spinlock API?


On 4/4/07, GAggarwal@in.safenet-inc.com <GAggarwal@in.safenet-inc.com>
wrote:
>
>
> Hi Rajat,
>
> I think spin_lock_irqsave() will fulfill the purpose as otherwise it may
be
> possible that the when a data structure is accessed in process context by
> taking spin_lock and an interrupt comes then the ISR will remain in
forever
> loop waiting for the process context to release the lock result in a
> deadlock situation for a uniprocessor system.

HI Gaurav,

I meant to use spin_lock_irqsave() in process context and spin_lock()
in IRQ context.

Thanks,

Rajat


The information contained in this electronic mail transmission may be privileged and confidential, and therefore, protected from disclosure. If you have received this communication in error, please notify us immediately by replying to this message and deleting it from your computer without copying or disclosing it.

[-- Attachment #2: Type: text/html, Size: 2512 bytes --]