From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Nick Piggin <npiggin@suse.de>
Cc: "linux-mm@kvack.org" <linux-mm@kvack.org>,
linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] mm/vmalloc: Export purge_vmap_area_lazy()
Date: Thu, 25 Mar 2010 19:25:59 +1100 [thread overview]
Message-ID: <1269505559.8599.239.camel@pasglop> (raw)
In-Reply-To: <20100325052814.GA7493@laptop.nomadix.com>
> You want vm_unmap_aliases(), which also flushes entries in the
> per-cpu vmap allocator (and is already exported for other code
> that has similar problems).
Ok, I missed that one. I'll update my patch. Thanks.
Cheers,
Ben.
WARNING: multiple messages have this Message-ID (diff)
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Nick Piggin <npiggin@suse.de>
Cc: linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Nathan Fontenot <nfont@austin.ibm.com>
Subject: Re: [PATCH 1/2] mm/vmalloc: Export purge_vmap_area_lazy()
Date: Thu, 25 Mar 2010 19:25:59 +1100 [thread overview]
Message-ID: <1269505559.8599.239.camel@pasglop> (raw)
In-Reply-To: <20100325052814.GA7493@laptop.nomadix.com>
> You want vm_unmap_aliases(), which also flushes entries in the
> per-cpu vmap allocator (and is already exported for other code
> that has similar problems).
Ok, I missed that one. I'll update my patch. Thanks.
Cheers,
Ben.
WARNING: multiple messages have this Message-ID (diff)
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Nick Piggin <npiggin@suse.de>
Cc: linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Nathan Fontenot <nfont@austin.ibm.com>
Subject: Re: [PATCH 1/2] mm/vmalloc: Export purge_vmap_area_lazy()
Date: Thu, 25 Mar 2010 19:25:59 +1100 [thread overview]
Message-ID: <1269505559.8599.239.camel@pasglop> (raw)
In-Reply-To: <20100325052814.GA7493@laptop.nomadix.com>
> You want vm_unmap_aliases(), which also flushes entries in the
> per-cpu vmap allocator (and is already exported for other code
> that has similar problems).
Ok, I missed that one. I'll update my patch. Thanks.
Cheers,
Ben.
--
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>
next prev parent reply other threads:[~2010-03-25 8:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-24 7:56 [PATCH 1/2] mm/vmalloc: Export purge_vmap_area_lazy() Benjamin Herrenschmidt
2010-03-24 7:56 ` Benjamin Herrenschmidt
2010-03-24 7:56 ` Benjamin Herrenschmidt
2010-03-25 5:28 ` Nick Piggin
2010-03-25 5:28 ` Nick Piggin
2010-03-25 5:28 ` Nick Piggin
2010-03-25 8:25 ` Benjamin Herrenschmidt [this message]
2010-03-25 8:25 ` Benjamin Herrenschmidt
2010-03-25 8:25 ` Benjamin Herrenschmidt
2010-03-25 8:39 ` MJ embd
2010-03-25 8:39 ` MJ embd
2010-03-25 8:39 ` MJ embd
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=1269505559.8599.239.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linuxppc-dev@lists.ozlabs.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.