public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Nick Piggin <npiggin@suse.de>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: [PATCH] vmap: add flag to allow lazy unmap to be disabled at runtime
Date: Mon, 26 Jul 2010 13:24:51 -0700	[thread overview]
Message-ID: <4C4DEF13.1030403@goop.org> (raw)



[ Nick, I forget if I sent this to you before.  Could you Ack it if it looks OK? Thanks, J ]

Add a flag to force lazy_max_pages() to zero to prevent any outstanding
mapped pages.  We'll need this for Xen.

Signed-off-by: Jeremy Fitzhardinge<jeremy.fitzhardinge@citrix.com>

diff --git a/include/linux/vmalloc.h b/include/linux/vmalloc.h
index 227c2a5..b840fda 100644
--- a/include/linux/vmalloc.h
+++ b/include/linux/vmalloc.h
@@ -7,6 +7,8 @@

  struct vm_area_struct;		/* vma defining user mapping in mm_types.h */

+extern bool vmap_lazy_unmap;
+
  /* bits in flags of vmalloc's vm_struct below */
  #define VM_IOREMAP	0x00000001	/* ioremap() and friends */
  #define VM_ALLOC	0x00000002	/* vmalloc() */
diff --git a/mm/vmalloc.c b/mm/vmalloc.c
index ae00746..7f35fe2 100644
--- a/mm/vmalloc.c
+++ b/mm/vmalloc.c
@@ -31,6 +31,7 @@
  #include<asm/tlbflush.h>
  #include<asm/shmparam.h>

+bool vmap_lazy_unmap __read_mostly = true;

  /*** Page table manipulation functions ***/

@@ -502,6 +503,9 @@ static unsigned long lazy_max_pages(void)
  {
  	unsigned int log;

+	if (!vmap_lazy_unmap)
+		return 0;
+
  	log = fls(num_online_cpus());

  	return log * (32UL * 1024 * 1024 / PAGE_SIZE);



             reply	other threads:[~2010-07-26 20:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-26 20:24 Jeremy Fitzhardinge [this message]
2010-07-27  8:24 ` [PATCH] vmap: add flag to allow lazy unmap to be disabled at runtime Nick Piggin
2010-07-27 18:13   ` Konrad Rzeszutek Wilk
2010-07-27 18:56   ` Jeremy Fitzhardinge

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=4C4DEF13.1030403@goop.org \
    --to=jeremy@goop.org \
    --cc=konrad.wilk@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=npiggin@suse.de \
    /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