From: "Rajat Jain" <rajat.noida.india@gmail.com>
To: kernel mail <kernelnewbies@nl.linux.org>,
newbie <linux-newbie@vger.kernel.org>
Subject: Need for a new spinlock API?
Date: Wed, 21 Mar 2007 09:23:28 +0530 [thread overview]
Message-ID: <b115cb5f0703202053n1b8bfd4bo39cd046e04fb15a2@mail.gmail.com> (raw)
Hi,
We often have a case where a driver wants to access its data structure
in process context as well as in interrupt context (in its ISR). In
such scenarios, we generally use spin_lock_irqsave() to grab the lock
as well as disable all the local interrupts. AFAIK, disabling of local
interrupts is required so as to avoid running your ISR (which needs
the lock) while process context is holding the lock. However, this
also disables any other ISRs (which DO NOT need the lock) on the local
processor.
Isn't this sub-optimal? Shouldn't there be a finer grained locking?
I was wondering if it is possible to have a spin lock API that grabs
the lock and disables ONLY the specified irq on the local processor?
Am I missing something here?
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
next reply other threads:[~2007-03-21 3:53 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-21 3:53 Rajat Jain [this message]
2007-03-21 7:32 ` Need for a new spinlock API? 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
-- strict thread matches above, loose matches on Subject: below --
2007-04-04 3:50 GAggarwal
2007-04-04 5:10 ` Rajat Jain
2007-04-04 5:34 GAggarwal
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=b115cb5f0703202053n1b8bfd4bo39cd046e04fb15a2@mail.gmail.com \
--to=rajat.noida.india@gmail.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