[lkml]   [2010]   [Jan]   [20]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH 5/7] Add /proc trigger for memory compaction
On Wed, 20 Jan 2010, Mel Gorman wrote:

> > With Lee's work on mempolicy-constrained hugepage allocations, there is a
> > use-case for this explicit trigger to be exported via sysfs in the
> > longterm:
> True, although the per-node structures are only available on NUMA making
> it necessary to have two interfaces. The per-node one is handy enough
> because it would be just
> /sys/devices/system/node/nodeX/compact_node
> When written to, this node is compacted by the writing process
> But there does not appear to be a "good" way of having a non-NUMA
> interface. /sys/devices/system/node does not exist .... Does anyone
> remember why !NUMA does not have a /sys/devices/system/node/node0? Is
> there a good reason or was there just no point?

There doesn't seem to be a usecase for a fake node0 sysfs entry since it
would be a duplication of procfs.

I think it would be best to create a global /proc/sys/vm/compact trigger
that would walk all "compactable" zones system-wide and then a per-node
/sys/devices/system/node/nodeX/compact trigger for that particular node,
both with permissions 0200.

It would be helpful to be able to determine what is "compactable" at the
same time by adding both global and per-node "compact_order" tunables that
would default to HUGETLB_PAGE_ORDER. Then, the corresponding "compact"
trigger would only do work if fill_contig_page_info() shows
!free_blocks_suitable for either all zones (global trigger) or each zone
in the node's zonelist (per-node trigger).

 \ /
  Last update: 2010-01-20 21:51    [W:0.130 / U:23.184 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site