From: Nick Piggin <npiggin@suse.de>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Steven Whitehouse <swhiteho@redhat.com>,
Minchan Kim <minchan.kim@gmail.com>,
linux-mm@kvack.org
Subject: Re: [patch] mm: vmap area cache
Date: Thu, 3 Jun 2010 23:55:33 +1000 [thread overview]
Message-ID: <20100603135533.GO6822@laptop> (raw)
In-Reply-To: <20100602144905.aa613dec.akpm@linux-foundation.org>
On Wed, Jun 02, 2010 at 02:49:05PM -0700, Andrew Morton wrote:
> On Mon, 31 May 2010 18:07:57 +1000
> Nick Piggin <npiggin@suse.de> wrote:
>
> > Hi Andrew,
> >
> > Could you put this in your tree? It could do with a bit more testing. I
> > will update you with updates or results from Steven.
> >
> > Thanks,
> > Nick
> > --
> >
> > Provide a free area cache for the vmalloc virtual address allocator, based
> > on the approach taken in the user virtual memory allocator.
> >
> > This reduces the number of rbtree operations and linear traversals over
> > the vmap extents to find a free area. The lazy vmap flushing makes this problem
> > worse because because freed but not yet flushed vmaps tend to build up in
> > the address space between flushes.
> >
> > Steven noticed a performance problem with GFS2. Results are as follows...
> >
> >
> >
>
> changelog got truncated - the "results" and the signoff are missing.
Yes I was going to add them when Steven gets a chance to re test his
performance case. Indications from earlier iterations are that it
should solve the regression.
I had hoped to just get some wider testing in -mm before getting the
results and asking to push it upstream.
> > --- linux-2.6.orig/mm/vmalloc.c
> > +++ linux-2.6/mm/vmalloc.c
> > @@ -262,8 +262,14 @@ struct vmap_area {
> > };
> >
> > static DEFINE_SPINLOCK(vmap_area_lock);
> > -static struct rb_root vmap_area_root = RB_ROOT;
> > static LIST_HEAD(vmap_area_list);
> > +static struct rb_root vmap_area_root = RB_ROOT;
> > +
> > +static struct rb_node *free_vmap_cache;
> > +static unsigned long cached_hole_size;
> > +static unsigned long cached_start;
> > +static unsigned long cached_align;
> > +
> > static unsigned long vmap_area_pcpu_hole;
> >
> > static struct vmap_area *__find_vmap_area(unsigned long addr)
> > @@ -332,9 +338,11 @@ static struct vmap_area *alloc_vmap_area
> > struct rb_node *n;
> > unsigned long addr;
> > int purged = 0;
> > + struct vmap_area *first;
> >
> > BUG_ON(!size);
> > BUG_ON(size & ~PAGE_MASK);
> > + BUG_ON(!is_power_of_2(align));
>
> Worried. How do we know this won't trigger?
I'd be very sure that nobody relies on it unless the caller is buggy
anyway. I mean, such alignment hardly means anything because the
caller doesn't know what address it will get.
I just put it in there because in my vmalloc user test harness, non
power of 2 alignments were the only case I encountered where allocator
behaviour was different before/after this patch. I don't think it is
a valid test case but I just wanted to be satisfied we don't have
weird callers.
> > va = kmalloc_node(sizeof(struct vmap_area),
> > gfp_mask & GFP_RECLAIM_MASK, node);
> > @@ -342,17 +350,39 @@ static struct vmap_area *alloc_vmap_area
> > return ERR_PTR(-ENOMEM);
> >
> > retry:
> > - addr = ALIGN(vstart, align);
> > -
> > spin_lock(&vmap_area_lock);
> > - if (addr + size - 1 < addr)
> > - goto overflow;
> > + /* invalidate cache if we have more permissive parameters */
> > + if (!free_vmap_cache ||
> > + size <= cached_hole_size ||
> > + vstart < cached_start ||
> > + align < cached_align) {
> > +nocache:
> > + cached_hole_size = 0;
> > + free_vmap_cache = NULL;
> > + }
> > + /* record if we encounter less permissive parameters */
> > + cached_start = vstart;
> > + cached_align = align;
> > +
> > + /* find starting point for our search */
> > + if (free_vmap_cache) {
> > + first = rb_entry(free_vmap_cache, struct vmap_area, rb_node);
> > + addr = ALIGN(first->va_end + PAGE_SIZE, align);
> > + if (addr < vstart)
> > + goto nocache;
> > + if (addr + size - 1 < addr)
> > + goto overflow;
>
> Some comments attached to the `if' tests would make it easier to
> understand what's going on.
OK, I'll try to come up with something.
>
> > +
> > + } else {
> > + addr = ALIGN(vstart, align);
> > + if (addr + size - 1 < addr)
> > + goto overflow;
> > - /* XXX: could have a last_hole cache */
> > - n = vmap_area_root.rb_node;
> > - if (n) {
> > - struct vmap_area *first = NULL;
> > + n = vmap_area_root.rb_node;
> > + if (!n)
> > + goto found;
> >
> > + first = NULL;
> > do {
> > struct vmap_area *tmp;
> > tmp = rb_entry(n, struct vmap_area, rb_node);
>
> this?
Yes, thanks.
> --- a/mm/vmalloc.c~mm-vmap-area-cache-fix
> +++ a/mm/vmalloc.c
> @@ -265,6 +265,7 @@ static DEFINE_SPINLOCK(vmap_area_lock);
> static LIST_HEAD(vmap_area_list);
> static struct rb_root vmap_area_root = RB_ROOT;
>
> +/* The vmap cache globals are protected by vmap_area_lock */
> static struct rb_node *free_vmap_cache;
> static unsigned long cached_hole_size;
> static unsigned long cached_start;
> _
--
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-03 13:55 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 [this message]
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
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=20100603135533.GO6822@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).