linux-kernel - Re: Improvement on memory subsystem

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <84144f020607190335p65ba24cbn3ba95eddd28ac675@mail.gmail.com>
Date:	Wed, 19 Jul 2006 13:35:27 +0300
From:	"Pekka Enberg" <penberg@...helsinki.fi>
To:	"yunfeng zhang" <zyf.zeroos@...il.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: Improvement on memory subsystem

On 7/19/06, yunfeng zhang <zyf.zeroos@...il.com> wrote:
> Here, the off-slab is the same as the off-slab concept of Linux,
> doesn't Linux stores bufctl_t array in its off-slab object?
>
> I consider that we should try our best to explore the potential of
> page structure. In my OS, page structure is just like a union and is
> cast into different types according to its flag field.

The slab allocator currently allocates space for struct slab and the
bufctls next to each other regardless of whether we are allocating
on-slab or off-slab. Your approach of splitting them results in more
data cache pressure for the cache_alloc() path, I think.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/