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-next>] [day] [month] [year] [list]
Message-ID: <20140812060745.GA7987@node.dhcp.inet.fi>
Date:	Tue, 12 Aug 2014 09:07:45 +0300
From:	"Kirill A. Shutemov" <kirill@...temov.name>
To:	Oren Twaig <oren@...lemp.com>
Cc:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	linux-mm@...ck.org,
	"Shai Fultheim (Shai@...leMP.com)" <Shai@...lemp.com>
Subject: Re: x86: vmalloc and THP

On Tue, Aug 12, 2014 at 08:00:54AM +0300, Oren Twaig wrote:
> <html style="direction: ltr;">

plain/text, please.

>Hello,
>
>Does memory allocated using vmalloc() will be mapped using huge
>pages either directly or later by THP ? 

No. It's neither aligned properly, nor physically contiguous.

>If not, is there any fast way to change this behavior ? Maybe by
>changing the granularity/alignment of such allocations to allow such
>mapping ?

What's the point to use vmalloc() in this case?

-- 
 Kirill A. Shutemov
--
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