From: Alan Cox <gnomes@lxorguk.ukuu.org.uk>
To: Nikolay Borisov <nborisov@suse.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
mathieu.desnoyers@efficios.com,
Peter Zijlstra <peterz@infradead.org>,
parri.andrea@gmail.com
Subject: Re: Reasoning about memory ordering
Date: Fri, 23 Feb 2018 15:38:07 +0000 [thread overview]
Message-ID: <20180223153807.64666cfe@alans-desktop> (raw)
In-Reply-To: <0db16ef6-c805-b1f6-527f-8fec149e3df5@suse.com>
> Given this is the current state of the code (it's part of btrfs) I believe
> the following could/should be done:
Is there benchmarking data to show that a custom lock is justified
(especiaally given it's going to mean btrfs and rtlinux don't play
together nicely since it won't be able to see the mutex lock and do
priority boosting ?)
Alan
next prev parent reply other threads:[~2018-02-23 15:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-23 12:30 Reasoning about memory ordering Nikolay Borisov
2018-02-23 15:38 ` Alan Cox [this message]
2018-02-23 15:59 ` Nikolay Borisov
2018-02-23 17:31 ` Andrea Parri
2018-02-23 17:45 ` Nikolay Borisov
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=20180223153807.64666cfe@alans-desktop \
--to=gnomes@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=nborisov@suse.com \
--cc=parri.andrea@gmail.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@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