linux-kernel - Re: Using Bootmem for large DMA buffers in the presence of the slab allocator

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: <alpine.DEB.2.00.1008041259440.11084@router.home>
Date:	Wed, 4 Aug 2010 13:01:48 -0500 (CDT)
From:	Christoph Lameter <cl@...ux-foundation.org>
To:	Peter Crosthwaite <peter.crosthwaite@...alogix.com>
cc:	Pekka Enberg <penberg@...helsinki.fi>,
	linux-kernel@...r.kernel.org, mpm@...enic.com,
	Michal Simek <michal.simek@...alogix.com>,
	"Edgar E. Iglesias" <edgar.iglesias@...alogix.com>,
	John Williams <john.williams@...alogix.com>
Subject: Re: Using Bootmem for large DMA buffers in the presence of the slab
  allocator

Note also that allocating a 64M buffer will be difficult due to the
maximum allocation size restrictions of the page allocator.

You therefore have no choice but to allocate the memory at boot
time. Or (if you have control over the arch) increase the maximum
allocation unit (MAX_ORDER I believe).


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