linux-kernel - Re: [PATCH 2/2] staging: android: ion: Add pss info for each ion

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Mon, 19 Jan 2015 10:23:50 +0800
From:	Greg KH <gregkh@...uxfoundation.org>
To:	Feng Tang <feng.tang@...el.com>
Cc:	John Stultz <john.stultz@...aro.org>, linux-kernel@...r.kernel.org,
	Colin Cross <ccross@...roid.com>,
	Heesub Shin <heesub.shin@...sung.com>,
	Mitchel Humpherys <mitchelh@...eaurora.org>
Subject: Re: [PATCH 2/2] staging: android: ion: Add pss info for each
 ion_client

On Mon, Jan 19, 2015 at 10:00:25AM +0800, Feng Tang wrote:
> In real ION buffer usage, many of the ion buffer are shared
> by several clients(imported and exported), and current ion
> debugfs only provides size of all buffers a client may use.
> This patch will considers the sharing and adds a "pss" info
> for each ion_client, which will help on profiling the ion
> memory usage.
> 
> Actually we can do more aggressively in android world, in
> which the "surfaceflinger" is a main proxy to help other
> apps to do the ion buffer allocation, and we can consider
> this and extract "surfaceflinger" related size out. And
> this could be the next step.
> 
> Signed-off-by: Feng Tang <feng.tang@...el.com>
> ---
>  drivers/staging/android/ion/ion.c |   25 +++++++++++++++++--------
>  1 file changed, 17 insertions(+), 8 deletions(-)

I really need others to review and test this with their systems before I
can accept it.  So I'll have to wait for an ack from John or Colin or
someone else...

thanks,

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/