linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Michal Nazarewicz <mina86@mina86.com>
Cc: Pintu Kumar <pintu.k@samsung.com>,
	riel@redhat.com, aquini@redhat.com, paul.gortmaker@windriver.com,
	jmarchan@redhat.com, lcapitulino@redhat.com,
	kirill.shutemov@linux.intel.com, m.szyprowski@samsung.com,
	aneesh.kumar@linux.vnet.ibm.com, iamjoonsoo.kim@lge.com,
	lauraa@codeaurora.org, gioh.kim@lge.com, mgorman@suse.de,
	rientjes@google.com, hannes@cmpxchg.org, vbabka@suse.cz,
	sasha.levin@oracle.com, linux-kernel@vger.kernel.org,
	linux-mm@kvack.org, pintu_agarwal@yahoo.com, cpgs@samsung.com,
	vishnu.ps@samsung.com, rohit.kr@samsung.com,
	ed.savinay@samsung.com
Subject: Re: [PATCH v2 2/2] fs: proc: Include cma info in proc/meminfo
Date: Mon, 27 Oct 2014 16:15:44 -0700	[thread overview]
Message-ID: <20141027161544.8955c1df4c01c48e22283692@linux-foundation.org> (raw)
In-Reply-To: <xa1tk33p2zvq.fsf@mina86.com>

On Fri, 24 Oct 2014 18:31:21 +0200 Michal Nazarewicz <mina86@mina86.com> wrote:

> On Wed, Oct 22 2014, Pintu Kumar <pintu.k@samsung.com> wrote:
> > This patch include CMA info (CMATotal, CMAFree) in /proc/meminfo.
> > Currently, in a CMA enabled system, if somebody wants to know the
> > total CMA size declared, there is no way to tell, other than the dmesg
> > or /var/log/messages logs.
> > With this patch we are showing the CMA info as part of meminfo, so that
> > it can be determined at any point of time.
> > This will be populated only when CMA is enabled.
> >
> > Below is the sample output from a ARM based device with RAM:512MB and CMA:16MB.
> >
> > MemTotal:         471172 kB
> > MemFree:          111712 kB
> > MemAvailable:     271172 kB
> > .
> > .
> > .
> > CmaTotal:          16384 kB
> > CmaFree:            6144 kB
> >
> > This patch also fix below checkpatch errors that were found during these changes.
> 
> As already mentioned, this should be in separate patch.

Yes, in theory.  But a couple of little whitespace fixes aren't really
worth a resend.  As long as they don't make the patch harder to read
and to backport I usually just let them through.

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2014-10-27 23:15 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-20  7:33 [PATCH] mm: cma: split cma-reserved in dmesg log Pintu Kumar
2014-10-20  9:35 ` Michal Nazarewicz
2014-10-20 22:48 ` Andrew Morton
2014-10-21  0:47 ` Gioh Kim
2014-10-21 13:21   ` PINTU KUMAR
2014-10-21 23:55     ` Gioh Kim
2014-10-22 14:06 ` [PATCH v2 1/2] " Pintu Kumar
2014-10-22 14:06   ` [PATCH v2 2/2] fs: proc: Include cma info in proc/meminfo Pintu Kumar
2014-10-22 20:00     ` Andrew Morton
2014-10-23  0:19     ` Gioh Kim
2014-10-24  8:57       ` PINTU KUMAR
2014-10-24 10:10         ` Gioh Kim
2014-10-24 10:43           ` PINTU KUMAR
2014-10-24 16:31     ` Michal Nazarewicz
2014-10-27 23:15       ` Andrew Morton [this message]
2014-10-23 17:01   ` [PATCH v2 1/2] mm: cma: split cma-reserved in dmesg log Michal Nazarewicz
2014-10-24 10:30     ` PINTU KUMAR
2014-10-24 16:32       ` Michal Nazarewicz
2014-11-03 23:57   ` David Rientjes
2014-11-04 17:15     ` PINTU KUMAR

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=20141027161544.8955c1df4c01c48e22283692@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=aneesh.kumar@linux.vnet.ibm.com \
    --cc=aquini@redhat.com \
    --cc=cpgs@samsung.com \
    --cc=ed.savinay@samsung.com \
    --cc=gioh.kim@lge.com \
    --cc=hannes@cmpxchg.org \
    --cc=iamjoonsoo.kim@lge.com \
    --cc=jmarchan@redhat.com \
    --cc=kirill.shutemov@linux.intel.com \
    --cc=lauraa@codeaurora.org \
    --cc=lcapitulino@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=m.szyprowski@samsung.com \
    --cc=mgorman@suse.de \
    --cc=mina86@mina86.com \
    --cc=paul.gortmaker@windriver.com \
    --cc=pintu.k@samsung.com \
    --cc=pintu_agarwal@yahoo.com \
    --cc=riel@redhat.com \
    --cc=rientjes@google.com \
    --cc=rohit.kr@samsung.com \
    --cc=sasha.levin@oracle.com \
    --cc=vbabka@suse.cz \
    --cc=vishnu.ps@samsung.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