From: Andrew Morton <akpm@linux-foundation.org>
To: Anshuman Khandual <khandual@linux.vnet.ibm.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] mm: Add sysfs interface to dump each node's zonelist information
Date: Wed, 31 Aug 2016 14:12:39 -0700 [thread overview]
Message-ID: <20160831141239.9624b38201796007c2735029@linux-foundation.org> (raw)
In-Reply-To: <1472613950-16867-2-git-send-email-khandual@linux.vnet.ibm.com>
On Wed, 31 Aug 2016 08:55:50 +0530 Anshuman Khandual <khandual@linux.vnet.ibm.com> wrote:
> Each individual node in the system has a ZONELIST_FALLBACK zonelist
> and a ZONELIST_NOFALLBACK zonelist. These zonelists decide fallback
> order of zones during memory allocations. Sometimes it helps to dump
> these zonelists to see the priority order of various zones in them.
> This change just adds a sysfs interface for doing the same.
>
> Example zonelist information from a KVM guest.
>
> [NODE (0)]
> ZONELIST_FALLBACK
> (0) (node 0) (zone DMA c00000000140c000)
> (1) (node 1) (zone DMA c000000100000000)
> (2) (node 2) (zone DMA c000000200000000)
> (3) (node 3) (zone DMA c000000300000000)
> ZONELIST_NOFALLBACK
> (0) (node 0) (zone DMA c00000000140c000)
> [NODE (1)]
> ZONELIST_FALLBACK
> (0) (node 1) (zone DMA c000000100000000)
> (1) (node 2) (zone DMA c000000200000000)
> (2) (node 3) (zone DMA c000000300000000)
> (3) (node 0) (zone DMA c00000000140c000)
> ZONELIST_NOFALLBACK
> (0) (node 1) (zone DMA c000000100000000)
> [NODE (2)]
> ZONELIST_FALLBACK
> (0) (node 2) (zone DMA c000000200000000)
> (1) (node 3) (zone DMA c000000300000000)
> (2) (node 0) (zone DMA c00000000140c000)
> (3) (node 1) (zone DMA c000000100000000)
> ZONELIST_NOFALLBACK
> (0) (node 2) (zone DMA c000000200000000)
> [NODE (3)]
> ZONELIST_FALLBACK
> (0) (node 3) (zone DMA c000000300000000)
> (1) (node 0) (zone DMA c00000000140c000)
> (2) (node 1) (zone DMA c000000100000000)
> (3) (node 2) (zone DMA c000000200000000)
> ZONELIST_NOFALLBACK
> (0) (node 3) (zone DMA c000000300000000)
Can you please sell this a bit better? Why does it "sometimes help"?
Why does the benefit of this patch to our users justify the overhead
and cost?
Please document the full path to the sysfs file(s) within the changelog.
Please find somewhere in Documentation/ to document the new interface.
next prev parent reply other threads:[~2016-08-31 21:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-31 3:25 [PATCH 1/2] mm: Move definition of 'zone_names' array into mmzone.h Anshuman Khandual
2016-08-31 3:25 ` [PATCH 2/2] mm: Add sysfs interface to dump each node's zonelist information Anshuman Khandual
2016-08-31 21:12 ` Andrew Morton [this message]
2016-09-02 4:34 ` Anshuman Khandual
2016-08-31 21:10 ` [PATCH 1/2] mm: Move definition of 'zone_names' array into mmzone.h Andrew Morton
2016-09-02 4:29 ` Anshuman Khandual
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=20160831141239.9624b38201796007c2735029@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=khandual@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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®