)]}'
{
  "commit": "20acaa18d0c002fec180956f87adeb3f11f635a6",
  "tree": "2cd2f21530150e8248a0217e380d58d42e79d89d",
  "parents": [
    "e4b69aa2a1bcee21f8d5e089b8682dd8aaace5eb"
  ],
  "author": {
    "name": "Suparna Bhattacharya",
    "email": "suparna@in.ibm.com",
    "time": "Sat Sep 16 12:15:58 2006 -0700"
  },
  "committer": {
    "name": "Linus Torvalds",
    "email": "torvalds@g5.osdl.org",
    "time": "Sat Sep 16 12:54:32 2006 -0700"
  },
  "message": "[PATCH] ext3 sequential read regression fix\n\next3-get-blocks support caused ~20% degrade in Sequential read\nperformance (tiobench). Problem is with marking the buffer boundary\nso IO can be submitted right away. Here is the patch to fix it.\n\n  2.6.18-rc6:\n  -----------\n  # ./iotest\n  1048576+0 records in\n  1048576+0 records out\n  4294967296 bytes (4.3 GB) copied, 75.2726 seconds, 57.1 MB/s\n\n  real    1m15.285s\n  user    0m0.276s\n  sys     0m3.884s\n\n  2.6.18-rc6 + fix:\n  -----------------\n  [root@elm3a241 ~]# ./iotest\n  1048576+0 records in\n  1048576+0 records out\n  4294967296 bytes (4.3 GB) copied, 62.9356 seconds, 68.2 MB/s\n\nThe boundary block check in ext3_get_blocks_handle needs to be adjusted\nagainst the count of blocks mapped in this call, now that it can map\nmore than one block.\n\nSigned-off-by: Suparna Bhattacharya \u003csuparna@in.ibm.com\u003e\nTested-by: Badari Pulavarty \u003cpbadari@us.ibm.com\u003e\nSigned-off-by: Andrew Morton \u003cakpm@osdl.org\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@osdl.org\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "0f0b1eadb98dd6dd5f74faa98d8b04012fd0a9f6",
      "old_mode": 33188,
      "old_path": "fs/ext3/inode.c",
      "new_id": "84be02e93652bd8e5548d8f07ad6e57c5947c817",
      "new_mode": 33188,
      "new_path": "fs/ext3/inode.c"
    }
  ]
}
