From: David Woodhouse <dwmw2@infradead.org>
To: 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 16:17:36 +0100 [thread overview]
Message-ID: <25506.990803856@redhat.com> (raw)
In-Reply-To: <3B0EE338.1000701@niisi.msk.ru>
andreev@niisi.msk.ru said:
> <br><br></pre></blockquote> I know that JFFS is the better choice, but
> I must use the FTL driver, because there is installed X-server on my
> flash <br> partition... <br>
I don't see the logic. The Compaq iPAQ works quite well with the X-server
in the JFFS2 filesystem.
> <br> I think that unlocking of the io_request_lock inside ftl driver
> is not a good idea, because the do_ftl_request must be <br> atomic.
My understanding is that it's perfectly safe to drop the io_request_lock
as long as we only look at the request at the head of the queue. There's no
need for do_ftl_request to be atomic - and in fact it cannot be atomic
because the flash read and write calls may sleep.
> What about enabling all or only <br> timer interrupts inside
> do_ftl_request. Can you uncomment the sti() in ftl.c in your CVS
> version?<br> <br> <br> </body></html>
If you ensure that it's correct to do so, and provide a patch which
releases the io_request_lock, then I'll certainly consider applying it.
--
dwmw2
next prev parent reply other threads:[~2001-05-25 15:13 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 [this message]
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
[not found] <3B0EE8CF.7040502@niisi.msk.ru>
[not found] ` <20010526000119.A23273@suse.de>
2001-05-28 19:07 ` 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=25506.990803856@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox