From: Valentin Schneider <valentin.schneider@arm.com>
To: Catalin Marinas <catalin.marinas@arm.com>
Cc: Nikolay Borisov <nborisov@suse.com>,
linux-btrfs@vger.kernel.org, paulmck@linux.ibm.com,
andrea.parri@amarulasolutions.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/2] Refactor snapshot vs nocow writers locking
Date: Mon, 29 Jul 2019 17:32:12 +0100 [thread overview]
Message-ID: <60eda0ab-08b3-de82-5b06-98386ee1928f@arm.com> (raw)
In-Reply-To: <20190729153319.GH2368@arrakis.emea.arm.com>
On 29/07/2019 16:33, Catalin Marinas wrote:
[...]
>> ---- MODULE specs ----
>> EXTENDS Integers, Sequences, TLC
>>
>> CONSTANTS
>> NR_WRITERS,
>> NR_READERS,
>> WRITER_TASK,
>> READER_TASK
>>
>> WRITERS == {WRITER_TASK} \X (1..NR_WRITERS)
>> READERS == {READER_TASK} \X (1..NR_READERS)
>> THREADS == WRITERS \union READERS
>
> Recommendation: use symbolic values for WRITERS and READERS (defined in
> .cfg: e.g. r1, r2, r3, w1, w2, w2). It allows you do to symmetry
> optimisations. We've also hit a TLC bug in the past with process values
> made up of a Cartesian product (though it may have been fixed since).
>
Right, I had forgotten that one:
https://github.com/tlaplus/tlaplus/issues/164
Being very lazy I dislike having to manually input those, but as you say
it can't be avoided if we want to use symmetry.
>> macro ReadLock(tid)
>> {
>> if (lock_state = "idle" \/ lock_state = "read_locked") {
>> lock_state := "read_locked";
>> threads[tid] := "read_locked";
>> } else {
>> assert lock_state = "write_locked";
>> \* waiting for writers to finish
>> threads[tid] := "write_waiting";
>> await lock_state = "" \/ lock_state = "read_locked";
>
> lock_state = "idle"?
>
Aye, I didn't modify those macros from the original spec.
>> macro WriteLock(tid)
>> {
>> if (lock_state = "idle" \/ lock_state = "write_locked") {
>> lock_state := "write_locked";
>> threads[tid] := "write_locked";
>> } else {
>> assert lock_state = "read_locked";
>> \* waiting for readers to finish
>> threads[tid] := "read_waiting";
>> await lock_state = "idle" \/ lock_state = "write_locked";
>> };
>> }
>
> I'd say that's one of the pitfalls of PlusCal. The above is executed
> atomically, so you'd have the lock_state read and updated in the same
> action. Looking at the C patches, there is an
> atomic_read(&lock->readers) followed by a
> percpu_counter_inc(&lock->writers). Between these two, you can have
> "readers" becoming non-zero via a different CPU.
>
> My suggestion would be to use procedures with labels to express the
> non-atomicity of such sequences.
>
Agreed, I've suggested something like this in my reply.
[...]
next prev parent reply other threads:[~2019-07-29 16:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-19 8:39 [PATCH v2 0/2] Refactor snapshot vs nocow writers locking Nikolay Borisov
2019-07-19 8:39 ` [PATCH v2 1/2] btrfs: Implement DRW lock Nikolay Borisov
2019-07-19 8:39 ` [PATCH v2 2/2] btrfs: convert snapshot/nocow exlcusion to drw lock Nikolay Borisov
2019-07-19 8:48 ` [RFC PATCH] btrfs: Hook btrfs' DRW lock to locktorture infrastructure Nikolay Borisov
2019-08-05 16:36 ` Nathan Chancellor
2019-08-05 18:17 ` David Sterba
2019-07-29 14:13 ` [PATCH v2 0/2] Refactor snapshot vs nocow writers locking Valentin Schneider
2019-07-29 15:33 ` Catalin Marinas
2019-07-29 16:32 ` Valentin Schneider [this message]
2019-07-30 11:03 ` Valentin Schneider
2019-07-30 12:11 ` Nikolay Borisov
2019-07-30 13:36 ` Valentin Schneider
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=60eda0ab-08b3-de82-5b06-98386ee1928f@arm.com \
--to=valentin.schneider@arm.com \
--cc=andrea.parri@amarulasolutions.com \
--cc=catalin.marinas@arm.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nborisov@suse.com \
--cc=paulmck@linux.ibm.com \
/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).