)]}'
{
  "commit": "8f71465c19ffefbfd0da3c1f5dc172b4bce05e93",
  "tree": "c27bb25b91b148e5977ea29132dc98ccea89f725",
  "parents": [
    "156d17905e783d057061b3b56a9b3befec064e47"
  ],
  "author": {
    "name": "Jeff Layton",
    "email": "jlayton@redhat.com",
    "time": "Tue May 01 17:41:49 2012 -0400"
  },
  "committer": {
    "name": "Steve French",
    "email": "sfrench@us.ibm.com",
    "time": "Tue May 01 22:27:54 2012 -0500"
  },
  "message": "cifs: don\u0027t cap ra_pages at the same level as default_backing_dev_info\n\nWhile testing, I\u0027ve found that even when we are able to negotiate a\nmuch larger rsize with the server, on-the-wire reads often end up being\ncapped at 128k because of ra_pages being capped at that level.\n\nLifting this restriction gave almost a twofold increase in sequential\nread performance on my craptactular KVM test rig with a 1M rsize.\n\nI think this is safe since the actual ra_pages that the VM requests\nis run through max_sane_readahead() prior to submitting the I/O. Under\nmemory pressure we should end up with large readahead requests being\nsuppressed anyway.\n\nSigned-off-by: Jeff Layton \u003cjlayton@redhat.com\u003e\nSigned-off-by: Steve French \u003csfrench@us.ibm.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "f4d381e331ce442a6181613c6327b7e016cacd72",
      "old_mode": 33188,
      "old_path": "fs/cifs/connect.c",
      "new_id": "6ce888b04dc887c09a7fb565d769e18bc07f53df",
      "new_mode": 33188,
      "new_path": "fs/cifs/connect.c"
    }
  ]
}