From: Blaisorblade <blaisorblade@yahoo.it>
To: user-mode-linux-devel@lists.sourceforge.net
Cc: Jeff Dike <jdike@addtoit.com>,
akpm@osdl.org, torvalds@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [uml-devel] [PATCH 6/8] UML - Kill some useless vmalloc tlb flushing
Date: Tue, 21 Jun 2005 01:01:16 +0200 [thread overview]
Message-ID: <200506210101.17338.blaisorblade@yahoo.it> (raw)
In-Reply-To: <200506201851.j5KIpKPr008499@ccure.user-mode-linux.org>
On Monday 20 June 2005 20:51, Jeff Dike wrote:
> There is absolutely no reason to flush the kernel's VM area during a
> tlb_flush_mm.
>
> This results in a noticable performance increase in the kernel build
> benchmark.
Andrew: hold off this one, definitely.
Jeff: Have you verified this with both modules enabled and iptables (a vmalloc
user) compiled modularly? Maybe even non-modular iptables will trigger the
bug but let's go for sure.
This situation killed a conceptually similar patch in 2.4.24-2um (which did
apply until 2.6.11):
diff -puN arch/um/kernel/skas/tlb.c~optimization-unstable
arch/um/kernel/skas/tlb.c
--- UmWorklinux-2.4.24/arch/um/kernel/skas/tlb.c~optimization-unstable
2004-07-02 13:45:07.057643968 +0200
+++ UmWorklinux-2.4.24-paolo/arch/um/kernel/skas/tlb.c 2004-07-02
13:45:14.098573584 +0200
@@ -132,7 +132,9 @@ void flush_tlb_range_skas(struct mm_stru
void flush_tlb_mm_skas(struct mm_struct *mm)
{
+#if 0
flush_tlb_kernel_vm_skas();
+#endif
fix_range(mm, 0, host_task_size, 0);
}
Given that:
void flush_tlb_kernel_vm_skas(void)
{
flush_tlb_kernel_range_skas(start_vm, end_vm);
}
and flush_tlb_kernel_range_skas was renamed to _common, I argue that this
patch is exactly the same one and will have the same bad effect.
> Signed-off-by: Jeff Dike <jdike@addtoit.com>
>
> Index: linux-2.6.12/arch/um/kernel/skas/tlb.c
> ===================================================================
> --- linux-2.6.12.orig/arch/um/kernel/skas/tlb.c 2005-06-20
> 11:54:56.000000000 -0400 +++
> linux-2.6.12/arch/um/kernel/skas/tlb.c 2005-06-20 12:11:00.000000000 -0400
> @@ -76,7 +76,6 @@ void flush_tlb_mm_skas(struct mm_struct
> return;
>
> fix_range(mm, 0, host_task_size, 0);
> - flush_tlb_kernel_range_common(start_vm, end_vm);
> }
>
> void force_flush_all_skas(void)
--
Inform me of my mistakes, so I can keep imitating Homer Simpson's "Doh!".
Paolo Giarrusso, aka Blaisorblade (Skype ID "PaoloGiarrusso", ICQ 215621894)
http://www.user-mode-linux.org/~blaisorblade
___________________________________
Yahoo! Mail: gratis 1GB per i messaggi e allegati da 10MB
http://mail.yahoo.it
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
prev parent reply other threads:[~2005-06-20 22:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-20 18:51 [uml-devel] [PATCH 6/8] UML - Kill some useless vmalloc tlb flushing Jeff Dike
2005-06-20 23:01 ` Blaisorblade [this message]
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=200506210101.17338.blaisorblade@yahoo.it \
--to=blaisorblade@yahoo.it \
--cc=akpm@osdl.org \
--cc=jdike@addtoit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.org \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/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