From: "Kirill A. Shutemov" <kirill@shutemov.name>
To: Oren Twaig <oren@scalemp.com>
Cc: "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: Wed, 13 Aug 2014 00:40:51 +0300 [thread overview]
Message-ID: <20140812214051.GA17497@node.dhcp.inet.fi> (raw)
In-Reply-To: <53EA3EE4.6090100@scalemp.com>
On Tue, Aug 12, 2014 at 07:20:52PM +0300, Oren Twaig wrote:
> >What's the point to use vmalloc() in this case?
> I've noticed that some lock/s are using linear addresses which are
> located at 0xffffc901922b4500 and from what I understand
> from mm.txt (kernel 3.0.101):
> *ffffc90000000000 - ffffe8ffffffffff (=45 bits) vmalloc/ioremap space
>
> *So I'm not sure who/how/why this lock got allocated there, but obviously
> it is using that linear set. No ?
It would be nice to know what lock it was, but nothing is inherently wrong
with lock in vmalloc space.
--
Kirill A. Shutemov
--
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: "Kirill A. Shutemov" <kirill@shutemov.name>
To: Oren Twaig <oren@scalemp.com>
Cc: "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: Wed, 13 Aug 2014 00:40:51 +0300 [thread overview]
Message-ID: <20140812214051.GA17497@node.dhcp.inet.fi> (raw)
In-Reply-To: <53EA3EE4.6090100@scalemp.com>
On Tue, Aug 12, 2014 at 07:20:52PM +0300, Oren Twaig wrote:
> >What's the point to use vmalloc() in this case?
> I've noticed that some lock/s are using linear addresses which are
> located at 0xffffc901922b4500 and from what I understand
> from mm.txt (kernel 3.0.101):
> *ffffc90000000000 - ffffe8ffffffffff (=45 bits) vmalloc/ioremap space
>
> *So I'm not sure who/how/why this lock got allocated there, but obviously
> it is using that linear set. No ?
It would be nice to know what lock it was, but nothing is inherently wrong
with lock in vmalloc space.
--
Kirill A. Shutemov
next prev parent reply other threads:[~2014-08-12 21:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-12 5:00 x86: vmalloc and THP 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 [this message]
2014-08-12 21:40 ` Kirill A. Shutemov
-- strict thread matches above, loose matches on Subject: below --
2014-08-12 5:01 Oren Twaig
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=20140812214051.GA17497@node.dhcp.inet.fi \
--to=kirill@shutemov.name \
--cc=Shai@scalemp.com \
--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 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.