linux-kernel - Re: [PATCH] slub: reduce overhead of slub

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] [day] [month] [year] [list]

Message-ID: <alpine.DEB.2.00.1107081240010.23187@router.home>
Date:	Fri, 8 Jul 2011 12:41:24 -0500 (CDT)
From:	Christoph Lameter <cl@...ux.com>
To:	Andi Kleen <andi@...stfloor.org>
cc:	Pekka Enberg <penberg@...nel.org>,
	David Miller <davem@...emloft.net>, marcin.slusarz@...il.com,
	mpm@...enic.com, linux-kernel@...r.kernel.org, rientjes@...gle.com,
	linux-mm@...ck.org
Subject: Re: [PATCH] slub: reduce overhead of slub_debug

On Thu, 7 Jul 2011, Andi Kleen wrote:

> Christoph Lameter <cl@...ux.com> writes:
>
>
> > +#ifdef __HAVE_ARCH_INV_MEMSCAN
> > +void *inv_memscan(void *addr, int c, size_t size)
> > +{
> > +	if (!size)
> > +		return addr;
> > +	asm volatile("repz; scasb\n\t"
>
> This will just do the slow byte accesses again internally.
> scasb is not normally very optimized in microcode as far
> as I know.
>
> Also rep has quite some startup overhead which makes
> it a bad idea for small sizes (<16-20 or so)
>
> I would stay with the C version. I bet that one is
> faster.

If the c code is such an improvement then memscan and other
implementations can be accellerated in the same way. That would be useful
in general. We can get rid of the implementation for memscan and friends
in x86 arch code.



--
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/