From: Luiz Capitulino <lcapitulino@redhat.com>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: linux-rt-users@vger.kernel.org, riel@redhat.com,
tglx@linutronix.de, srostedt@redhat.com, williams@redhat.com
Subject: Re: [PATCH RESEND -rt] mm: perform lru_add_drain_all() remotely
Date: Thu, 12 May 2016 15:52:02 -0400 [thread overview]
Message-ID: <20160512155202.46666531@redhat.com> (raw)
In-Reply-To: <20160512144943.GD19035@linutronix.de>
On Thu, 12 May 2016 16:49:43 +0200
Sebastian Andrzej Siewior <bigeasy@linutronix.de> wrote:
> * Luiz Capitulino | 2016-05-12 09:51:49 [-0400]:
>
> >That's correct. This is an -RT patch for two reasons:
> >
> > 1. This solution builds on top of the per-cpu locks API implemented
> > by -RT and already in place in the pagevecs drain code
> >
> > 2. As SCHED_FIFO is the norm in -RT, the problem is more common there
>
> more common so not RT-only. Would you people prefer this for mainline or
> would you rather something else in case this needs to be fixed
> mainline, too?
To have this for mainline we'd have to forward-port local_locks.
It's doable, but I think it's a bit too much only to solve this
problem.
The alternative, which is what I had in mind, was to forward-port
this change to mainline when local_locks gets merged upstream. But
I guess this will only happen when sleeping spinlocks are merged?
next prev parent reply other threads:[~2016-05-12 19:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-09 14:50 [PATCH RESEND -rt] mm: perform lru_add_drain_all() remotely Luiz Capitulino
2016-05-12 8:42 ` Sebastian Andrzej Siewior
2016-05-12 9:21 ` Sebastian Andrzej Siewior
2016-05-12 13:51 ` Luiz Capitulino
2016-05-12 14:49 ` Sebastian Andrzej Siewior
2016-05-12 19:52 ` Luiz Capitulino [this message]
2016-05-25 15:59 ` Sebastian Andrzej Siewior
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=20160512155202.46666531@redhat.com \
--to=lcapitulino@redhat.com \
--cc=bigeasy@linutronix.de \
--cc=linux-rt-users@vger.kernel.org \
--cc=riel@redhat.com \
--cc=srostedt@redhat.com \
--cc=tglx@linutronix.de \
--cc=williams@redhat.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).