Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1424863

Re: [PATCH v2 6/7] mm/page_owner: use stackdepot to store stacktrace

From Michal Hocko <mhocko@kernel.org>
Newsgroups linux.kernel
Subject Re: [PATCH v2 6/7] mm/page_owner: use stackdepot to store stacktrace
Date 2016-06-17 12:00 +0200
Message-ID <rKYJb-4U2-1@gated-at.bofh.it> (permalink)
References <rCTnj-te-3@gated-at.bofh.it> <rCTnk-te-13@gated-at.bofh.it> <rH3ep-5FP-13@gated-at.bofh.it> <rKWo1-3vB-17@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


On Fri 17-06-16 16:25:26, Joonsoo Kim wrote:
> On Mon, Jun 06, 2016 at 03:56:04PM +0200, Michal Hocko wrote:
[...]
> > I still have troubles to understand your numbers
> > 
> > > static allocation:
> > > 92274688 bytes -> 25165824 bytes
> > 
> > I assume that the first numbers refers to the static allocation for the
> > given amount of memory while the second one is the dynamic after the
> > boot, right?
> 
> No, first number refers to the static allocation before the patch and
> second one is for after the patch.

I guess we are both talking about the same thing in different words. All
the allocations are static before the patch while all are dynamic after
the patch. Your boot example just shows how much dynamic memory gets
allocated during your boot. This will depend on the particular
configuration but it will at least give a picture what the savings might
be.
-- 
Michal Hocko
SUSE Labs

Back to linux.kernel | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


Thread

Re: [PATCH v2 6/7] mm/page_owner: use stackdepot to store stacktrace Joonsoo Kim <iamjoonsoo.kim@lge.com> - 2016-06-17 09:30 +0200
  Re: [PATCH v2 6/7] mm/page_owner: use stackdepot to store stacktrace Michal Hocko <mhocko@kernel.org> - 2016-06-17 12:00 +0200
    Re: [PATCH v2 6/7] mm/page_owner: use stackdepot to store stacktrace Joonsoo Kim <iamjoonsoo.kim@lge.com> - 2016-06-20 09:00 +0200

csiph-web