linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Alexey Korolev <akorolex@gmail.com>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.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 19:02:09 +1200	[thread overview]
Message-ID: <202cde0e0905280002o5614f279r9db7c8c52ad7df10@mail.gmail.com> (raw)
In-Reply-To: <20090528143524.e8a2cde7.kamezawa.hiroyu@jp.fujitsu.com>

Hi

>> Hi,
>> ...
>> What you could suggest to workaround the problem except hacks with page count?
>> May be it makes sence to introduce wm_insert_pages function?
>>
>
>
> Maybe followings are for drivers ?
>
> void *alloc_pages_exact(size_t size, gfp_t gfp_mask)
> void free_pages_exact(void *virt, size_t size)
>
Hmm. This functions were developed for needs of video drivers to
prevent extra memory allocations, page splitting is the side effect of
using this function.
It should be Ok for UMA case.
The only problem that the driver I'm writing now should support NUMA
nodes selection also. In this case alloc_pages_exact won't help :(.
What could be the best solution to solve existing inconsistency? Any ideas?

Thanks,
Alexey

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

  parent reply	other threads:[~2009-05-28  7:02 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 [this message]
     [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
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=202cde0e0905280002o5614f279r9db7c8c52ad7df10@mail.gmail.com \
    --to=akorolex@gmail.com \
    --cc=greg@kroah.com \
    --cc=kamezawa.hiroyu@jp.fujitsu.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