linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Nick Piggin <npiggin@suse.de>
To: Christoph Lameter <cl@linux-foundation.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Linux Memory Management List <linux-mm@kvack.org>,
	linux-arch@vger.kernel.org
Subject: Re: [patch] mm: rewrite vmap layer
Date: Wed, 20 Aug 2008 11:02:34 +0200	[thread overview]
Message-ID: <20080820090234.GA7018@wotan.suse.de> (raw)
In-Reply-To: <48AADBDC.2000608@linux-foundation.org>

On Tue, Aug 19, 2008 at 09:42:36AM -0500, Christoph Lameter wrote:
> Nick Piggin wrote:
> 
> > +static void free_unmap_vmap_area(struct vmap_area *va)
> > +{
> > +	va->flags |= VM_LAZY_FREE;
> > +	atomic_add((va->va_end - va->va_start) >> PAGE_SHIFT, &vmap_lazy_nr);
> > +	if (unlikely(atomic_read(&vmap_lazy_nr) > LAZY_MAX))
> > +		purge_vmap_area_lazy();
> > +}
> 
> Could you check here if we are in an atomic context and then simply not purge
> the vmap area? That may we may get to a vfree that can be run in an atomic
> context.

If the locks and per-cpu access is made irq safe, then yes.

 
> Or run purge_vma_area_lazy from keventd?
 
Right. But that's only needed if we want to vmap from irq context too
(otherwise we can just do the purge check at vmap time).

Is there any good reason to be able to vmap or vunmap from interrupt
time, though?

--
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>

  reply	other threads:[~2008-08-20  9:02 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-18 13:32 Nick Piggin
2008-08-19  0:24 ` Andrew Morton
2008-08-19  7:37   ` Russell King
2008-08-19 10:39     ` Nick Piggin
2008-08-20  3:32       ` Kyle McMartin
2008-08-19 10:02   ` Nick Piggin
2008-08-19 14:42 ` Christoph Lameter
2008-08-20  9:02   ` Nick Piggin [this message]
2008-08-20 14:03     ` Christoph Lameter
2008-08-20 16:22       ` Nick Piggin
2008-08-20 16:50         ` Christoph Lameter
2008-08-20 16:59           ` Nick Piggin
2008-08-20 17:05             ` Christoph Lameter
2008-08-20 17:48               ` Nick Piggin
2008-08-21  7:19       ` Johannes Weiner
2008-08-21 13:13         ` Christoph Lameter
2008-09-05  3:06 ` Andrew Morton
2008-09-07 12:06   ` 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=20080820090234.GA7018@wotan.suse.de \
    --to=npiggin@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=cl@linux-foundation.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    /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