)]}'
{
  "commit": "c5c5622e7e0b9851286adf5c225e03aa98f3cdac",
  "tree": "93d5da9e9d960a47b57a1fe661c3be6a34aa4be2",
  "parents": [
    "5e0713e24adb94767c20643341e60b29fe5eea35"
  ],
  "author": {
    "name": "Josef Bacik",
    "email": "josef@toxicpanda.com",
    "time": "Mon Sep 10 10:22:03 2018 -0700"
  },
  "committer": {
    "name": "Josef Bacik",
    "email": "josef@toxicpanda.com",
    "time": "Fri Sep 28 10:37:06 2018 -0700"
  },
  "message": "blk-iolatency: keep track of previous windows stats\n\nWe apply a smoothing to the scale changes in order to keep sawtoothy\nbehavior from occurring.  However our window for checking if we\u0027ve\nmissed our target can sometimes be lower than the smoothing interval\n(500ms), especially on faster drives like ssd\u0027s.  In order to deal with\nthis keep track of the running tally of the previous intervals that we\nthrew away because we had already done a scale event recently.\n\nThis is needed for the ssd case as these low latency drives will have\nbursts of latency, and if it happens to be ok for the window that\ndirectly follows the opening of the scale window we could unthrottle\nwhen previous windows we were missing our target.\n\nSigned-off-by: Josef Bacik \u003cjosef@toxicpanda.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "fd246805b0be0a2ea4499597ff23e5c4cbc6d0cd",
      "old_mode": 33188,
      "old_path": "block/blk-iolatency.c",
      "new_id": "35c48d7b8f78e1c9594533d113ea72aafa80ff14",
      "new_mode": 33188,
      "new_path": "block/blk-iolatency.c"
    }
  ]
}