linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Jesper Dangaard Brouer <brouer@redhat.com>
To: Rik van Riel <riel@redhat.com>
Cc: brouer@redhat.com, Christoph Lameter <cl@linux.com>,
	Pekka Enberg <penberg@kernel.org>,
	js1304@gmail.com, lsf@lists.linux-foundation.org,
	linux-mm <linux-mm@kvack.org>,
	David Rientjes <rientjes@google.com>,
	Joonsoo Kim <iamjoonsoo.kim@lge.com>,
	lsf-pc@lists.linux-foundation.org,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [Lsf] [LSF/MM TOPIC] Ideas for SLUB allocator
Date: Tue, 12 Apr 2016 23:14:35 +0200	[thread overview]
Message-ID: <20160412231435.3cbf3aeb@redhat.com> (raw)
In-Reply-To: <1460484828.7134.4.camel@redhat.com>

On Tue, 12 Apr 2016 14:13:48 -0400
Rik van Riel <riel@redhat.com> wrote:

> On Tue, 2016-04-12 at 11:01 -0500, Christoph Lameter wrote:
> > On Tue, 12 Apr 2016, Jesper Dangaard Brouer wrote:
> >   
> > > 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 will be there.
> >   
> > > I've already published the preliminary slides here:
> > >  http://people.netfilter.org/hawk/presentations/MM-summit2016/slab_
> > > mm_summit2016.odp  
> > 
> > Re Autotuning: SLUB obj per page:
> > 	SLUB can combine pages of different orders in a slab cache so
> > this would
> > 	be possible.
> > 
> > per CPU freelist per page:
> > 	Could we drop the per cpu partial lists if this works?
> > 
> > Clearing memory:
> > 	Could exploit the fact that the page is zero on alloc and also
> > zap
> > 	when no object in the page is in use?  
> 
> Between the SLUB things both of you want to
> discuss, do you think one 30 minute slot will
> be enough to start with, or should we schedule
> a whole hour?
> 
> We have some free slots left on the second day,
> where discussions can overflow if necessary.

30 min slot is fine by me :-)

-- 
Best regards,
  Jesper Dangaard Brouer
  MSc.CS, Principal Kernel Engineer at Red Hat
  Author of http://www.iptv-analyzer.org
  LinkedIn: http://www.linkedin.com/in/brouer

--
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 21:14 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 ` [Lsf] " Matthew Wilcox
2016-04-12 15:03   ` Jesper Dangaard Brouer
2016-04-12 16:01 ` Christoph Lameter
2016-04-12 18:13   ` Rik van Riel
2016-04-12 21:14     ` Jesper Dangaard Brouer [this message]

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=20160412231435.3cbf3aeb@redhat.com \
    --to=brouer@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=cl@linux.com \
    --cc=iamjoonsoo.kim@lge.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 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).