Linux Newbie help
 help / color / mirror / Atom feed
From: "Rajat Jain" <rajat.noida.india@gmail.com>
To: "GAggarwal@in.safenet-inc.com" <GAggarwal@in.safenet-inc.com>
Cc: kernelnewbies@nl.linux.org, linux-newbie@vger.kernel.org
Subject: Re: Need for a new spinlock API?
Date: Wed, 4 Apr 2007 10:40:25 +0530	[thread overview]
Message-ID: <b115cb5f0704032210s19c9ba5ehe9f4783d0505a138@mail.gmail.com> (raw)
In-Reply-To: <D45AC362EAFF2F47891E71637D192ABF01D377FF@INEXCH1>

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
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

  reply	other threads:[~2007-04-04  5:10 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-04  3:50 Need for a new spinlock API? GAggarwal
2007-04-04  5:10 ` Rajat Jain [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-04-04  5:34 GAggarwal
2007-03-21  3:53 Rajat Jain
2007-03-21  7:32 ` Arjan van de Ven
2007-03-21 18:59   ` anubhav rakshit
2007-03-21 21:03     ` Arjan van de Ven
2007-03-21 23:07       ` Tzahi Fadida
2007-03-22  1:12       ` Rajat Jain
2007-03-22  4:17         ` Ajay Singh (ajaysi)
2007-03-22  4:33           ` Rajat Jain
2007-03-22  4:55             ` Ajay Singh (ajaysi)
2007-03-22  5:59               ` Rajat Jain
2007-03-22  8:51                 ` Arjan van de Ven
2007-03-22  8:50         ` Arjan van de Ven
2007-04-04  3:26   ` Rajat Jain
2007-04-04  5:38     ` anubhav rakshit

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=b115cb5f0704032210s19c9ba5ehe9f4783d0505a138@mail.gmail.com \
    --to=rajat.noida.india@gmail.com \
    --cc=GAggarwal@in.safenet-inc.com \
    --cc=kernelnewbies@nl.linux.org \
    --cc=linux-newbie@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox