linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Nick Piggin <npiggin@suse.de>
Cc: Linux Memory Management List <linux-mm@kvack.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [rfc][patch] mm: vmap rewrite
Date: Sat, 07 Jun 2008 18:38:01 +0100	[thread overview]
Message-ID: <484AC779.1070803@goop.org> (raw)
In-Reply-To: <20080605102015.GA11366@wotan.suse.de>

Nick Piggin wrote:
> Hi. RFC.
>
> Rewrite the vmap allocator to use rbtrees and lazy tlb flushing, and provide a
> fast, scalable percpu frontend for small vmaps.
>
> XEN and PAT and such do not like deferred TLB flushing. They just need to call
> vm_unmap_aliases() in order to flush any deferred mappings.  That call is very
> expensive (well, actually not a lot more expensive than a single vunmap under
> the old scheme), however it should be OK if not called too often.
>   

What are the performance characteristics?  Can it be fast-pathed if 
there are no outstanding aliases?

For Xen, I'd need to do the alias unmap each time it allocates a page 
for use in a pagetable.  For initial process construction that could be 
deferred, but creating mappings on a live process could get fairly 
expensive as a result.  The ideal interface for me would be a way of 
testing if a given page has vmap aliases, so that we need only do the 
unmap if really necessary.  I'm guessing that goes into "need a new page 
flag" territory though...

    J

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  parent reply	other threads:[~2008-06-07 17:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-05 10:20 Nick Piggin
2008-06-06  7:17 ` Jiri Slaby
2008-06-10  3:45   ` Nick Piggin
2008-06-07 17:38 ` Jeremy Fitzhardinge [this message]
2008-06-10  2:53   ` Nick Piggin
2008-06-11 18:46     ` Jeremy Fitzhardinge
2008-06-12  1:22       ` Nick Piggin
2008-06-12 20:18   ` [rfc][patch] mm: vmap rewrite #2 Nick Piggin

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=484AC779.1070803@goop.org \
    --to=jeremy@goop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.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