linux-kernel - [git pull] slab allocator fixes / cleanups

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

Message-ID: <Pine.LNX.4.64.0802141544130.3913@schroedinger.engr.sgi.com>
Date:	Thu, 14 Feb 2008 16:42:29 -0800 (PST)
From:	Christoph Lameter <clameter@....com>
To:	torvalds@...ux-foundation.org
cc:	Pekka Enberg <penberg@...helsinki.fi>,
	linux-kernel@...r.kernel.org, linux-mm@...ck.org
Subject: [git pull] slab allocator fixes / cleanups

The following changes since commit e760e716d47b48caf98da348368fd41b4a9b9e7e:
  Linus Torvalds (1):
        Merge git://git.kernel.org/.../jejb/scsi-rc-fixes-2.6

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/christoph/vm.git slab-linus

Adrian Bunk (1):
      make slub.c:slab_address() static

Christoph Lameter (3):
      slub: Determine gfpflags once and not every time a slab is allocated
      slub: Fallback to kmalloc_large for failing higher order allocs
      slub: Support 4k kmallocs again to compensate for page allocator slowness

Marcin Slusarz (1):
      slab: avoid double initialization & do initialization in 1 place

Pekka Enberg (1):
      slub: kmalloc page allocator pass-through cleanup

 include/linux/slub_def.h |   15 +++++--
 mm/slab.c                |    3 +-
 mm/slub.c                |   94 
+++++++++++++++++++++++++++++++---------------
 3 files changed, 75 insertions(+), 37 deletions(-)

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