From: Oren Twaig <oren@scalemp.com>
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
linux-mm@kvack.org
Cc: "Shai Fultheim (Shai@ScaleMP.com)" <Shai@scalemp.com>
Subject: x86: vmalloc and THP
Date: Tue, 12 Aug 2014 08:01:41 +0300 [thread overview]
Message-ID: <53E99FB5.1020506@scalemp.com> (raw)
Hello,
Does memory allocated using vmalloc() will be mapped using huge pages
either directly or later by THP ?
If not, is there any fast way to change this behavior ? Maybe by
changing the granularity/alignment of such allocations to allow such
mapping ?
Thanks,
Oren Twaig.
---
This email is free from viruses and malware because avast! Antivirus protection is active.
http://www.avast.com
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
WARNING: multiple messages have this Message-ID (diff)
From: Oren Twaig <oren@scalemp.com>
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
linux-mm@kvack.org
Cc: "Shai Fultheim (Shai@ScaleMP.com)" <Shai@scalemp.com>
Subject: x86: vmalloc and THP
Date: Tue, 12 Aug 2014 08:01:41 +0300 [thread overview]
Message-ID: <53E99FB5.1020506@scalemp.com> (raw)
Hello,
Does memory allocated using vmalloc() will be mapped using huge pages
either directly or later by THP ?
If not, is there any fast way to change this behavior ? Maybe by
changing the granularity/alignment of such allocations to allow such
mapping ?
Thanks,
Oren Twaig.
---
This email is free from viruses and malware because avast! Antivirus protection is active.
http://www.avast.com
next reply other threads:[~2014-08-12 5:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-12 5:01 Oren Twaig [this message]
2014-08-12 5:01 ` x86: vmalloc and THP Oren Twaig
-- strict thread matches above, loose matches on Subject: below --
2014-08-12 5:00 Oren Twaig
2014-08-12 6:07 ` Kirill A. Shutemov
2014-08-12 6:07 ` Kirill A. Shutemov
2014-08-12 12:28 ` Eric Dumazet
2014-08-12 12:28 ` Eric Dumazet
2014-08-12 15:01 ` Kirill A. Shutemov
2014-08-12 15:01 ` Kirill A. Shutemov
2014-08-12 16:20 ` Oren Twaig
2014-08-12 16:20 ` Oren Twaig
2014-08-12 21:40 ` Kirill A. Shutemov
2014-08-12 21:40 ` Kirill A. Shutemov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=53E99FB5.1020506@scalemp.com \
--to=oren@scalemp.com \
--cc=Shai@scalemp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.