DSPBRIDGE: Improved reserved and mapped resource cleanup
Status from this message: Pushed to dspbridge
Get series with b4
b4 am [email protected]Versions newest first · linked by author and title
- v5 Latest4 patches 6 repliesApplied
- v44 patches 6 repliesSuperseded
- v32 patches 0 repliesSuperseded
Earlier versions · 2
| Version | Posted | Patches | Replies | Status |
|---|---|---|---|---|
| v2 | 2 patches | 5 replies | Superseded | |
| v1 | 2 patches | 1 reply | Superseded |
Changes in v5 from the cover letter
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
Patches in v5 Applied
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/4 | DSPBRIDGE: Rename DMM_RES_OBJECT to DMM_MAP_OBJECTarch/ drivers/ drivers/ | +43 | 1 reply | |
| 2/4 | DSPBRIDGE: New reserved memory accounting frameworkarch/ arch/ drivers/ +4 more | +83 | 1 reply | |
| 3/4 | DSPBRIDGE: Fix memory corruption in DRV_ProcFreeDMMResdrivers/ | +2 | 1 reply | |
| 4/4 | DSPBRIDGE: Improved mapped memory cleanuparch/ arch/ drivers/ +2 more | +54 | 1 reply |
Reviews trailers per patch
1 of 4 patches has a Reviewed-by or Acked-by of their own; the series has one for all of them.
| Patch | Felipe Contreras | Fernando Guzman Lugo |
|---|---|---|
| Series | Reviwed-by | A-b |
| 1/4 | R-b | |
| 2/4 | ||
| 3/4 | ||
| 4/4 |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [PATCHv5 0/4] DSPBRIDGE: Improved reserved and mapped resource cleanup
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(-)