From: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
To: linux-mm@kvack.org
Subject: Re: [RFC PATCH 0/8][Sorted-buddy] mm: Linux VM Infrastructure to support Memory Power Management
Date: Fri, 09 Nov 2012 10:14:23 -0800 [thread overview]
Message-ID: <509D47FF.2030005@linux.intel.com> (raw)
I did like this implementation and think it is valuable.
I am experimenting with one of our HW. This type of partition does help in
saving power. Our calculations shows significant saving of power per DIM with the help
of some HW/BIOS changes. We are only talking about content preserving memory,
so we don't have to be 100% correct.
In my experiments, I tried two methods:
- Similar to approach suggested by Mel Gorman. I have a special sticky
migrate type like CMA.
- Buddy buckets: Buddies are organized into memory region aware buckets.
During allocation it prefers higher order buckets. I made sure that there is
no affect of my change if there are no power saving memory DIMs. The advantage
of this bucket is that I can keep the memory in close proximity for a related
task groups by direct hashing to a bucket. The free list if organized as two
dimensional array with bucket and migrate type for each order.
In both methods, currently reclaim is targeted to be done by a sysfs interface
similar to memory compaction for a node allowing user space to initiate reclaim.
Thanks,
Srinivas Pandruvada
Open Source Technology Center,
Intel Corp.
--
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 reply other threads:[~2012-11-09 18:13 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-09 18:14 Srinivas Pandruvada [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-11-06 19:52 [RFC PATCH 0/8][Sorted-buddy] mm: Linux VM Infrastructure to support Memory Power Management Srivatsa S. Bhat
2012-11-08 18:02 ` Mel Gorman
2012-11-08 19:38 ` Srivatsa S. Bhat
2012-11-09 5:14 ` Vaidyanathan Srinivasan
2012-11-09 9:00 ` Mel Gorman
2012-11-09 14:51 ` Srivatsa S. Bhat
2012-11-09 15:23 ` Srivatsa S. Bhat
2012-11-09 16:13 ` Dave Hansen
2012-11-09 16:34 ` Srivatsa S. Bhat
2012-11-09 16:43 ` Srivatsa S. Bhat
2012-11-09 16:52 ` Srivatsa S. Bhat
2012-11-16 18:32 ` Srivatsa S. Bhat
2012-11-09 15:34 ` Arjan van de Ven
[not found] ` <loom.20121109T172910-394@post.gmane.org>
2012-11-12 16:14 ` Srivatsa S. Bhat
2012-12-04 10:51 ` wujianguo
2012-12-06 6:32 ` Srivatsa S. Bhat
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=509D47FF.2030005@linux.intel.com \
--to=srinivas.pandruvada@linux.intel.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;
as well as URLs for NNTP newsgroup(s).