From: Andrew Morton <akpm@linux-foundation.org>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: linux-mm@kvack.org, tglx@linutronix.de,
Vlastimil Babka <vbabka@suse.cz>,
frederic@kernel.org
Subject: Re: [PATCH 2/2] mm/swap: Access struct pagevec remotely
Date: Fri, 9 Nov 2018 15:06:05 -0800 [thread overview]
Message-ID: <20181109150605.1e5d765b6d7a12edf9bb26e5@linux-foundation.org> (raw)
In-Reply-To: <20180914145924.22055-3-bigeasy@linutronix.de>
On Fri, 14 Sep 2018 16:59:24 +0200 Sebastian Andrzej Siewior <bigeasy@linutronix.de> wrote:
> Now that struct pagevec is locked during access, it is possible to
> access it from a remote CPU. The advantage is that the work can be done
> from the "requesting" CPU without firing a worker on a remote CPU and
> waiting for it to complete the work.
Well, removing a deferred work thingy is always welcome. But I'm not
sure this was the overall aim of the patchset. In fact I'm somewhat
unclear on what the overall aim is. Does it have some relevance to -RT
kernels?
Anyway, please see if you can clarify the high-level intent, refresh,
retest and resend?
next prev parent reply other threads:[~2018-11-09 23:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-14 14:59 [PATCH 0/2] mm/swap: Add locking for pagevec Sebastian Andrzej Siewior
2018-09-14 14:59 ` [PATCH 1/2] mm/swap: Add pagevec locking Sebastian Andrzej Siewior
2018-09-30 3:16 ` [LKP] [mm/swap] d884021f52: will-it-scale.per_process_ops -2.4% regression kernel test robot
2018-09-30 8:17 ` Sebastian Andrzej Siewior
2018-09-14 14:59 ` [PATCH 2/2] mm/swap: Access struct pagevec remotely Sebastian Andrzej Siewior
2018-11-09 23:06 ` Andrew Morton [this message]
2018-10-12 7:21 ` [PATCH 0/2] mm/swap: Add locking for pagevec Vlastimil Babka
2018-10-15 9:50 ` Mel Gorman
2018-10-16 16:26 ` Frederic Weisbecker
2018-10-16 17:13 ` Thomas Gleixner
2018-10-16 19:54 ` Frederic Weisbecker
2018-10-16 20:44 ` Thomas Gleixner
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=20181109150605.1e5d765b6d7a12edf9bb26e5@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=bigeasy@linutronix.de \
--cc=frederic@kernel.org \
--cc=linux-mm@kvack.org \
--cc=tglx@linutronix.de \
--cc=vbabka@suse.cz \
/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