linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Mel Gorman <mgorman@techsingularity.net>
To: Peter Zijlstra <peterz@infradead.org>, Will Deacon <will@kernel.org>
Cc: Davidlohr Bueso <dave@stgolabs.net>,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: Loadavg accounting error on arm64
Date: Mon, 16 Nov 2020 11:49:38 +0000	[thread overview]
Message-ID: <20201116114938.GN3371@techsingularity.net> (raw)
In-Reply-To: <20201116091054.GL3371@techsingularity.net>

On Mon, Nov 16, 2020 at 09:10:54AM +0000, Mel Gorman wrote:
> I'll be looking again today to see can I find a mistake in the ordering for
> how sched_contributes_to_load is handled but again, the lack of knowledge
> on the arm64 memory model means I'm a bit stuck and a second set of eyes
> would be nice :(
> 

This morning, it's not particularly clear what orders the visibility of
sched_contributes_to_load exactly like other task fields in the schedule
vs try_to_wake_up paths. I thought the rq lock would have ordered them but
something is clearly off or loadavg would not be getting screwed. It could
be done with an rmb and wmb (testing and hasn't blown up so far) but that's
far too heavy.  smp_load_acquire/smp_store_release might be sufficient
on it although less clear if the arm64 gives the necessary guarantees.

(This is still at the chucking out ideas as I haven't context switched
back in all the memory barrier rules).

-- 
Mel Gorman
SUSE Labs

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2020-11-16 11:56 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-16  9:10 Loadavg accounting error on arm64 Mel Gorman
2020-11-16 11:49 ` Mel Gorman [this message]
2020-11-16 12:00   ` Mel Gorman
2020-11-16 12:53   ` Peter Zijlstra
2020-11-16 12:58     ` Peter Zijlstra
2020-11-16 15:29       ` Mel Gorman
2020-11-16 16:42         ` Mel Gorman
2020-11-16 16:49         ` Peter Zijlstra
2020-11-16 17:24           ` Mel Gorman
2020-11-16 17:41             ` Will Deacon
2020-11-16 12:46 ` Peter Zijlstra
2020-11-16 12:58   ` Mel Gorman
2020-11-16 13:11 ` Will Deacon
2020-11-16 13:37   ` Mel Gorman
2020-11-16 14:20     ` Peter Zijlstra
2020-11-16 15:52       ` Mel Gorman
2020-11-16 16:54         ` Peter Zijlstra
2020-11-16 17:16           ` Mel Gorman
2020-11-16 19:31       ` Mel Gorman
2020-11-17  8:30         ` [PATCH] sched: Fix data-race in wakeup Peter Zijlstra
2020-11-17  9:15           ` Will Deacon
2020-11-17  9:29             ` Peter Zijlstra
2020-11-17  9:46               ` Peter Zijlstra
2020-11-17 10:36                 ` Will Deacon
2020-11-17 12:52                 ` Valentin Schneider
2020-11-17 15:37                   ` Valentin Schneider
2020-11-17 16:13                     ` Peter Zijlstra
2020-11-17 19:32                       ` Valentin Schneider
2020-11-18  8:05                         ` Peter Zijlstra
2020-11-18  9:51                           ` Valentin Schneider
2020-11-18 13:33               ` Marco Elver
2020-11-17  9:38           ` [PATCH] sched: Fix rq->nr_iowait ordering Peter Zijlstra
2020-11-17 11:43             ` Mel Gorman
2020-11-17 12:40           ` [PATCH] sched: Fix data-race in wakeup Mel Gorman

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=20201116114938.GN3371@techsingularity.net \
    --to=mgorman@techsingularity.net \
    --cc=dave@stgolabs.net \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterz@infradead.org \
    --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 NNTP newsgroup(s).