linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Eric Dumazet <eric.dumazet@gmail.com>
To: "Kirill A. Shutemov" <kirill@shutemov.name>
Cc: Oren Twaig <oren@scalemp.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	linux-mm@kvack.org,
	"Shai Fultheim (Shai@ScaleMP.com)" <Shai@scalemp.com>
Subject: Re: x86: vmalloc and THP
Date: Tue, 12 Aug 2014 05:28:52 -0700	[thread overview]
Message-ID: <1407846532.10122.66.camel@edumazet-glaptop2.roam.corp.google.com> (raw)
In-Reply-To: <20140812060745.GA7987@node.dhcp.inet.fi>

On Tue, 2014-08-12 at 09:07 +0300, Kirill A. Shutemov wrote:
> On Tue, Aug 12, 2014 at 08:00:54AM +0300, Oren Twaig wrote:

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

Look at various large hashes we have in the system, all using
vmalloc() :

[    0.006856] Dentry cache hash table entries: 16777216 (order: 15, 134217728 bytes)
[    0.033130] Inode-cache hash table entries: 8388608 (order: 14, 67108864 bytes)
[    1.197621] TCP established hash table entries: 524288 (order: 11, 8388608 bytes)

I would imagine a performance difference if we were using hugepages.



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

  reply	other threads:[~2014-08-12 12:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-12  5:00 Oren Twaig
2014-08-12  6:07 ` Kirill A. Shutemov
2014-08-12 12:28   ` Eric Dumazet [this message]
2014-08-12 15:01     ` Kirill A. Shutemov
2014-08-12 16:20   ` Oren Twaig
2014-08-12 21:40     ` Kirill A. Shutemov
2014-08-12  5:01 Oren Twaig

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=1407846532.10122.66.camel@edumazet-glaptop2.roam.corp.google.com \
    --to=eric.dumazet@gmail.com \
    --cc=Shai@scalemp.com \
    --cc=kirill@shutemov.name \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=oren@scalemp.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox