From: Juri Lelli <juri.lelli@gmail.com>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: Thomas Gleixner <tglx@linutronix.de>,
LKML <linux-kernel@vger.kernel.org>,
linux-rt-users <linux-rt-users@vger.kernel.org>,
Steven Rostedt <rostedt@goodmis.org>
Subject: Re: [ANNOUNCE] v5.6.2-rt1
Date: Wed, 15 Apr 2020 15:37:04 +0200 [thread overview]
Message-ID: <20200415133704.GG9767@localhost.localdomain> (raw)
In-Reply-To: <20200415111235.6gomftgifn62dylp@linutronix.de>
On 15/04/20 13:12, Sebastian Andrzej Siewior wrote:
> On 2020-04-08 09:00:13 [+0200], Juri Lelli wrote:
> > Hi,
> Hi,
>
> > On 03/04/20 19:04, Sebastian Andrzej Siewior wrote:
> > > Dear RT folks!
> > >
> > > I'm pleased to announce the v5.6.2-rt1 patch set.
> > >
> > > Changes since v5.4.28-rt19:
> > >
> > > - Rebase to v5.6.2
> >
> > I was reviewing the new set and I couldn't find v5.4.28-rt19
> > 6dbbc833c99f ("mm: perform lru_add_drain_all() remotely"). Don't think
> > it has been squashed either.
> >
> > Am I wrong? If not, why was that left out?
>
> I was going to drop it from v5.4 but kept it last minute. I announced in
> https://lkml.kernel.org/r/20200309171350.kjb3pdjazhxm2li2@linutronix.de
>
> that the problem it fixes is not limited to RT so we need a solution for
> both config switches. The current plan for local-locks is not to work
> cross CPU because it breaks the local_irq_save() / preempt_disable()
> replacement which is something this patch relies on.
> The worker triggered via vmstat_update() is also blocked if the user
> task runs at an elevated priority for longer time.
OK. Thanks for clarifying.
Best,
Juri
prev parent reply other threads:[~2020-04-15 13:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-03 17:04 [ANNOUNCE] v5.6.2-rt1 Sebastian Andrzej Siewior
2020-04-05 4:53 ` 0087-rcu-Use-a-raw_spinlock_t-for-kfree-batching.patch Mike Galbraith
2020-04-15 13:34 ` 0087-rcu-Use-a-raw_spinlock_t-for-kfree-batching.patch Sebastian Andrzej Siewior
2020-04-08 7:00 ` [ANNOUNCE] v5.6.2-rt1 Juri Lelli
2020-04-15 11:12 ` Sebastian Andrzej Siewior
2020-04-15 13:37 ` Juri Lelli [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=20200415133704.GG9767@localhost.localdomain \
--to=juri.lelli@gmail.com \
--cc=bigeasy@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=rostedt@goodmis.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.