From: Greg KH <gregkh@linuxfoundation.org>
To: Feng Tang <feng.tang@intel.com>
Cc: John Stultz <john.stultz@linaro.org>,
linux-kernel@vger.kernel.org, Colin Cross <ccross@android.com>,
Heesub Shin <heesub.shin@samsung.com>,
Mitchel Humpherys <mitchelh@codeaurora.org>
Subject: Re: [PATCH 2/2] staging: android: ion: Add pss info for each ion_client
Date: Mon, 19 Jan 2015 10:23:50 +0800 [thread overview]
Message-ID: <20150119022350.GB1094@kroah.com> (raw)
In-Reply-To: <1421632825-1538-1-git-send-email-feng.tang@intel.com>
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@intel.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
next prev parent reply other threads:[~2015-01-19 2:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-19 2:00 Feng Tang
2015-01-19 2:23 ` Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-01-04 7:11 [PATCH 1/2] staging: andriod: ion: Add ion_phys_get_by_id function Feng Tang
2015-01-04 7:11 ` [PATCH 2/2] staging: android: ion: Add pss info for each ion_client Feng Tang
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=20150119022350.GB1094@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=ccross@android.com \
--cc=feng.tang@intel.com \
--cc=heesub.shin@samsung.com \
--cc=john.stultz@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mitchelh@codeaurora.org \
/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
all inboxes | Powered by JetHome®