From: "Michał Nazarewicz" <m.nazarewicz@samsung.com>
To: linux-mm@kvack.org, Johan Mossberg <johan.xx.mossberg@stericsson.com>
Subject: Re: [PATCH 0/3] hwmem: Hardware memory driver
Date: Tue, 16 Nov 2010 15:50:16 +0100 [thread overview]
Message-ID: <op.vl9p52wp7p4s8u@pikus> (raw)
In-Reply-To: <1289912882-23996-1-git-send-email-johan.xx.mossberg@stericsson.com>
On Tue, 16 Nov 2010 14:07:59 +0100, Johan Mossberg <johan.xx.mossberg@stericsson.com> wrote:
> The following patchset implements a "hardware memory driver". The
> main purpose of hwmem is:
>
> * To allocate buffers suitable for use with hardware. Currently
> this means contiguous buffers.
> * To synchronize the caches for the allocated buffers. This is
> achieved by keeping track of when the CPU uses a buffer and when
> other hardware uses the buffer, when we switch from CPU to other
> hardware or vice versa the caches are synchronized.
> * To handle sharing of allocated buffers between processes i.e.
> import, export.
>
> Hwmem is available both through a user space API and through a
> kernel API.
>
> Here at ST-Ericsson we use hwmem for graphics buffers. Graphics
> buffers need to be contiguous due to our hardware, are passed
> between processes (usually application and window manager)and are
> part of usecases where performance is top priority so we can't
> afford to synchronize the caches unecessarily.
>
> Hwmem and CMA (Contiguous Memory Allocator) overlap to some extent.
> Hwmem could use CMA as its allocator and thereby remove the overlap
> but then defragmentation can not be implemented as CMA currently
> has no support for this. We would very much like to see a
> discussion about adding defragmentation to CMA.
I would definitelly like to see what the two solution share and try to
merge those.
In particular, I'll try to figure out what you mean by defragmentation
and see whethe it could be added to CMA.
My idea about CMA is to provide only allocator framework and let others
interact with user space and/or share resources, which, as I understand,
hwmem does.
PS. I don't follow linux-mm carefully, so I'd be great if you'd Cc me on
future versions of hwmem.
--
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--
--
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/ .
Fight unfair telecom policy in Canada: sign http://dissolvethecrtc.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2010-11-16 14:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-16 13:07 Johan Mossberg
2010-11-16 13:08 ` [PATCH 1/3] hwmem: Add hwmem (part 1) Johan Mossberg
2010-11-16 13:08 ` [PATCH 2/3] hwmem: Add hwmem (part 2) Johan Mossberg
2010-11-16 13:08 ` [PATCH 3/3] hwmem: Add hwmem to ux500 and mop500 Johan Mossberg
2010-11-16 14:50 ` Michał Nazarewicz [this message]
2010-11-16 15:25 ` [PATCH 0/3] hwmem: Hardware memory driver Johan MOSSBERG
2010-11-16 15:33 ` Michał Nazarewicz
2010-11-16 16:16 ` Johan MOSSBERG
2010-11-16 17:36 ` Michał Nazarewicz
2010-11-17 9:28 ` Johan MOSSBERG
2010-11-19 10:44 ` Michał Nazarewicz
2010-11-19 13:47 ` Johan MOSSBERG
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.vl9p52wp7p4s8u@pikus \
--to=m.nazarewicz@samsung.com \
--cc=johan.xx.mossberg@stericsson.com \
--cc=linux-mm@kvack.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