lkmm.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: "Szőke Benjamin" <egyszeregy@freemail.hu>
To: paulmck@kernel.org, Alan Stern <stern@rowland.harvard.edu>
Cc: parri.andrea@gmail.com, will@kernel.org, peterz@infradead.org,
	boqun.feng@gmail.com, npiggin@gmail.com, dhowells@redhat.com,
	j.alglave@ucl.ac.uk, luc.maranget@inria.fr, akiyks@gmail.com,
	dlustig@nvidia.com, joel@joelfernandes.org,
	linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org,
	lkmm@lists.linux.dev
Subject: Re: [PATCH] tools/memory-model: Fix litmus-tests's file names for case-insensitive filesystem.
Date: Fri, 13 Dec 2024 00:09:12 +0100	[thread overview]
Message-ID: <c46da2b3-bb86-4385-bffb-2edea61d79d0@freemail.hu> (raw)
In-Reply-To: <e3a5aa0a-2c8b-4679-9344-64135df63fe1@paulmck-laptop>

2024. 11. 12. 22:53 keltezéssel, Paul E. McKenney írta:
> On Tue, Nov 12, 2024 at 03:20:00PM -0500, Alan Stern wrote:
>> On Tue, Nov 12, 2024 at 10:26:37AM -0800, Paul E. McKenney wrote:
>>> We do have a rule for the filenames in that directory that most of
>>> them follow (I am looking at *you*, "dep+plain.litmus"!).  So we have
>>> a few options:
>>>
>>> 1.	Status quo.  (How boring!!!)
>>>
>>> 2.	Come up with a better rule mapping the litmus-test file
>>> 	contents to the filename, and rename things to follow that rule.
>>> 	(Holy bikeshedding, Batman!)
>>>
>>> 3.	Keep it simple and keep the current rule, but make the
>>> 	combination of spin_lock() and smp_mb__after_spinlock()
>>> 	have a greater Hamming distance from "lock".  Szőke's
>>> 	patch changed only one of the filenames containing "Lock".
>>> 	(Bikeshedding, but narrower scope.)
>>>
>>> 4.	One of the above, but bring the litmus tests not following
>>> 	the rule into compliance.
>>>
>>> 5.	Give up on the idea of the name reflecting the contents of the
>>> 	file, and just number them or something.  (More bikeshedding
>>> 	and a different form of confusion.)
>>>
>>> 6.	#5, but accompanied by some tool or script that allows easy
>>> 	searching of the litmus tests by pattern of interaction.
>>> 	(Easy for *me* to say!)
>>>
>>> 7.	Something else entirely.
>>>
>>> Thoughts?
>>
>> Thumbs up for 3.
> 
> Very good!  Any nominations for the lucky replacement for "Lock"?
> 
> 							Thanx, Paul

Subject: [PATCH] tools/memory-model: Fix litmus-tests's file names.
Makes a greater Hamming distance for name of Z6.0+pooncelock* files.
https://lore.kernel.org/lkml/20241209150044.766-1-egyszeregy@freemail.hu/


      reply	other threads:[~2024-12-12 23:17 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-11 16:42 [PATCH] tools/memory-model: Fix litmus-tests's file names for case-insensitive filesystem egyszeregy
2024-11-11 16:54 ` Paul E. McKenney
2024-11-11 18:52   ` Szőke Benjamin
2024-11-11 19:22     ` Paul E. McKenney
2024-11-11 19:56       ` Szőke Benjamin
2024-11-11 20:29         ` Paul E. McKenney
2024-11-11 21:15           ` Szőke Benjamin
2024-11-11 21:23             ` Boqun Feng
2024-11-11 21:39               ` Szőke Benjamin
2024-11-11 21:44                 ` Boqun Feng
2024-11-11 21:52                 ` Paul E. McKenney
2024-11-11 22:00             ` Linus Torvalds
2024-11-11 23:21               ` Szőke Benjamin
2024-11-12  1:02                 ` Boqun Feng
2024-11-12 10:06                   ` Szőke Benjamin
2024-11-12 16:43                     ` Paul E. McKenney
2024-11-12 16:56                       ` Boqun Feng
2024-11-12  0:59             ` Alan Stern
2024-11-12  4:20               ` Paul E. McKenney
2024-11-12 15:35                 ` Alan Stern
2024-11-12 18:26                   ` Paul E. McKenney
2024-11-12 20:20                     ` Alan Stern
2024-11-12 21:53                       ` Paul E. McKenney
2024-12-12 23:09                         ` Szőke Benjamin [this message]

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=c46da2b3-bb86-4385-bffb-2edea61d79d0@freemail.hu \
    --to=egyszeregy@freemail.hu \
    --cc=akiyks@gmail.com \
    --cc=boqun.feng@gmail.com \
    --cc=dhowells@redhat.com \
    --cc=dlustig@nvidia.com \
    --cc=j.alglave@ucl.ac.uk \
    --cc=joel@joelfernandes.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkmm@lists.linux.dev \
    --cc=luc.maranget@inria.fr \
    --cc=npiggin@gmail.com \
    --cc=parri.andrea@gmail.com \
    --cc=paulmck@kernel.org \
    --cc=peterz@infradead.org \
    --cc=stern@rowland.harvard.edu \
    --cc=will@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 read-only IMAP folder(s) and NNTP newsgroup(s).