From: Ameya Palande <ameya.palande@nokia.com>
To: linux-omap@vger.kernel.org
Cc: felipe.contreras@nokia.com, nm@ti.com, deepak.chitriki@ti.com,
omar.ramirez@ti.com, x0095840@ti.com
Subject: [PATCHv2 0/2] DSPBRIDGE: Improved reserved memory cleanup
Date: Tue, 16 Feb 2010 15:20:07 +0200 [thread overview]
Message-ID: <cover.1266326009.git.ameya.palande@nokia.com> (raw)
This patch series splits DMM_RES_OBJECT into DMM_MAP_OBJECT and DMM_RSV_OBJECT
which are used independently for mapped and reserved memory resources
accounting. This will help in cleanup of reserved memory resources which was
not handled properly before. With these patches resource cleanup mechanism
will work perfectly in a use case where a big chunk of memory is reserved and
then lot of mappings are created inside it.
v2: Addresses following comments about reducing indentation
http://marc.info/?l=linux-omap&m=126624982331523&w=2
Ameya Palande (2):
DSPBRIDGE: Rename DMM_RES_OBJECT to DMM_MAP_OBJECT
DSPBRIDGE: New reserved memory accounting framework
arch/arm/plat-omap/include/dspbridge/drv.h | 25 ++++++--
arch/arm/plat-omap/include/dspbridge/proc.h | 5 +-
drivers/dsp/bridge/pmgr/dmm.c | 3 +-
drivers/dsp/bridge/pmgr/wcd.c | 7 +-
drivers/dsp/bridge/rmgr/drv.c | 84 ++++++++++++++++-----------
drivers/dsp/bridge/rmgr/drv_interface.c | 7 ++-
drivers/dsp/bridge/rmgr/node.c | 5 +-
drivers/dsp/bridge/rmgr/proc.c | 58 +++++++++++++++----
8 files changed, 132 insertions(+), 62 deletions(-)
next reply other threads:[~2010-02-16 13:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-16 13:20 Ameya Palande [this message]
2010-02-16 13:20 ` [PATCH 1/2] DSPBRIDGE: Rename DMM_RES_OBJECT to DMM_MAP_OBJECT Ameya Palande
2010-02-16 18:27 ` Felipe Contreras
2010-02-16 13:20 ` [PATCH 2/2] DSPBRIDGE: New reserved memory accounting framework Ameya Palande
2010-02-16 18:42 ` Felipe Contreras
2010-02-17 2:05 ` Guzman Lugo, Fernando
2010-02-17 9:50 ` Felipe Contreras
2010-02-17 2:01 ` Guzman Lugo, Fernando
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=cover.1266326009.git.ameya.palande@nokia.com \
--to=ameya.palande@nokia.com \
--cc=deepak.chitriki@ti.com \
--cc=felipe.contreras@nokia.com \
--cc=linux-omap@vger.kernel.org \
--cc=nm@ti.com \
--cc=omar.ramirez@ti.com \
--cc=x0095840@ti.com \
/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