From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Marcelo Tosatti <mtosatti@redhat.com>
Cc: linux-rt-users@vger.kernel.org,
Juri Lelli <juri.lelli@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
Frederic Weisbecker <frederic@kernel.org>
Subject: Re: [patch 2/2] mm: page_alloc: drain pages remotely
Date: Wed, 17 Jun 2020 09:42:23 +0200 [thread overview]
Message-ID: <20200617074223.wtd5lsxbpvqvbxs7@linutronix.de> (raw)
In-Reply-To: <20200616165536.GA306273@fuller.cnet>
On 2020-06-16 13:55:36 [-0300], Marcelo Tosatti wrote:
> > We had this
> > https://lore.kernel.org/linux-mm/20190424111208.24459-1-bigeasy@linutronix.de/
>
> Will reply to that thread. Do you want to refresh/resend that patchset or
> should I?
I don't plan to refresh/resend it because what we have now with local-locks
in v5.8-rc1 works for RT.
I dropped that from RT in v5.4.26-rt17 so the previous release should have
the last version of this. Please be aware that Joe Korty reported that
this patch somehow breaks a workload for him. The report never made it
to the list but he confirmed in
https://lkml.kernel.org/r/20200330154110.GA2975@zipoli.concurrent-rt.com
that is problem is gone with the removal of the patch.
Sebastian
next prev parent reply other threads:[~2020-06-17 7:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-16 16:11 [patch 0/2] re-enable remote per-cpu-pages draining Marcelo Tosatti
2020-06-16 16:11 ` [patch 1/2] rt: add local_lock_on and local_lock_irqsave_on to locallock.h Marcelo Tosatti
2020-06-16 16:11 ` [patch 2/2] mm: page_alloc: drain pages remotely Marcelo Tosatti
2020-06-16 16:32 ` Sebastian Andrzej Siewior
2020-06-16 16:55 ` Marcelo Tosatti
2020-06-17 7:42 ` Sebastian Andrzej Siewior [this message]
2020-06-17 10:11 ` Marcelo Tosatti
2020-06-17 12:01 ` Sebastian Andrzej Siewior
2020-06-16 17:04 ` Marcelo Tosatti
2020-06-17 7:46 ` Sebastian Andrzej Siewior
2020-06-17 10:12 ` Marcelo Tosatti
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=20200617074223.wtd5lsxbpvqvbxs7@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=frederic@kernel.org \
--cc=juri.lelli@redhat.com \
--cc=linux-rt-users@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=tglx@linutronix.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;
as well as URLs for NNTP newsgroup(s).