From: Evgeniy Polyakov <zbr@ioremap.net>
To: NeilBrown <neilb@suse.de>
Cc: linux-kernel@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [PATCH] w1: Introduce a slave mutex for serializing IO.
Date: Fri, 4 May 2012 01:27:06 +0400 [thread overview]
Message-ID: <20120503212706.GA26612@ioremap.net> (raw)
In-Reply-To: <20120504070838.5bd23110@notabene.brown>
On Fri, May 04, 2012 at 07:08:38AM +1000, NeilBrown (neilb@suse.de) wrote:
> You can only check the owner on SMP builds, or when debugging is enabled.
> So I don't think that approach can work.
You can store owner in master device and protect with mutex itself.
On non-smp systems it can not be preempted, so can be checked without
mutex.
--
Evgeniy Polyakov
next prev parent reply other threads:[~2012-05-03 21:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-25 2:49 [PATCH] w1: Introduce a slave mutex for serializing IO NeilBrown
2012-05-01 21:39 ` Evgeniy Polyakov
2012-05-02 6:26 ` NeilBrown
2012-05-03 17:58 ` Evgeniy Polyakov
2012-05-03 21:08 ` NeilBrown
2012-05-03 21:27 ` Evgeniy Polyakov [this message]
2012-05-09 1:43 ` NeilBrown
2012-05-15 1:26 ` Evgeniy Polyakov
2012-05-18 6:05 ` NeilBrown
2012-06-10 20:58 ` Evgeniy Polyakov
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=20120503212706.GA26612@ioremap.net \
--to=zbr@ioremap.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@suse.de \
/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