Generic Linux architectural discussions
 help / color / mirror / Atom feed
From: David Howells <dhowells@redhat.com>
To: Nick Piggin <npiggin@suse.de>
Cc: dhowells@redhat.com, linux-arch@vger.kernel.org
Subject: Re: [rfc] vmalloc: lazy, batched vunmapping
Date: Fri, 24 Aug 2007 09:59:25 +0100	[thread overview]
Message-ID: <14030.1187945965@redhat.com> (raw)
In-Reply-To: <20070824032646.GE6989@wotan.suse.de>

Nick Piggin <npiggin@suse.de> wrote:

> I'm working on a bit of code that vmaps/vunmaps a bit more often than
> I'd like. I've implemented a frontend to cache commonly used mappings,
> which solves most of the problem, but in looking various other ways to
> get the last bit of performance, I thought might be generally helpful
> to batch up vunmap driven TLB flushes. So I'll just throw the idea
> out there (is anyone else doing a lot of vmapping? I'd like to hear
> from you!).

Can the OOM handler force a purge?

David

  reply	other threads:[~2007-08-24  8:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-24  3:26 [rfc] vmalloc: lazy, batched vunmapping Nick Piggin
2007-08-24  8:59 ` David Howells [this message]
2007-08-24 11:24   ` 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=14030.1187945965@redhat.com \
    --to=dhowells@redhat.com \
    --cc=linux-arch@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