Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: mina86@mina86.com (Michal Nazarewicz)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 08/10] mm: cma: Contiguous Memory Allocator added
Date: Tue, 14 Jun 2011 20:40:46 +0200	[thread overview]
Message-ID: <op.vw2wt8cs3l0zgt@mnazarewicz-glaptop> (raw)
In-Reply-To: <201106142030.07549.arnd@arndb.de>

> On Tuesday 14 June 2011 18:58:35 Michal Nazarewicz wrote:
>> Is having support for multiple regions a bad thing?  Frankly,
>> removing this support will change code from reading context passed
>> as argument to code reading context from global variable.  Nothing
>> is gained; functionality is lost.

On Tue, 14 Jun 2011 20:30:07 +0200, Arnd Bergmann wrote:
> What is bad IMHO is making them the default, which forces the board
> code to care about memory management details. I would much prefer
> to have contiguous allocation parameters tuned automatically to just
> work on most boards before we add ways to do board-specific hacks.

I see those as orthogonal problems.  The code can have support for
multiple contexts but by default use a single global context exported
as cma_global variable (or some such).

And I'm not arguing against having ?contiguous allocation parameters
tuned automatically to just work on most boards?.  I just don't see
the reason to delete functionality that is already there, does not
add much code and can be useful.

-- 
Best regards,                                         _     _
.o. | Liege of Serenely Enlightened Majesty of      o' \,=./ `o
..o | Computer Science,  Michal "mina86" Nazarewicz    (o o)
ooo +-----<email/xmpp: mnazarewicz@google.com>-----ooO--(_)--Ooo--

  reply	other threads:[~2011-06-14 18:40 UTC|newest]

Thread overview: 59+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-10  9:54 [PATCHv10 0/10] Contiguous Memory Allocator Marek Szyprowski
2011-06-10  9:54 ` [PATCH 01/10] lib: bitmap: Added alignment offset for bitmap_find_next_zero_area() Marek Szyprowski
2011-06-10  9:54 ` [PATCH 02/10] lib: genalloc: Generic allocator improvements Marek Szyprowski
2011-06-10 11:24   ` Alan Cox
2011-06-10 12:22     ` Marek Szyprowski
2011-06-10 12:52       ` Alan Cox
2011-06-10 17:16         ` Michal Nazarewicz
2011-06-14 15:49         ` [Linaro-mm-sig] " Jordan Crouse
2011-06-10  9:54 ` [PATCH 03/10] mm: move some functions from memory_hotplug.c to page_isolation.c Marek Szyprowski
2011-06-10  9:54 ` [PATCH 04/10] mm: alloc_contig_freed_pages() added Marek Szyprowski
2011-06-10  9:54 ` [PATCH 05/10] mm: alloc_contig_range() added Marek Szyprowski
2011-06-10  9:54 ` [PATCH 06/10] mm: MIGRATE_CMA migration type added Marek Szyprowski
2011-06-10  9:54 ` [PATCH 07/10] mm: MIGRATE_CMA isolation functions added Marek Szyprowski
2011-06-10  9:54 ` [PATCH 08/10] mm: cma: Contiguous Memory Allocator added Marek Szyprowski
2011-06-10 16:21   ` Arnd Bergmann
2011-06-13  9:05     ` Marek Szyprowski
2011-06-14 13:49       ` Arnd Bergmann
2011-06-14 13:55         ` Michal Nazarewicz
2011-06-14 16:03           ` Arnd Bergmann
2011-06-14 16:58             ` Michal Nazarewicz
2011-06-14 18:30               ` Arnd Bergmann
2011-06-14 18:40                 ` Michal Nazarewicz [this message]
2011-06-15  7:11                 ` Marek Szyprowski
2011-06-15  7:37                   ` Arnd Bergmann
2011-06-15  8:14                     ` Marek Szyprowski
2011-06-16  0:48                     ` [Linaro-mm-sig] " Philip Balister
2011-06-16  7:03                       ` Arnd Bergmann
2011-06-22  7:03                     ` Hans Verkuil
2011-06-22  7:32                       ` Michal Nazarewicz
2011-06-22 12:42                       ` Arnd Bergmann
2011-06-22 13:15                         ` Marek Szyprowski
2011-06-22 13:39                           ` Arnd Bergmann
2011-06-22 16:04                             ` Michal Nazarewicz
2011-06-22 15:54                           ` Michal Nazarewicz
2011-06-15 11:53                 ` Daniel Vetter
2011-06-15 13:12                   ` Thomas Hellstrom
2011-06-17 16:08                   ` Arnd Bergmann
2011-06-14 17:01             ` Daniel Stone
2011-06-14 18:58               ` Zach Pfeffer
2011-06-14 20:42                 ` Arnd Bergmann
2011-06-14 21:01                   ` Jordan Crouse
2011-06-15 11:27                     ` Arnd Bergmann
2011-06-15  6:29                   ` Subash Patel
2011-06-15  8:36                   ` Marek Szyprowski
2011-06-15 21:39                     ` Larry Bassel
2011-06-15 22:06                       ` Arnd Bergmann
2011-06-16 17:01                         ` Larry Bassel
2011-06-17 12:45                           ` Arnd Bergmann
2011-07-04  5:25                         ` Ankita Garg
2011-07-04 14:45                           ` Arnd Bergmann
2011-06-16  3:20                       ` Zach Pfeffer
2011-06-15  9:26                   ` Michal Nazarewicz
2011-06-15 11:20                     ` Arnd Bergmann
2011-06-15 11:30                       ` Michal Nazarewicz
2011-06-15  6:01             ` Subash Patel
2011-06-15  8:02         ` Marek Szyprowski
2011-06-15 11:14           ` Arnd Bergmann
2011-06-10  9:54 ` [PATCH 09/10] ARM: integrate CMA with dma-mapping subsystem Marek Szyprowski
2011-06-10  9:54 ` [PATCH 10/10] ARM: S5PV210: add CMA support for FIMC devices on Aquila board Marek Szyprowski

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=op.vw2wt8cs3l0zgt@mnazarewicz-glaptop \
    --to=mina86@mina86.com \
    --cc=linux-arm-kernel@lists.infradead.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