public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Linh Dang <linhd@nortelnetworks.com>
To: linux-mtd@lists.infradead.org
Subject: Re: Bottom halves being disabled
Date: Tue, 24 Aug 2004 22:36:28 -0400	[thread overview]
Message-ID: <wn5n00kgd03.fsf@linhd-2.ca.nortel.com> (raw)
In-Reply-To: <1093350246.14552.12435.camel@hades.cambridge.redhat.com> (David Woodhouse's message of "Tue, 24 Aug 2004 13:24:06 +0100")


David Woodhouse <dwmw2@infradead.org> wrote:

> On Tue, 2004-08-24 at 05:09 -0700, Ed Co wrote:
>> Hi All,
>>
>> In the NOR driver code, the spin locks are acquired
>> everywhere with bottom halves disabled using the
>> spin_lock_bh() API. My doubt is why are the bottom
>> halves disabled? (Doesn't that add to the real time
>> latency on the system!)
>>
>> Hoping someone would clear the doubt
>
> Because we intend the erase completion to be asynchronous, hence we
> lock against the timers which may one day check for it. There's no
> real reason we couldn't switch to spin_lock() for now.

Is it safe to convert those spin_locks to mutexes?

-- 
Linh Dang

  reply	other threads:[~2004-08-25  2:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-24 12:09 Bottom halves being disabled Ed Co
2004-08-24 12:24 ` David Woodhouse
2004-08-25  2:36   ` Linh Dang [this message]
2004-08-25  9:38     ` David Woodhouse
2004-08-25 10:48       ` Linh Dang
2004-08-25 10:53         ` David Woodhouse
2004-08-25 12:46           ` Linh Dang
2004-09-09 18:12           ` Hi Latency in do_read_onechip (was Re: Bottom halves being disabled) Linh Dang
2004-08-24 12:28 ` Bottom halves being disabled Josh Boyer

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=wn5n00kgd03.fsf@linhd-2.ca.nortel.com \
    --to=linhd@nortelnetworks.com \
    --cc=linux-mtd@lists.infradead.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