From: David Miller <davem@davemloft.net>
To: arnd@arndb.de
Cc: isdn@linux-pingi.de, netdev@vger.kernel.org
Subject: Re: [PATCH 13/18] i4l: kill big kernel lock
Date: Wed, 15 Sep 2010 19:31:31 -0700 (PDT) [thread overview]
Message-ID: <20100915.193131.108799689.davem@davemloft.net> (raw)
In-Reply-To: <1284492909-7147-14-git-send-email-arnd@arndb.de>
From: Arnd Bergmann <arnd@arndb.de>
Date: Tue, 14 Sep 2010 21:35:04 +0200
> The isdn4linux driver uses the big kernel lock only
> to serialize access to a few fields in its own
> modem_info structure.
>
> The easiest replacement is a driver-wide mutex.
> More fine-grained locking would be more appropriate
> here, but likely harder to implement.
>
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
Applied.
next prev parent reply other threads:[~2010-09-16 2:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-14 19:34 [PATCH 00/18] Make the big kernel lock optional Arnd Bergmann
2010-09-14 19:35 ` [PATCH 13/18] i4l: kill big kernel lock Arnd Bergmann
2010-09-16 2:31 ` David Miller [this message]
2010-09-14 19:35 ` [PATCH 14/18] misdn: " Arnd Bergmann
2010-09-16 2:31 ` David Miller
2010-09-15 9:37 ` [PATCH 00/18] Make the big kernel lock optional Stephen Rothwell
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=20100915.193131.108799689.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=arnd@arndb.de \
--cc=isdn@linux-pingi.de \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).