From: Michal Hocko <email@example.com> To: Andi Kleen <firstname.lastname@example.org> Cc: Christoph Lameter <email@example.com>, Mel Gorman <firstname.lastname@example.org>, Joonsoo Kim <email@example.com>, Aruna Ramakrishna <firstname.lastname@example.org>, email@example.com, firstname.lastname@example.org, Mike Kravetz <email@example.com>, Pekka Enberg <firstname.lastname@example.org>, David Rientjes <email@example.com>, Andrew Morton <firstname.lastname@example.org>, Jiri Slaby <email@example.com> Subject: Re: what is the purpose of SLAB and SLUB Date: Mon, 29 Aug 2016 15:44:58 +0200 [thread overview] Message-ID: <20160829134458.GD2968@dhcp22.suse.cz> (raw) In-Reply-To: <firstname.lastname@example.org> On Fri 26-08-16 13:47:47, Andi Kleen wrote: > Christoph Lameter <email@example.com> writes: > > > >> If you want to rework the VM to use a larger fundamental unit, track > >> sub-units where required and deal with the internal fragmentation issues > >> then by all means go ahead and deal with it. > > > > Hmmm... The time problem is always there. Tried various approaches over > > the last decade. Could be a massive project. We really would need a > > larger group of developers to effectively do this. > > I'm surprised that compactions is not able to fix the fragmentation. > Is the problem that there are too many non movable objects around? Compaction can certainly help and the more we are proactive in that direction the better. Vlastimil has already done a first step in that direction and we a have a dedicated kcompactd kernel thread for that purpose. But I guess what Mel had in mind is the latency of higher order pages which is inherently higher with the current page allocator no matter how well the compaction works. There are other changes, mostly for the fast path, needed to make higher order pages less of a second citizen. -- Michal Hocko SUSE Labs
next prev parent reply other threads:[~2016-08-29 13:45 UTC|newest] Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top 2016-08-17 18:20 [PATCH v3] mm/slab: Improve performance of gathering slabinfo stats Aruna Ramakrishna 2016-08-17 19:03 ` Eric Dumazet 2016-08-17 19:25 ` Aruna Ramakrishna 2016-08-18 11:52 ` Michal Hocko 2016-08-19 5:47 ` aruna.ramakrishna 2016-08-23 2:13 ` Joonsoo Kim 2016-08-23 15:38 ` what is the purpose of SLAB and SLUB (was: Re: [PATCH v3] mm/slab: Improve performance of gathering slabinfo) stats Michal Hocko 2016-08-23 15:54 ` what is the purpose of SLAB and SLUB Andi Kleen 2016-08-25 4:10 ` Christoph Lameter 2016-08-25 7:32 ` Michal Hocko 2016-08-25 19:49 ` Christoph Lameter 2016-08-24 1:15 ` what is the purpose of SLAB and SLUB (was: Re: [PATCH v3] mm/slab: Improve performance of gathering slabinfo) stats Joonsoo Kim 2016-08-24 8:05 ` Michal Hocko 2016-08-24 8:20 ` Mel Gorman 2016-08-25 4:01 ` Christoph Lameter 2016-08-25 10:07 ` Mel Gorman 2016-08-25 19:55 ` Christoph Lameter 2016-08-26 20:47 ` what is the purpose of SLAB and SLUB Andi Kleen 2016-08-29 13:44 ` Michal Hocko [this message] 2016-08-29 14:49 ` Christoph Lameter 2016-08-30 9:39 ` what is the purpose of SLAB and SLUB (was: Re: [PATCH v3] mm/slab: Improve performance of gathering slabinfo) stats Mel Gorman 2016-08-30 19:32 ` Christoph Lameter
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=20160829134458.GD2968@dhcp22.suse.cz \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: what is the purpose of SLAB and SLUB' \ /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
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).