From: Thomas Gleixner <tglx@linutronix.de>
To: LKML <linux-kernel@vger.kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Ingo Molnar <mingo@elte.hu>, Tony Luck <tony.luck@intel.com>,
Trond Myklebust <Trond.Myklebust@netapp.com>
Subject: [patch] remove put_cpu_no_resched() [ Resend ]
Date: Sat, 02 May 2009 20:23:51 -0000 [thread overview]
Message-ID: <20090502202317.506137353@linutronix.de> (raw)
In-Reply-To: <20090502202312.124351431@linutronix.de>
[-- Attachment #1: remove-put-cpu-no-resched.patch --]
[-- Type: text/plain, Size: 2571 bytes --]
Impact: remove a high latency source
put_cpu_no_resched() is an optimization of put_cpu() which
unfortunately can cause high latencies.
The nfs iostats code uses put_cpu_no_resched() in a code sequence
where a reschedule request caused by an interrupt between the
get_cpu() and the put_cpu_no_resched() can delay the reschedule for at
least HZ.
The other users of put_cpu_no_resched() optimize correctly in
interrupt code, but there is no real harm in using the put_cpu()
function which is an alias for preempt_enable(). The extra check of the
preemmpt count is not as critical as the potential source of missing a
reschedule.
Debugged in the preempt-rt tree and verified in mainline.
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Cc: Ingo Molnar <mingo@elte.hu>
Cc: Tony Luck <tony.luck@intel.com>
Cc: Trond Myklebust <Trond.Myklebust@netapp.com>
---
arch/ia64/kernel/perfmon.c | 2 +-
fs/nfs/iostat.h | 4 ++--
include/linux/smp.h | 1 -
3 files changed, 3 insertions(+), 4 deletions(-)
Index: linux-2.6/arch/ia64/kernel/perfmon.c
===================================================================
--- linux-2.6.orig/arch/ia64/kernel/perfmon.c
+++ linux-2.6/arch/ia64/kernel/perfmon.c
@@ -5595,7 +5595,7 @@ pfm_interrupt_handler(int irq, void *arg
(*pfm_alt_intr_handler->handler)(irq, arg, regs);
}
- put_cpu_no_resched();
+ put_cpu();
return IRQ_HANDLED;
}
Index: linux-2.6/fs/nfs/iostat.h
===================================================================
--- linux-2.6.orig/fs/nfs/iostat.h
+++ linux-2.6/fs/nfs/iostat.h
@@ -31,7 +31,7 @@ static inline void nfs_inc_server_stats(
cpu = get_cpu();
iostats = per_cpu_ptr(server->io_stats, cpu);
iostats->events[stat]++;
- put_cpu_no_resched();
+ put_cpu();
}
static inline void nfs_inc_stats(const struct inode *inode,
@@ -50,7 +50,7 @@ static inline void nfs_add_server_stats(
cpu = get_cpu();
iostats = per_cpu_ptr(server->io_stats, cpu);
iostats->bytes[stat] += addend;
- put_cpu_no_resched();
+ put_cpu();
}
static inline void nfs_add_stats(const struct inode *inode,
Index: linux-2.6/include/linux/smp.h
===================================================================
--- linux-2.6.orig/include/linux/smp.h
+++ linux-2.6/include/linux/smp.h
@@ -177,7 +177,6 @@ static inline void init_call_single_data
#define get_cpu() ({ preempt_disable(); smp_processor_id(); })
#define put_cpu() preempt_enable()
-#define put_cpu_no_resched() preempt_enable_no_resched()
/*
* Callback to arch code if there's nosmp or maxcpus=0 on the
next parent reply other threads:[~2009-05-02 20:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090502202312.124351431@linutronix.de>
2009-05-02 20:23 ` Thomas Gleixner [this message]
2009-05-03 8:30 ` Ingo Molnar
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=20090502202317.506137353@linutronix.de \
--to=tglx@linutronix.de \
--cc=Trond.Myklebust@netapp.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tony.luck@intel.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
all inboxes | Powered by JetHome®