From: Matthew Dobson <colpatch@us.ibm.com>
To: Andrew Morton <akpm@zip.com.au>,
Martin Bligh <mjbligh@us.ibm.com>,
linux-mm@kvack.org, Michael Hohnbaum <hohnbaum@us.ibm.com>
Subject: [patch] Useless locking in mm/numa.c
Date: Thu, 18 Jul 2002 18:03:35 -0700 [thread overview]
Message-ID: <3D376567.4040307@us.ibm.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 193 bytes --]
There is a lock that is apparently protecting nothing. The node_lock spinlock
in mm/numa.c is protecting read-only accesses to pgdat_list. Here is a patch
to get rid of it.
Cheers!
-Matt
[-- Attachment #2: node_lock.patch --]
[-- Type: text/plain, Size: 752 bytes --]
--- linux-2.5.26-vanilla/mm/numa.c Tue Jul 16 16:49:30 2002
+++ linux-2.5.26-vanilla/mm/numa.c.fixed Thu Jul 18 17:59:35 2002
@@ -44,15 +44,11 @@
#define LONG_ALIGN(x) (((x)+(sizeof(long))-1)&~((sizeof(long))-1))
-static spinlock_t node_lock = SPIN_LOCK_UNLOCKED;
-
void show_free_areas_node(pg_data_t *pgdat)
{
unsigned long flags;
- spin_lock_irqsave(&node_lock, flags);
show_free_areas_core(pgdat);
- spin_unlock_irqrestore(&node_lock, flags);
}
/*
@@ -106,11 +102,9 @@
#ifdef CONFIG_NUMA
temp = NODE_DATA(numa_node_id());
#else
- spin_lock_irqsave(&node_lock, flags);
if (!next) next = pgdat_list;
temp = next;
next = next->node_next;
- spin_unlock_irqrestore(&node_lock, flags);
#endif
start = temp;
while (temp) {
next reply other threads:[~2002-07-19 1:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-19 1:03 Matthew Dobson [this message]
2002-07-19 18:36 ` Kanoj Sarcar
2002-07-19 18:38 ` William Lee Irwin III
2002-07-19 18:40 ` Kanoj Sarcar
2002-07-19 20:30 ` Matthew Dobson
2002-07-19 21:45 ` Matthew Dobson
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=3D376567.4040307@us.ibm.com \
--to=colpatch@us.ibm.com \
--cc=akpm@zip.com.au \
--cc=hohnbaum@us.ibm.com \
--cc=linux-mm@kvack.org \
--cc=mjbligh@us.ibm.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