Hi, Hi Ameya, Patches look good only one comment, In PROC_Attach: =============== - Why don't use only one hProcessor? If hProcessor already exists then just return the pointer. We can use a counter to know when to release the handle. Or maybe we can do the Detach only in bridge_release but that might imply to leave the exported detach function "empty" or do not export detach function but it would impact the dspbridge users. That would avoid the use of a list to keep track of the handles. Let me try your patch with this modification and I'll let you know. /Ernesto > -----Original Message----- > From: Ameya Palande [mailto:ameya.palande@xxxxxxxxx] > Sent: Monday, August 10, 2009 8:22 PM > To: linux-omap@xxxxxxxxxxxxxxx > Cc: hiroshi.doyu@xxxxxxxxx; Ramirez Luna, Omar; Guzman Lugo, Fernando; > Moogi, Suyog; roman.tereshonkov@xxxxxxxxx; Ramos Falcon, Ernesto > Subject: DSPBRIDGE: Tie Resource accounting to Process Context > > This patch series uses filp->private data to get access to a > PROCESS_CONTEXT > pointer which in turn tracks all the resources tied to an open file > handle. > > This will help in: > 1. Implementation of clean resource accounting. > 2. Proper resource cleanup irrespective of multithreading or multitasking > in > user space applications. > -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
