From: Mel Gorman <mel@csn.ul.ie>
To: Eric B Munson <ebmunson@us.ibm.com>
Cc: linux-mm@kvack.org, aglitke@us.ibm.com
Subject: Re: [PATCH] hugetlb: vmstat events for huge page allocations v3
Date: Thu, 27 Mar 2008 17:00:58 +0000 [thread overview]
Message-ID: <20080327170058.GB7120@csn.ul.ie> (raw)
In-Reply-To: <1205784175.7122.2.camel@grover.beaverton.ibm.com>
On (17/03/08 13:02), Eric B Munson didst pronounce:
> From: Adam Litke <agl@us.ibm.com>
>
> Following feedback here is v3
>
> Allocating huge pages directly from the buddy allocator is not guaranteed
> to succeed. Success depends on several factors (such as the amount of
> physical memory available and the level of fragmentation). With the
> addition of dynamic hugetlb pool resizing, allocations can occur much more
> frequently. For these reasons it is desirable to keep track of huge page
> allocation successes and failures.
>
> Add two new vmstat entries to track huge page allocations that succeed and
> fail. The presence of the two entries is contingent upon
> CONFIG_HUGETLB_PAGE being enabled.
>
> This patch was created against linux-2.6.25-rc5
>
It applied cleanly to 2.6.25-rc5-mm1 as well so I tested using a small x86
machine and found no problems. There was one curiousity with libhugetlbfs
with dynamic pool resizing was that two failures were accounted for when the
mapping was larger than the number of huge pages could be allocated. However,
it turned out that the first failure was libhugetlbfs calling mlock() but
not existing on failure and the second was the page fault. So, while I didn't
expect it in advance, it is still correct accounting.
Tested-by: Mel Gorman <mel@csn.ul.ie>
> Signed-off-by: Adam Litke <agl@us.ibm.com>
> Signed-off-by: Eric Munson <ebmunson@us.ibm.com>
>
> include/linux/vmstat.h | 8 +++++++-
> mm/hugetlb.c | 7 +++++++
> mm/vmstat.c | 4 ++++
> 3 files changed, 18 insertions(+), 1 deletions(-)
>
> diff --git a/include/linux/vmstat.h b/include/linux/vmstat.h
> index 9f1b4b4..f68f538 100644
> --- a/include/linux/vmstat.h
> +++ b/include/linux/vmstat.h
> @@ -25,6 +25,12 @@
> #define HIGHMEM_ZONE(xx)
> #endif
>
> +#ifdef CONFIG_HUGETLB_PAGE
> +#define HTLB_STATS HTLB_BUDDY_PGALLOC, HTLB_BUDDY_PGALLOC_FAIL,
> +#else
> +#define HTLB_STATS
> +#endif
> +
> #define FOR_ALL_ZONES(xx) DMA_ZONE(xx) DMA32_ZONE(xx) xx##_NORMAL HIGHMEM_ZONE(xx) , xx##_MOVABLE
>
> enum vm_event_item { PGPGIN, PGPGOUT, PSWPIN, PSWPOUT,
> @@ -36,7 +42,7 @@ enum vm_event_item { PGPGIN, PGPGOUT, PSWPIN, PSWPOUT,
> FOR_ALL_ZONES(PGSCAN_KSWAPD),
> FOR_ALL_ZONES(PGSCAN_DIRECT),
> PGINODESTEAL, SLABS_SCANNED, KSWAPD_STEAL, KSWAPD_INODESTEAL,
> - PAGEOUTRUN, ALLOCSTALL, PGROTATED,
> + PAGEOUTRUN, ALLOCSTALL, PGROTATED, HTLB_STATS
> NR_VM_EVENT_ITEMS
> };
>
> diff --git a/mm/hugetlb.c b/mm/hugetlb.c
> index 74c1b6b..dd20cb0 100644
> --- a/mm/hugetlb.c
> +++ b/mm/hugetlb.c
> @@ -239,6 +239,11 @@ static int alloc_fresh_huge_page(void)
> hugetlb_next_nid = next_nid;
> } while (!page && hugetlb_next_nid != start_nid);
>
> + if (ret)
> + count_vm_event(HTLB_BUDDY_PGALLOC);
> + else
> + count_vm_event(HTLB_BUDDY_PGALLOC_FAIL);
> +
> return ret;
> }
>
> @@ -299,9 +304,11 @@ static struct page *alloc_buddy_huge_page(struct vm_area_struct *vma,
> */
> nr_huge_pages_node[nid]++;
> surplus_huge_pages_node[nid]++;
> + __count_vm_event(HTLB_BUDDY_PGALLOC);
> } else {
> nr_huge_pages--;
> surplus_huge_pages--;
> + __count_vm_event(HTLB_BUDDY_PGALLOC_FAIL);
> }
> spin_unlock(&hugetlb_lock);
>
> diff --git a/mm/vmstat.c b/mm/vmstat.c
> index 422d960..bbe728d 100644
> --- a/mm/vmstat.c
> +++ b/mm/vmstat.c
> @@ -644,6 +644,10 @@ static const char * const vmstat_text[] = {
> "allocstall",
>
> "pgrotated",
> +#ifdef CONFIG_HUGETLB_PAGE
> + "htlb_alloc_success",
> + "htlb_alloc_fail",
> +#endif
> #endif
> };
>
--
Mel Gorman
Part-time Phd Student Linux Technology Center
University of Limerick IBM Dublin Software Lab
--
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>
next prev parent reply other threads:[~2008-03-27 17:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-17 20:02 Eric B Munson
2008-03-27 17:00 ` Mel Gorman [this message]
2008-03-27 17:36 ` Andy Whitcroft
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=20080327170058.GB7120@csn.ul.ie \
--to=mel@csn.ul.ie \
--cc=aglitke@us.ibm.com \
--cc=ebmunson@us.ibm.com \
--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