From: David Woodhouse <dwmw2@infradead.org>
To: joakim.tjernlund@lumentis.se
Cc: "Dave Ellis" <DGE@sixnetio.com>, linux-mtd@lists.infradead.org
Subject: Re: Disk blocks for long periods
Date: Wed, 07 Aug 2002 10:51:44 +0100 [thread overview]
Message-ID: <31147.1028713904@redhat.com> (raw)
In-Reply-To: <IGEFJKJNHJDCBKALBJLLAEIIFFAA.joakim.tjernlund@lumentis.se>
joakim.tjernlund@lumentis.se said:
> Can the JFFS2 layer also use spin_lock() instead of spin_lock_bh()?
> Shold we try not to disable bottom-halves or does it not matter?
Well, the MTD API documentation (in my head) says that the erase completion
callback may be called in bottom-half context (i.e. from a timer), which is
why JFFS2 uses spin_lock_bh().
I suppose we could change that.
--
dwmw2
next prev parent reply other threads:[~2002-08-07 9:51 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-05 18:50 Disk blocks for long periods Dave Ellis
2002-08-06 10:06 ` Joakim Tjernlund
2002-08-06 12:14 ` David Woodhouse
2002-08-06 13:52 ` Jörn Engel
2002-08-06 13:53 ` David Woodhouse
2002-08-06 16:45 ` Joakim Tjernlund
2002-08-07 9:51 ` David Woodhouse [this message]
2002-08-08 7:23 ` Joakim Tjernlund
2002-08-08 8:02 ` David Woodhouse
2002-08-08 8:32 ` Joakim Tjernlund
2002-08-08 8:40 ` David Woodhouse
-- strict thread matches above, loose matches on Subject: below --
2002-08-07 16:42 Dave Ellis
2002-08-08 7:08 ` Joakim Tjernlund
2002-08-08 8:08 ` David Woodhouse
2002-08-08 9:15 ` Joakim Tjernlund
2002-08-08 9:18 ` David Woodhouse
2002-08-06 20:16 Dave Ellis
2002-08-06 21:06 ` Joakim Tjernlund
2002-08-06 14:53 Dave Ellis
2002-08-06 15:09 ` Joakim Tjernlund
2002-08-07 11:11 ` David Woodhouse
2002-08-05 10:35 MTD Partition problems David Woodhouse
2002-08-05 13:35 ` Disk blocks for long periods Joakim Tjernlund
2002-08-05 13:44 ` David Woodhouse
2002-08-05 13:59 ` Joakim Tjernlund
2002-08-05 14:12 ` David Woodhouse
2002-08-05 14:32 ` Joakim Tjernlund
2002-08-05 14:42 ` David Woodhouse
2002-08-05 21:45 ` Jasmine Strong
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=31147.1028713904@redhat.com \
--to=dwmw2@infradead.org \
--cc=DGE@sixnetio.com \
--cc=joakim.tjernlund@lumentis.se \
--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