From: Miles Chen <miles.chen@mediatek.com>
To: Michal Hocko <mhocko@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Joe Perches <joe@perches.com>,
Matthew Wilcox <willy@infradead.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, wsd_upstream@mediatek.com
Subject: Re: [PATCH v3] mm/page_owner: use kvmalloc instead of kmalloc
Date: Wed, 31 Oct 2018 16:47:17 +0800 [thread overview]
Message-ID: <1540975637.10275.10.camel@mtkswgap22> (raw)
In-Reply-To: <20181030081537.GV32673@dhcp22.suse.cz>
On Tue, 2018-10-30 at 09:15 +0100, Michal Hocko wrote:
> On Tue 30-10-18 14:55:51, Miles Chen wrote:
> [...]
> > It's a real problem when using page_owner.
> > I found this issue recently: I'm not able to read page_owner information
> > during a overnight test. (error: read failed: Out of memory). I replace
> > kmalloc() with vmalloc() and it worked well.
>
> Is this with trimming the allocation to a single page and doing shorter
> than requested reads?
I printed out the allocate count on my device the request count is <=
4096. So I tested this scenario by trimming the count to from 4096 to
1024 bytes and it works fine.
count = count > 1024? 1024: count;
It tested it on both 32bit and 64bit kernel.
next prev parent reply other threads:[~2018-10-31 8:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-29 5:16 [PATCH v3] mm/page_owner: use kvmalloc instead of kmalloc miles.chen
2018-10-29 8:07 ` Michal Hocko
2018-10-29 8:17 ` Michal Hocko
2018-10-30 1:29 ` Miles Chen
2018-10-30 6:06 ` Michal Hocko
2018-10-30 6:55 ` Miles Chen
2018-10-30 8:15 ` Michal Hocko
2018-10-31 8:47 ` Miles Chen [this message]
2018-10-31 10:15 ` Michal Hocko
2018-10-31 10:19 ` Miles Chen
2018-10-31 11:41 ` Michal Hocko
2018-11-01 10:00 ` Miles Chen
2018-11-01 10:27 ` Michal Hocko
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=1540975637.10275.10.camel@mtkswgap22 \
--to=miles.chen@mediatek.com \
--cc=akpm@linux-foundation.org \
--cc=joe@perches.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=willy@infradead.org \
--cc=wsd_upstream@mediatek.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;
as well as URLs for NNTP newsgroup(s).