From: Alexandr Andreev <andreev@niisi.msk.ru>
To: Jens Axboe <axboe@suse.de>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Disabling interrupts before block device request call
Date: Mon, 28 May 2001 15:24:14 -0400 [thread overview]
Message-ID: <3B12A5DE.7020408@niisi.msk.ru> (raw)
In-Reply-To: <3B0EE8CF.7040502@niisi.msk.ru> <20010526000119.A23273@suse.de>
Jens Axboe wrote
>
>Even with dropping io_request_lock, it's not recommended to sleep inside
>the request_fn. WIth plugging, you are basically preventing the other
>plugged queues from being run until you return.
>
>You could use a timer or similar to call you on a specified timeout
>instead.
>
Does it mean, that if i need timer interrupts in my block device driver,
i need to do sti() instead of unlock io_request_lock? Is there any
common rule for device drivers in such case?
prev parent reply other threads:[~2001-05-28 11:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
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:24 ` Alexandr Andreev [this message]
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=3B12A5DE.7020408@niisi.msk.ru \
--to=andreev@niisi.msk.ru \
--cc=axboe@suse.de \
--cc=linux-kernel@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