All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: Alexandr Andreev <andreev@niisi.msk.ru>
Cc: "linux-mtd@lists.infrared.org" <linux-mtd@lists.infradead.org>
Subject: Re: Why timer interrupt is disabled?
Date: Fri, 25 May 2001 18:36:14 +0100	[thread overview]
Message-ID: <11416.990812174@redhat.com> (raw)
In-Reply-To: <3B0F0766.1080207@niisi.msk.ru>

andreev@niisi.msk.ru said:
> reemptively. So, we can unlock the io_request_lock in ftl.c, but what
> about double  unlocking? Or, do you want to lock it back after
> proceeding request :)  Is there any conflicts, when we try to unlock
> already unlocked lock?  

You have to lock it again before returning. 

But you really shouldn't be taking my advice on how to write block devices. 
I've been trying to avoid it :)

--
dwmw2

  reply	other threads:[~2001-05-25 17:33 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-25 13:04 Why timer interrupt is disabled? andreev
2001-05-25 13:12 ` David Woodhouse
     [not found]   ` <3B0EE338.1000701@niisi.msk.ru>
2001-05-25 15:17     ` David Woodhouse
2001-05-26  0:17       ` Alexandr Andreev
2001-05-25 16:37         ` David Woodhouse
2001-05-25 17:06           ` Herman Oosthuysen
2001-05-26  1:31           ` Alexandr Andreev
2001-05-25 17:36             ` David Woodhouse [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-05-25 23:20 Disabling interrupts before block device request call Alexandr Andreev
2001-05-25 22:01 ` Jens Axboe
2001-05-28 19:07   ` Why timer interrupt is disabled? Alexandr Andreev
2001-05-28 15:36     ` David Woodhouse

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=11416.990812174@redhat.com \
    --to=dwmw2@infradead.org \
    --cc=andreev@niisi.msk.ru \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.