From: Ameya Palande <ameya.palande@nokia.com>
To: "ext Guzman Lugo, Fernando" <x0095840@ti.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"Contreras Felipe (Nokia-D/Helsinki)"
<felipe.contreras@nokia.com>, "Menon, Nishanth" <nm@ti.com>,
"Chitriki Rudramuni, Deepak" <deepak.chitriki@ti.com>,
"Ramirez Luna, Omar" <omar.ramirez@ti.com>
Subject: RE: [PATCHv4 4/4] DSPBRIDGE: Improved mapped memory cleanup
Date: Thu, 18 Feb 2010 14:15:55 +0200 [thread overview]
Message-ID: <1266495355.2105.5.camel@sanganak> (raw)
In-Reply-To: <496565EC904933469F292DDA3F1663E602CA2B9AD9@dlee06.ent.ti.com>
Hi Fernando,
On Thu, 2010-02-18 at 02:52 +0100, ext Guzman Lugo, Fernando wrote:
> Hi,
>
> >-----Original Message-----
> >From: Ameya Palande [mailto:ameya.palande@nokia.com]
> >Sent: Wednesday, February 17, 2010 12:06 PM
> >To: linux-omap@vger.kernel.org
> >Cc: felipe.contreras@nokia.com; Menon, Nishanth; Chitriki Rudramuni,
> >Deepak; Guzman Lugo, Fernando; Ramirez Luna, Omar
> >Subject: [PATCHv4 4/4] DSPBRIDGE: Improved mapped memory cleanup
> >
> >This patch improves current mapped memory cleanup mechanism by using linux
> >native list implementation. As a side effect we also get following
> >benefits:
> >
> >1. Unnecessary data members in DMM_MAP_OBJECT are removed which results in
> > memory saving.
> >
> >2. Following functions are removed as they are not needed anymore:
> > DRV_ProcFreeDMMRes()
> > DRV_UpdateDMMResElement()
> > DRV_InsertDMMResElement()
> > DRV_GetDMMResElement()
> > DRV_RemoveDMMResElement()
> >
> >Signed-off-by: Ameya Palande <ameya.palande@nokia.com>
> >---
> >@@ -1334,11 +1333,17 @@ DSP_STATUS PROC_Map(DSP_HPROCESSOR hProcessor, void
> >*pMpuAddr, u32 ulSize,
> > }
> > (void)SYNC_LeaveCS(hProcLock);
> >
> >- if (DSP_SUCCEEDED(status)) {
> >- DRV_InsertDMMResElement(&dmmRes, pr_ctxt);
> >- DRV_UpdateDMMResElement(dmmRes, (u32)pMpuAddr, ulSize,
> >- (u32)pReqAddr, (u32)*ppMapAddr, hProcessor);
> >+ if (DSP_FAILED(status))
> >+ goto func_end;
> >+
> >+ map_obj = kmalloc(sizeof(struct DMM_MAP_OBJECT), GFP_KERNEL);
> >+ if (map_obj) {
> >+ map_obj->dsp_addr = (u32)*ppMapAddr;
> >+ spin_lock(&pr_ctxt->dmm_map_lock);
> >+ list_add(&map_obj->link, &pr_ctxt->dmm_map_list);
> >+ spin_unlock(&pr_ctxt->dmm_map_lock);
> > }
>
> What do you think about it?
> Instead of removing DRV_InsertDMMResElement make it an inline function with your code inside:
Making DRV_InsertDMMResElement inline doesn't make sense since we are
not calling it multiple times.
> inline void DRV_InsertDMMResElement(u32 ppMapAddr)
> {
> map_obj = kmalloc(sizeof(struct DMM_MAP_OBJECT), GFP_KERNEL);
> if (map_obj) {
> map_obj->dsp_addr = (u32)*ppMapAddr;
> spin_lock(&pr_ctxt->dmm_map_lock);
> list_add(&map_obj->link, &pr_ctxt->dmm_map_list);
> spin_unlock(&pr_ctxt->dmm_map_lock);
> }
> }
>
> It could make the code more understandable about what it is actually doing.
> It also applies to the functions which removes this patch.
I can put a comment here to clarify what this code is doing ;)
Cheers,
Ameya.
next prev parent reply other threads:[~2010-02-18 12:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-17 18:05 [PATCHv4 0/4] DSPBRIDGE: Improved reserved and mapped resource cleanup Ameya Palande
2010-02-17 18:05 ` [PATCHv4 1/4] DSPBRIDGE: Rename DMM_RES_OBJECT to DMM_MAP_OBJECT Ameya Palande
2010-02-17 18:05 ` [PATCHv4 2/4] DSPBRIDGE: New reserved memory accounting framework Ameya Palande
2010-02-18 1:40 ` Guzman Lugo, Fernando
2010-02-18 14:48 ` Ameya Palande
2010-02-17 18:05 ` [PATCHv4 3/4] DSPBRIDGE: Fix memory corruption in DRV_ProcFreeDMMRes Ameya Palande
2010-02-17 18:05 ` [PATCHv4 4/4] DSPBRIDGE: Improved mapped memory cleanup Ameya Palande
2010-02-18 1:52 ` Guzman Lugo, Fernando
2010-02-18 12:15 ` Ameya Palande [this message]
2010-02-18 14:27 ` Felipe Contreras
2010-02-18 14:47 ` Ameya Palande
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=1266495355.2105.5.camel@sanganak \
--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