linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Michal Hocko <mhocko@kernel.org>
To: Christoph Lameter <cl@linux.com>
Cc: Matthew Wilcox <willy@infradead.org>,
	linux-mm@kvack.org, Pekka Enberg <penberg@cs.helsinki.fi>,
	akpm@linux-foundation.org, Mel Gorman <mel@skynet.ie>,
	andi@firstfloor.org, Rik van Riel <riel@redhat.com>
Subject: Re: [RFC 0/6] Slab Fragmentation Reduction V16
Date: Mon, 13 Mar 2017 10:15:16 +0100	[thread overview]
Message-ID: <20170313091515.GD31518@dhcp22.suse.cz> (raw)
In-Reply-To: <alpine.DEB.2.20.1703080955180.16208@east.gentwo.org>

On Wed 08-03-17 09:58:58, Cristopher Lameter wrote:
> On Wed, 8 Mar 2017, Michal Hocko wrote:
> 
> > JFTR the previous version was posted here: https://lwn.net/Articles/371892/
> > and Dave had some concerns https://lkml.org/lkml/2010/2/8/329 which led
> > to a different approach and design of the slab shrinking
> > https://lkml.org/lkml/2010/2/8/329.
> >
> > I haven't looked at this series yet but has those concerns been
> > addressed/considered?
> 
> Well yes this has been discussed for a couple of years. The basic approach
> is not only needed for the file systems (like what Chinner was focusing
> on) but in general for slab caches. The objection was regarding the
> integration into the slab reclaim logic in vmscan.c and the filesystem
> reclaim in general.
> 
> Dave and Matthew were at linux.conf.au and we agreed to first try it with
> the radix tree and then generalize from there.  The reclaim logic
> was a bit hacky and we will have to find some better way to
> integrate this.
> 
> There is a video on youtube capturing the discussion (My talk on movable
> kernel objects).

Hmm, OK. There seems to be a slot to discuss this at LSFMM this year so
I hope we can discuss your proposal there.

-- 
Michal Hocko
SUSE Labs

--
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:[~2017-03-13  9:15 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-07 21:24 Christoph Lameter
2017-03-07 21:24 ` [RFC 1/6] slub: Replace ctor field with ops field in /sys/slab/* Christoph Lameter
2017-03-07 21:24 ` [RFC 2/6] slub: Add defrag_ratio field and sysfs support Christoph Lameter
2017-03-07 21:24 ` [RFC 3/6] slub: Add get() and kick() methods Christoph Lameter
2017-03-07 21:24 ` [RFC 4/6] slub: Sort slab cache list and establish maximum objects for defrag slabs Christoph Lameter
2017-03-07 21:24 ` [RFC 5/6] slub: Slab defrag core Christoph Lameter
2017-03-07 22:03   ` Matthew Wilcox
2017-03-07 21:24 ` [RFC 6/6] slub: Extend slabinfo to support -D and -F options Christoph Lameter
2017-03-08 14:34 ` [RFC 0/6] Slab Fragmentation Reduction V16 Michal Hocko
2017-03-08 15:58   ` Christoph Lameter
2017-03-13  9:15     ` Michal Hocko [this message]
2017-03-13  9:16       ` Michal Hocko

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=20170313091515.GD31518@dhcp22.suse.cz \
    --to=mhocko@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=andi@firstfloor.org \
    --cc=cl@linux.com \
    --cc=linux-mm@kvack.org \
    --cc=mel@skynet.ie \
    --cc=penberg@cs.helsinki.fi \
    --cc=riel@redhat.com \
    --cc=willy@infradead.org \
    /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