From: Arnd Bergmann <arnd@arndb.de>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
Roman Zippel <zippel@linux-m68k.org>,
linux-m68k@vger.kernel.org
Subject: Re: [PATCH 07/18] m68k: remove big kernel lock
Date: Wed, 22 Sep 2010 13:04:45 +0200 [thread overview]
Message-ID: <201009221304.45353.arnd@arndb.de> (raw)
In-Reply-To: <m21v8mkhg7.fsf@igel.home>
On Tuesday 21 September 2010, Andreas Schwab wrote:
>
> Arnd Bergmann <arnd@arndb.de> writes:
>
> > The cache flush code only locks against itself, so there
> > is no excuse to use the BKL here. This replaces it with
> > a local mutex in order to maintain serialization of flushes.
>
> I don't think this needs a lock at all.
>
Quite likely, I just took the most conservative approach.
If you want to queue a patch to drop the BKL from m68k, I'll
happily drop this one from my series.
Arnd
next prev parent reply other threads:[~2010-09-22 11:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1284492909-7147-1-git-send-email-arnd@arndb.de>
2010-09-14 19:34 ` [PATCH 07/18] m68k: remove big kernel lock Arnd Bergmann
2010-09-21 19:46 ` Andreas Schwab
2010-09-22 11:04 ` Arnd Bergmann [this message]
2010-10-16 17:35 ` Geert Uytterhoeven
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=201009221304.45353.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=geert@linux-m68k.org \
--cc=linux-m68k@vger.kernel.org \
--cc=schwab@linux-m68k.org \
--cc=zippel@linux-m68k.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