From: Mel Gorman <mel@csn.ul.ie>
To: Alexey Korolev <akorolex@gmail.com>
Cc: linux-mm@kvack.org, greg@kroah.com, vijaykumar@bravegnu.org
Subject: Re: Inconsistency (bug) of vm_insert_page with high order allocations
Date: Thu, 28 May 2009 10:59:04 +0100 [thread overview]
Message-ID: <20090528095904.GD10334@csn.ul.ie> (raw)
In-Reply-To: <202cde0e0905272207y2926d679s7380a0f26f6c6e71@mail.gmail.com>
On Thu, May 28, 2009 at 05:07:01PM +1200, Alexey Korolev wrote:
> Hi,
> I have the following issue. I need to allocate a big chunk of
> contiguous memory and then transfer it to user mode applications to
> let them operate with given buffers.
>
> To allocate memory I use standard function alloc_apges(gfp_mask,
> order) which asks buddy allocator to give a chunk of memory of given
> "order".
> Allocator returns page and also sets page count to 1 but for page of
> high order. I.e. pages 2,3 etc inside high order allocation will have
> page->_count==0.
> If I try to mmap allocated area to user space vm_insert_page will
> return error as pages 2,3, etc are not refcounted.
>
page = alloc_pages(high_order);
split_page(page, high_order);
That will fix up the ref-counting of each of the individual pages. You are
then responsible for freeing them individually. As you are inserting these
into userspace, I suspect that's ok.
> The issue could be workaround if to set-up refcount to 1 manually for
> each page. But this workaround is not very good, because page refcount
> is used inside mm subsystem only.
>
And you would have reimplemented split_page().
> While searching a driver with the similar solutions in kernel tree it
> was found a driver which suffers from exactly the same
> problem("poch"). So it is not single problem.
>
> What you could suggest to workaround the problem except hacks with page count?
> May be it makes sence to introduce wm_insert_pages function?
>
> In this case users would have the following picture:
> zero order page: alloc_page <-> vm_instert_page
> non zero order : alloc_pages(..., order) <-> vm_instert_pages(...., order)
>
--
Mel Gorman
Part-time Phd Student Linux Technology Center
University of Limerick IBM Dublin Software Lab
--
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>
next prev parent reply other threads:[~2009-05-28 9:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-28 5:07 Alexey Korolev
[not found] ` <20090528143524.e8a2cde7.kamezawa.hiroyu@jp.fujitsu.com>
2009-05-28 7:02 ` Alexey Korolev
[not found] ` <20090528162108.a6adcc36.kamezawa.hiroyu@jp.fujitsu.com>
2009-05-30 5:42 ` Alexey Korolev
2009-06-01 23:53 ` KAMEZAWA Hiroyuki
2009-05-28 9:59 ` Mel Gorman [this message]
2009-05-30 5:27 ` Alexey Korolev
2009-06-02 8:38 ` Mel Gorman
2009-06-03 5:58 ` Alexey Korolev
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=20090528095904.GD10334@csn.ul.ie \
--to=mel@csn.ul.ie \
--cc=akorolex@gmail.com \
--cc=greg@kroah.com \
--cc=linux-mm@kvack.org \
--cc=vijaykumar@bravegnu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox