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: <Pine.LNX.4.64.0705171145330.3010@schroedinger.engr.sgi.com>
Date:	Thu, 17 May 2007 11:46:58 -0700 (PDT)
From:	Christoph Lameter <clameter@....com>
To:	Stefan Richter <stefanr@...6.in-berlin.de>
cc:	"Cestonaro, Thilo (external)" 
	<Thilo.Cestonaro.external@...itsu-siemens.com>,
	linux-kernel@...r.kernel.org
Subject: Re: How to guarantee that kmalloc returns an address below 4GB

On Wed, 16 May 2007, Stefan Richter wrote:

> Cestonaro, Thilo (external) wrote:
> > is there an option for kmalloc, which I can use to allocate
> > a buffer which is in physical memory placed below 4GB?
> > Not in a remapped area.
> 
> GFP_DMA32

Nope. There are no general slabs available for DMA32.

You could use a dma slab by specifying GFP_DMA. However, on i386 and 
x86_64 this will get you memory in the precious first 16MB. On IA64 and 
other platforms you will get memory < 4GB.

Another option is to use the page allocator and specify GFP_DMA32.

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ