[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <8760qr8orh.fsf@tassilo.jf.intel.com>
Date: Tue, 23 Aug 2016 08:54:10 -0700
From: Andi Kleen <andi@...stfloor.org>
To: Michal Hocko <mhocko@...nel.org>
Cc: Joonsoo Kim <iamjoonsoo.kim@....com>,
Aruna Ramakrishna <aruna.ramakrishna@...cle.com>,
linux-mm@...ck.org, linux-kernel@...r.kernel.org,
Mike Kravetz <mike.kravetz@...cle.com>,
Christoph Lameter <cl@...ux.com>,
Pekka Enberg <penberg@...nel.org>,
David Rientjes <rientjes@...gle.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Mel Gorman <mgorman@...e.de>, Jiri Slaby <jslaby@...e.cz>
Subject: Re: what is the purpose of SLAB and SLUB
Michal Hocko <mhocko@...nel.org> writes:
>
>> Anyway, we cannot remove one without regression so we don't remove one
>> until now. In this case, there is no point to stop improving one.
>
> I can completely see the reason to not drop SLAB (and I am not suggesting
> that) but I would expect that SLAB would be more in a feature freeze
> state. Or if both of them need to evolve then at least describe which
> workloads pathologically benefit/suffer from one or the other.
Why would you stop someone from working on SLAB if they want to?
Forcibly enforcing a freeze on something can make sense if you're
in charge of a team to conserve resources, but in Linux the situation is
very different.
Everyone works on what they (or their employer wants), not what
someone else wants. So if they want slab that is what they do.
-Andi
--
ak@...ux.intel.com -- Speaking for myself only
Powered by blists - more mailing lists