From: Andrew Morton <akpm@osdl.org>
To: linux-arch@vger.kernel.org
Cc: steiner@sgi.com, mort@wildopensource.com, jbarnes@sgi.com
Subject: Fw: Re: Reduce TLB flushing during process migration
Date: Wed, 12 May 2004 15:32:03 -0700 [thread overview]
Message-ID: <20040512153203.5ac1b196.akpm@osdl.org> (raw)
fyi, we're planning on pulling out the tlb_migrate_prepare() stuff
again - apparently it's not welcome on ia64 in its present form.
davem, you expressed interest in this previously. The question is whether
we should remove the whole thing, or just the ia64 component?
Begin forwarded message:
Date: Wed, 12 May 2004 15:08:36 -0700
From: Andrew Morton <akpm@osdl.org>
To: davidm@hpl.hp.com
Cc: steiner@sgi.com, mort@wildopensource.com, jbarnes@sgi.com
Subject: Re: Reduce TLB flushing during process migration
David Mosberger <davidm@napali.hpl.hp.com> wrote:
>
> Please remove it until a proper solution exists.
I'll submit this on Friday, when bugalugs returns.
David Mosberger asked that this be backed out:
"I do not believe that flushing the TLB before migration is be the right thing
to do on ia64 machines which support global TLB purges (i.e., all but SGI's
machines)."
It was of huge benefit for the SGI machines, so work is ongoing.
---
25-akpm/include/asm-generic/tlb.h | 2 --
25-akpm/include/asm-ia64/tlb.h | 2 --
25-akpm/kernel/sched.c | 10 ----------
3 files changed, 14 deletions(-)
diff -puN include/asm-generic/tlb.h~revert-process-migration-speedup include/asm-generic/tlb.h
--- 25/include/asm-generic/tlb.h~revert-process-migration-speedup Wed May 12 15:04:55 2004
+++ 25-akpm/include/asm-generic/tlb.h Wed May 12 15:05:24 2004
@@ -146,6 +146,4 @@ static inline void tlb_remove_page(struc
__pmd_free_tlb(tlb, pmdp); \
} while (0)
-#define tlb_migrate_prepare(mm) do { } while(0)
-
#endif /* _ASM_GENERIC__TLB_H */
diff -puN include/asm-ia64/tlb.h~revert-process-migration-speedup include/asm-ia64/tlb.h
--- 25/include/asm-ia64/tlb.h~revert-process-migration-speedup Wed May 12 15:04:55 2004
+++ 25-akpm/include/asm-ia64/tlb.h Wed May 12 15:05:24 2004
@@ -211,8 +211,6 @@ __tlb_remove_tlb_entry (struct mmu_gathe
tlb->end_addr = address + PAGE_SIZE;
}
-#define tlb_migrate_prepare(mm) flush_tlb_mm(mm)
-
#define tlb_start_vma(tlb, vma) do { } while (0)
#define tlb_end_vma(tlb, vma) do { } while (0)
diff -puN kernel/sched.c~revert-process-migration-speedup kernel/sched.c
--- 25/kernel/sched.c~revert-process-migration-speedup Wed May 12 15:04:55 2004
+++ 25-akpm/kernel/sched.c Wed May 12 15:05:24 2004
@@ -26,8 +26,6 @@
#include <linux/highmem.h>
#include <linux/smp_lock.h>
#include <asm/mmu_context.h>
-#include <linux//pagemap.h>
-#include <asm/tlb.h>
#include <linux/interrupt.h>
#include <linux/completion.h>
#include <linux/kernel_stat.h>
@@ -1302,14 +1300,6 @@ static void sched_migrate_task(task_t *p
wake_up_process(mt);
put_task_struct(mt);
wait_for_completion(&req.done);
-
- /*
- * we want a new context here. This eliminates TLB
- * flushes on the cpus where the process executed prior to
- * the migration.
- */
- tlb_migrate_prepare(current->mm);
-
return;
}
out:
_
next reply other threads:[~2004-05-12 22:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-12 22:32 Andrew Morton [this message]
2004-05-12 23:57 ` Fw: Re: Reduce TLB flushing during process migration David S. Miller
2004-05-13 7:43 ` Andi Kleen
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=20040512153203.5ac1b196.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=jbarnes@sgi.com \
--cc=linux-arch@vger.kernel.org \
--cc=mort@wildopensource.com \
--cc=steiner@sgi.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