From mboxrd@z Thu Jan 1 00:00:00 1970 From: m.nazarewicz@samsung.com (=?utf-8?B?TWljaGHFgiBOYXphcmV3aWN6?=) Date: Fri, 27 Aug 2010 04:41:36 +0200 Subject: [PATCH/RFCv4 0/6] The Contiguous Memory Allocator framework In-Reply-To: <1282810627.1975.237.camel@laptop> References: <1282310110.2605.976.camel@laptop> <1282810627.1975.237.camel@laptop> Message-ID: To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On Thu, 26 Aug 2010 10:17:07 +0200, Peter Zijlstra wrote: > So why not work on the page allocator to improve its contiguous > allocation behaviour. If you look at the thing you'll find pageblocks > and migration types. If you change it so that you pin the migration type > of one or a number of contiguous pageblocks to say MIGRATE_MOVABLE, so > that they cannot be used for anything but movable pages you're pretty > much there. And that's exactly where I'm headed. I've created API that seems to be usable and meat mine and others requirements (not that I'm not saying it cannot be improved -- I'm always happy to hear comments) and now I'm starting to concentrate on the reusing of the grabbed memory. At first I wasn't sure how this can be managed but thanks to many comments (including yours, thanks!) I have an idea of how the thing should work and what I should do from now. -- Best regards, _ _ | Humble Liege of Serenely Enlightened Majesty of o' \,=./ `o | Computer Science, Micha? "mina86" Nazarewicz (o o) +----[mina86*mina86.com]---[mina86*jabber.org]----ooO--(_)--Ooo-- From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752359Ab0H0CmO (ORCPT ); Thu, 26 Aug 2010 22:42:14 -0400 Received: from mailout2.w1.samsung.com ([210.118.77.12]:65508 "EHLO mailout2.w1.samsung.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750710Ab0H0CmL convert rfc822-to-8bit (ORCPT ); Thu, 26 Aug 2010 22:42:11 -0400 Date: Fri, 27 Aug 2010 04:41:36 +0200 From: =?utf-8?B?TWljaGHFgiBOYXphcmV3aWN6?= Subject: Re: [PATCH/RFCv4 0/6] The Contiguous Memory Allocator framework In-reply-to: <1282810627.1975.237.camel@laptop> To: Peter Zijlstra Cc: FUJITA Tomonori , Daniel Walker , Russell King , Konrad Rzeszutek Wilk , Mel Gorman , Pawel Osciak , Jonathan Corbet , linux-kernel@vger.kernel.org, Hans Verkuil , linux-mm@kvack.org, Kyungmin Park , Zach Pfeffer , Mark Brown , Marek Szyprowski , linux-arm-kernel@lists.infradead.org, linux-media@vger.kernel.org Message-id: Organization: Samsung Electronics MIME-version: 1.0 Content-type: text/plain; charset=utf-8; format=flowed; delsp=yes Content-transfer-encoding: 8BIT User-Agent: Opera Mail/10.61 (Linux) References: <1282310110.2605.976.camel@laptop> <1282810627.1975.237.camel@laptop> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 26 Aug 2010 10:17:07 +0200, Peter Zijlstra wrote: > So why not work on the page allocator to improve its contiguous > allocation behaviour. If you look at the thing you'll find pageblocks > and migration types. If you change it so that you pin the migration type > of one or a number of contiguous pageblocks to say MIGRATE_MOVABLE, so > that they cannot be used for anything but movable pages you're pretty > much there. And that's exactly where I'm headed. I've created API that seems to be usable and meat mine and others requirements (not that I'm not saying it cannot be improved -- I'm always happy to hear comments) and now I'm starting to concentrate on the reusing of the grabbed memory. At first I wasn't sure how this can be managed but thanks to many comments (including yours, thanks!) I have an idea of how the thing should work and what I should do from now. -- Best regards, _ _ | Humble Liege of Serenely Enlightened Majesty of o' \,=./ `o | Computer Science, Michał "mina86" Nazarewicz (o o) +----[mina86*mina86.com]---[mina86*jabber.org]----ooO--(_)--Ooo-- From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail172.messagelabs.com (mail172.messagelabs.com [216.82.254.3]) by kanga.kvack.org (Postfix) with SMTP id CEC0F6B01F1 for ; Thu, 26 Aug 2010 22:42:11 -0400 (EDT) MIME-version: 1.0 Content-type: text/plain; charset=utf-8; format=flowed; delsp=yes Received: from eu_spt1 ([210.118.77.13]) by mailout3.w1.samsung.com (Sun Java(tm) System Messaging Server 6.3-8.04 (built Jul 29 2009; 32bit)) with ESMTP id <0L7S00FFDI690970@mailout3.w1.samsung.com> for linux-mm@kvack.org; Fri, 27 Aug 2010 03:42:09 +0100 (BST) Received: from linux.samsung.com ([106.116.38.10]) by spt1.w1.samsung.com (iPlanet Messaging Server 5.2 Patch 2 (built Jul 14 2004)) with ESMTPA id <0L7S00IV6I68TL@spt1.w1.samsung.com> for linux-mm@kvack.org; Fri, 27 Aug 2010 03:42:09 +0100 (BST) Date: Fri, 27 Aug 2010 04:41:36 +0200 From: =?utf-8?B?TWljaGHFgiBOYXphcmV3aWN6?= Subject: Re: [PATCH/RFCv4 0/6] The Contiguous Memory Allocator framework In-reply-to: <1282810627.1975.237.camel@laptop> Message-id: Content-transfer-encoding: Quoted-Printable References: <1282310110.2605.976.camel@laptop> <1282810627.1975.237.camel@laptop> Sender: owner-linux-mm@kvack.org To: Peter Zijlstra Cc: FUJITA Tomonori , Daniel Walker , Russell King , Konrad Rzeszutek Wilk , Mel Gorman , Pawel Osciak , Jonathan Corbet , linux-kernel@vger.kernel.org, Hans Verkuil , linux-mm@kvack.org, Kyungmin Park , Zach Pfeffer , Mark Brown , Marek Szyprowski , linux-arm-kernel@lists.infradead.org, linux-media@vger.kernel.org List-ID: On Thu, 26 Aug 2010 10:17:07 +0200, Peter Zijlstra wrote: > So why not work on the page allocator to improve its contiguous > allocation behaviour. If you look at the thing you'll find pageblocks > and migration types. If you change it so that you pin the migration ty= pe > of one or a number of contiguous pageblocks to say MIGRATE_MOVABLE, so= > that they cannot be used for anything but movable pages you're pretty > much there. And that's exactly where I'm headed. I've created API that seems to be usable and meat mine and others requirements (not that I'm not saying it= cannot be improved -- I'm always happy to hear comments) and now I'm starting to concentrate on the reusing of the grabbed memory. At first I wasn't sure how this can be managed but thanks to many comments (including yours, thanks!) I have an idea of how the thing should work and what I should do from now. -- = Best regards, _ _ | Humble Liege of Serenely Enlightened Majesty of o' \,=3D./ `o | Computer Science, Micha=C5=82 "mina86" Nazarewicz (o o) +----[mina86*mina86.com]---[mina86*jabber.org]----ooO--(_)--Ooo-- -- 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: email@kvack.org