lkml.org 
[lkml]   [2021]   [Oct]   [4]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    SubjectRe: [QUESTION] is SLAB considered legacy and deprecated?
    From
    On 10/4/21 08:01, Hyeonggon Yoo wrote:
    > On Sun, Oct 03, 2021 at 06:25:29PM -0700, David Rientjes wrote:
    >> I would disagree that SLAB isn't currently maintained, I think it's
    >> actively maintained.
    >
    > I thought it was not actively maintained because most of patches were
    > fixups and cleanups for years and as Vlastimil said, new features are

    Fixups and cleanups still count as "actively maintained". The opposite
    case would be "nobody uses it because it was broken for years since
    commit X and we only noticed now".

    > only added to SLUB. development was focused on SLUB.
    >
    >> I think the general guidance is that changes for both allocators can still
    >> be merged upstream if they show a significant win (improved performnace,
    >> maintaining performance while reducing memory footprint, code hygiene,
    >> etc) and there's no specific policy that we cannot make changes to
    >> mm/slab.c.
    >
    > Good.
    >
    > I see things to improve in SLAB and want to improve it.
    > I will appreciate if you review them.

    It would be great if your motivation started with "I prefer SLAB over
    SLUB because X and Y but I need to improve Z", not just a theoretical
    concern.

    > Thanks,
    > Hyeonggon
    >

    \
     
     \ /
      Last update: 2021-10-04 13:40    [W:4.124 / U:0.008 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site