From: akpm@linux-foundation.org
To: jdike@addtoit.com, blaisorblade@yahoo.it, jdike@linux.intel.com,
mm-commits@vger.kernel.org
Subject: - uml-speed-up-exec.patch removed from -mm tree
Date: Mon, 07 May 2007 17:06:37 -0700 [thread overview]
Message-ID: <200705080006.l4806buL009209@shell0.pdx.osdl.net> (raw)
The patch titled
uml: speed up exec
has been removed from the -mm tree. Its filename was
uml-speed-up-exec.patch
This patch was dropped because it was merged into mainline or a subsystem tree
------------------------------------------------------
Subject: uml: speed up exec
From: Jeff Dike <jdike@addtoit.com>
flush_thread doesn't need to do a full page table walk in order to clear the
address space. It knows what the end result needs to be, so it can call unmap
directly.
This results in a 10-20% speedup in an exec from bash.
Signed-off-by: Jeff Dike <jdike@linux.intel.com>
Cc: Paolo 'Blaisorblade' Giarrusso <blaisorblade@yahoo.it>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
arch/um/kernel/skas/exec.c | 12 +++++++++++-
1 file changed, 11 insertions(+), 1 deletion(-)
diff -puN arch/um/kernel/skas/exec.c~uml-speed-up-exec arch/um/kernel/skas/exec.c
--- a/arch/um/kernel/skas/exec.c~uml-speed-up-exec
+++ a/arch/um/kernel/skas/exec.c
@@ -17,7 +17,17 @@
void flush_thread_skas(void)
{
- force_flush_all();
+ void *data = NULL;
+ unsigned long end = proc_mm ? task_size : CONFIG_STUB_START;
+ int ret;
+
+ ret = unmap(¤t->mm->context.skas.id, 0, end, 1, &data);
+ if(ret){
+ printk("flush_thread_skas - clearing address space failed, "
+ "err = %d\n", ret);
+ force_sig(SIGKILL, current);
+ }
+
switch_mm_skas(¤t->mm->context.skas.id);
}
_
Patches currently in -mm which might be from jdike@addtoit.com are
origin.patch
uml-hostfs-style-fixes.patch
uml-an-idle-system-should-have-zero-load-average.patch
remove-tas.patch
x86-create-asm-cmpxchgh.patch
uml-network-and-pcap-cleanup.patch
uml-pcap-devices-should-get-macs-from-command-line.patch
reply other threads:[~2007-05-08 0:11 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200705080006.l4806buL009209@shell0.pdx.osdl.net \
--to=akpm@linux-foundation.org \
--cc=blaisorblade@yahoo.it \
--cc=jdike@addtoit.com \
--cc=jdike@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mm-commits@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.