From: Lai Jiangshan <laijs@cn.fujitsu.com>
To: linux-kernel@vger.kernel.org
Cc: Lai Jiangshan <laijs@cn.fujitsu.com>,
akpm@linux-foundation.org, Chris Metcalf <cmetcalf@tilera.com>,
Mel Gorman <mgorman@suse.de>, Tejun Heo <tj@kernel.org>,
Christoph Lameter <cl@gentwo.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
Andrea Arcangeli <aarcange@redhat.com>,
Rik van Riel <riel@redhat.com>, Jianyu Zhan <nasa4836@gmail.com>,
Johannes Weiner <hannes@cmpxchg.org>,
Khalid Aziz <khalid.aziz@oracle.com>,
linux-mm@kvack.org
Subject: [PATCH] swap: remove the struct cpumask has_work
Date: Thu, 31 Jul 2014 11:30:19 +0800 [thread overview]
Message-ID: <1406777421-12830-3-git-send-email-laijs@cn.fujitsu.com> (raw)
It is suggested that cpumask_var_t and alloc_cpumask_var() should be used
instead of struct cpumask. But I don't want to add this complicity nor
leave this unwelcome "static struct cpumask has_work;", so I just remove
it and use flush_work() to perform on all online drain_work. flush_work()
performs very quickly on initialized but unused work item, thus we don't
need the struct cpumask has_work for performance.
CC: akpm@linux-foundation.org
CC: Chris Metcalf <cmetcalf@tilera.com>
CC: Mel Gorman <mgorman@suse.de>
CC: Tejun Heo <tj@kernel.org>
CC: Christoph Lameter <cl@gentwo.org>
CC: Frederic Weisbecker <fweisbec@gmail.com>
Signed-off-by: Lai Jiangshan <laijs@cn.fujitsu.com>
---
mm/swap.c | 11 ++++-------
1 files changed, 4 insertions(+), 7 deletions(-)
diff --git a/mm/swap.c b/mm/swap.c
index 9e8e347..bb524ca 100644
--- a/mm/swap.c
+++ b/mm/swap.c
@@ -833,27 +833,24 @@ static DEFINE_PER_CPU(struct work_struct, lru_add_drain_work);
void lru_add_drain_all(void)
{
static DEFINE_MUTEX(lock);
- static struct cpumask has_work;
int cpu;
mutex_lock(&lock);
get_online_cpus();
- cpumask_clear(&has_work);
for_each_online_cpu(cpu) {
struct work_struct *work = &per_cpu(lru_add_drain_work, cpu);
+ INIT_WORK(work, lru_add_drain_per_cpu);
+
if (pagevec_count(&per_cpu(lru_add_pvec, cpu)) ||
pagevec_count(&per_cpu(lru_rotate_pvecs, cpu)) ||
pagevec_count(&per_cpu(lru_deactivate_pvecs, cpu)) ||
- need_activate_page_drain(cpu)) {
- INIT_WORK(work, lru_add_drain_per_cpu);
+ need_activate_page_drain(cpu))
schedule_work_on(cpu, work);
- cpumask_set_cpu(cpu, &has_work);
- }
}
- for_each_cpu(cpu, &has_work)
+ for_each_online_cpu(cpu)
flush_work(&per_cpu(lru_add_drain_work, cpu));
put_online_cpus();
--
1.7.4.4
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next reply other threads:[~2014-07-31 3:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-31 3:30 Lai Jiangshan [this message]
2014-07-31 11:51 ` [PATCH] swap: remove the struct cpumask has_work Michal Hocko
2014-07-31 16:09 ` Chris Metcalf
2014-08-01 1:39 ` Lai Jiangshan
2014-08-01 17:16 ` Chris Metcalf
2014-08-01 17:28 ` Frederic Weisbecker
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=1406777421-12830-3-git-send-email-laijs@cn.fujitsu.com \
--to=laijs@cn.fujitsu.com \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=cl@gentwo.org \
--cc=cmetcalf@tilera.com \
--cc=fweisbec@gmail.com \
--cc=hannes@cmpxchg.org \
--cc=khalid.aziz@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=nasa4836@gmail.com \
--cc=riel@redhat.com \
--cc=tj@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).