)]}'
{
  "commit": "fb003b80daa0dead5b87f4e2e4fb8da68b110ff2",
  "tree": "aa9c3694cb21e61774471e88bd22918c5746c706",
  "parents": [
    "e14808b49f55e0e1135da5e4a154a540dd9f3662"
  ],
  "author": {
    "name": "Mel Gorman",
    "email": "mgorman@suse.de",
    "time": "Thu Nov 15 09:01:14 2012 +0000"
  },
  "committer": {
    "name": "Mel Gorman",
    "email": "mgorman@suse.de",
    "time": "Tue Dec 11 14:42:51 2012 +0000"
  },
  "message": "sched: numa: Slowly increase the scanning period as NUMA faults are handled\n\nCurrently the rate of scanning for an address space is controlled\nby the individual tasks. The next scan is simply determined by\n2*p-\u003enuma_scan_period.\n\nThe 2*p-\u003enuma_scan_period is arbitrary and never changes. At this point\nthere is still no proper policy that decides if a task or process is\nproperly placed. It just scans and assumes the next NUMA fault will\nplace it properly. As it is assumed that pages will get properly placed\nover time, increase the scan window each time a fault is incurred. This\nis a big assumption as noted in the comments.\n\nIt should be noted that changing to p-\u003enuma_scan_period will increase\nsystem CPU usage because now the scanning rate has effectively doubled.\nIf that is a problem then the min_rate should be made 200ms instead of\nrestoring the 2* logic.\n\nSigned-off-by: Mel Gorman \u003cmgorman@suse.de\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "37e895a941ab34fcf029761e9b2227d4382837d5",
      "old_mode": 33188,
      "old_path": "kernel/sched/fair.c",
      "new_id": "dd18087fd36938a6883ce52bf15c717d07a0ec74",
      "new_mode": 33188,
      "new_path": "kernel/sched/fair.c"
    }
  ]
}