From: Arjan van de Ven <arjan@infradead.org>
To: linux-kernel@vger.kernel.org
Cc: vda@ilport.com.ua, akpm@osdl.org
Subject: Re: + update-mm-acx-driver-to-version-0331.patch added to -mm tree
Date: Wed, 01 Feb 2006 06:28:13 +0100 [thread overview]
Message-ID: <1138771694.5123.3.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <200602010211.k112BVps013714@shell0.pdx.osdl.net>
> -struct wlandevice {
> +struct acx_device {
> + /* most frequent accesses first (dereferencing and cache line!) */
> +
> + /*** Locking ***/
> + struct semaphore sem;
> + spinlock_t lock;
> +#if defined(PARANOID_LOCKING) /* Lock debugging */
> + const char *last_sem;
> + const char *last_lock;
> + unsigned long sem_time;
> + unsigned long lock_time;
> +#endif
> +
any chance of turning this into a mutex instead?
(and you get some of the debugging for free instead that way)
next parent reply other threads:[~2006-02-01 5:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200602010211.k112BVps013714@shell0.pdx.osdl.net>
2006-02-01 5:28 ` Arjan van de Ven [this message]
2006-02-01 7:07 ` + update-mm-acx-driver-to-version-0331.patch added to -mm tree Denis Vlasenko
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=1138771694.5123.3.camel@laptopd505.fenrus.org \
--to=arjan@infradead.org \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vda@ilport.com.ua \
/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).