From: Nick Piggin <npiggin@suse.de>
To: Steven Whitehouse <swhiteho@redhat.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Minchan Kim <minchan.kim@gmail.com>,
linux-mm@kvack.org
Subject: Re: [patch] mm: vmap area cache
Date: Mon, 28 Jun 2010 18:45:04 +1000 [thread overview]
Message-ID: <20100628084504.GC28364@laptop> (raw)
In-Reply-To: <1277714262.2461.2.camel@localhost>
On Mon, Jun 28, 2010 at 09:37:42AM +0100, Steven Whitehouse wrote:
> Hi,
>
> On Sat, 2010-06-26 at 18:31 +1000, Nick Piggin wrote:
> > On Fri, Jun 25, 2010 at 02:00:17PM +0100, Steven Whitehouse wrote:
> > > Hi,
> > >
> > > Barry Marson has now tested your patch and it seems to work just fine.
> > > Sorry for the delay,
> > >
> > > Steve.
> >
> > Hi Steve,
> >
> > Thanks for that, do you mean that it has solved thee regression?
> >
> > Thanks,
> > Nick
> >
>
> Yes, thats what I have heard from Barry. He said that it was pretty
> close to the expected performance but did not give any figures. The fact
> that his test actually completes shows that most of the problem has been
> solved,
Thanks, so I think it's good to go.
It is interesting that it is just "close" to expected performance.
The lazy vunmap patch is preventing a global IPI and TLB flush on
all CPUs for every vfree() (amortizing it down to basically nothing
if you are doing just small vmaps).
Unless you are testing on a UP machine, I would have expected
improved performance if you are doing a lot of vmalloc/vfree activity.
It could be that the search is still taking some time, and is
outweighing the gains.
We have a few options for being cleverer, so if you're ever interested
to get more detailed results and find a bit more performance here,
let me know.
And thanks for all the reporting and testing so far.
--
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-06-28 8:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-31 8:07 [patch] mm: vmap area cache Nick Piggin
2010-05-31 13:21 ` Minchan Kim
2010-06-02 21:49 ` Andrew Morton
2010-06-03 13:55 ` Nick Piggin
2010-06-25 13:00 ` Steven Whitehouse
2010-06-26 8:31 ` Nick Piggin
2010-06-28 8:37 ` Steven Whitehouse
2010-06-28 8:45 ` Nick Piggin [this message]
2010-06-28 9:05 ` Steven Whitehouse
2010-06-30 23:26 ` Andrew Morton
2010-07-01 7:50 ` Nick Piggin
2010-07-01 8:49 ` Steven Whitehouse
2010-07-01 9:02 ` Nick Piggin
2010-07-14 8:55 ` Steven Whitehouse
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=20100628084504.GC28364@laptop \
--to=npiggin@suse.de \
--cc=akpm@linux-foundation.org \
--cc=linux-mm@kvack.org \
--cc=minchan.kim@gmail.com \
--cc=swhiteho@redhat.com \
/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.