public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
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,
	x0095840@ti.com, omar.ramirez@ti.com
Subject: [PATCHv5 0/4] DSPBRIDGE: Improved reserved and mapped resource cleanup
Date: Thu, 18 Feb 2010 16:40:49 +0200	[thread overview]
Message-ID: <cover.1266503387.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.

Changes since v4:
1. Replace unnecessary list_for_each_entry_safe to list_for_each_entry
   http://marc.info/?l=linux-omap&m=126645721715598&w=2
2. Comments at appropriate places to explain resource tracking objects
   insertion and removals.
   http://marc.info/?l=linux-omap&m=126649541624172&w=2

Changes since v3:
1. Improved mapped memory resource cleanup

Changes since v2:
1. Removed locking from DRV_RemoveAllDMMResElements()
2. Removed cleanup variable from PROC_UnReserveMemory()
   http://marc.info/?l=linux-omap&m=126637211831587&w=2
3. Rebased patchset on top of following commit:
   DSPBRIDGE: Remove conditional check from the InputMsg function

Changed since v1:
1. Reduced indentation
   http://marc.info/?l=linux-omap&m=126624982331523&w=2

Ameya Palande (4):
  DSPBRIDGE: Rename DMM_RES_OBJECT to DMM_MAP_OBJECT
  DSPBRIDGE: New reserved memory accounting framework
  DSPBRIDGE: Fix memory corruption in DRV_ProcFreeDMMRes
  DSPBRIDGE: Improved mapped memory cleanup

 arch/arm/plat-omap/include/dspbridge/drv.h         |   44 ++---
 arch/arm/plat-omap/include/dspbridge/proc.h        |    4 +-
 .../plat-omap/include/dspbridge/resourcecleanup.h  |   11 --
 drivers/dsp/bridge/pmgr/wcd.c                      |    7 +-
 drivers/dsp/bridge/rmgr/drv.c                      |  176 +++-----------------
 drivers/dsp/bridge/rmgr/drv_interface.c            |    5 +-
 drivers/dsp/bridge/rmgr/node.c                     |    5 +-
 drivers/dsp/bridge/rmgr/proc.c                     |  105 +++++++++---
 8 files changed, 134 insertions(+), 223 deletions(-)


             reply	other threads:[~2010-02-18 14:41 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-18 14:40 Ameya Palande [this message]
2010-02-18 14:40 ` [PATCH 1/4] DSPBRIDGE: Rename DMM_RES_OBJECT to DMM_MAP_OBJECT Ameya Palande
2010-02-23 16:23   ` Omar Ramirez Luna
2010-02-18 14:40 ` [PATCH 2/4] DSPBRIDGE: New reserved memory accounting framework Ameya Palande
2010-02-23 16:23   ` Omar Ramirez Luna
2010-02-18 14:40 ` [PATCH 3/4] DSPBRIDGE: Fix memory corruption in DRV_ProcFreeDMMRes Ameya Palande
2010-02-23 16:23   ` Omar Ramirez Luna
2010-02-18 14:40 ` [PATCH 4/4] DSPBRIDGE: Improved mapped memory cleanup Ameya Palande
2010-02-23 16:23   ` Omar Ramirez Luna
2010-02-18 18:16 ` [PATCHv5 0/4] DSPBRIDGE: Improved reserved and mapped resource cleanup Felipe Contreras
2010-02-18 22:46 ` 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.1266503387.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