All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Wilcox <willy@linux.intel.com>
To: Jesper Dangaard Brouer <jbrouer@redhat.com>
Cc: lsf@lists.linux-foundation.org, linux-mm <linux-mm@kvack.org>,
	Rik van Riel <riel@redhat.com>, Christoph Lameter <cl@linux.com>,
	Joonsoo Kim <iamjoonsoo.kim@lge.com>,
	Pekka Enberg <penberg@kernel.org>,
	David Rientjes <rientjes@google.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	js1304@gmail.com, lsf-pc@lists.linux-foundation.org
Subject: Re: [Lsf] [LSF/MM TOPIC] Ideas for SLUB allocator
Date: Tue, 12 Apr 2016 09:37:28 -0400	[thread overview]
Message-ID: <20160412133728.GM2781@linux.intel.com> (raw)
In-Reply-To: <20160412120215.000283c7@redhat.com>

On Tue, Apr 12, 2016 at 12:02:15PM +0200, Jesper Dangaard Brouer wrote:
> Hi Rik,
> 
> I have another topic, which is very MM-specific.
> 
> I have some ideas for improving SLUB allocator further, after my work
> on implementing the slab bulk APIs.  Maybe you can give me a small
> slot, I only have 7 guidance slides.  Or else I hope we/I can talk
> about these ideas in a hallway track with Christoph and others involved
> in slab development...
> 
> I've already published the preliminary slides here:
>  http://people.netfilter.org/hawk/presentations/MM-summit2016/slab_mm_summit2016.odp

The current bulk API returns the pointers in an array.  What the
radix tree would like is the ability to bulk allocate from a slab and
chain the allocations through an offset.  See __radix_tree_preload()
in lib/radix-tree.c.  I don't know if this is a common thing to do
elsewhere in the kernel.  Obviously, radix-tree could allocate the array
on the stack and set up the chain itself, but I would think it would be
just as easy for slab to do it itself and save the stack space.

--
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:[~2016-04-12 13:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-12 10:02 [LSF/MM TOPIC] Ideas for SLUB allocator Jesper Dangaard Brouer
2016-04-12 13:37 ` Matthew Wilcox [this message]
2016-04-12 15:03   ` [Lsf] " Jesper Dangaard Brouer
2016-04-12 16:01 ` Christoph Lameter
2016-04-12 18:13   ` Rik van Riel
2016-04-12 21:14     ` [Lsf] " Jesper Dangaard Brouer

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=20160412133728.GM2781@linux.intel.com \
    --to=willy@linux.intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=cl@linux.com \
    --cc=iamjoonsoo.kim@lge.com \
    --cc=jbrouer@redhat.com \
    --cc=js1304@gmail.com \
    --cc=linux-mm@kvack.org \
    --cc=lsf-pc@lists.linux-foundation.org \
    --cc=lsf@lists.linux-foundation.org \
    --cc=penberg@kernel.org \
    --cc=riel@redhat.com \
    --cc=rientjes@google.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.