)]}'
{
  "commit": "eb07a9408e05f67caa671bdf2a509a4d2bd05abf",
  "tree": "e17b801356317ffa1225c2cb19e9580649d528fb",
  "parents": [
    "4d95847381228639844c7197deb8b2211274ef22"
  ],
  "author": {
    "name": "Matt Carlson",
    "email": "mcarlson@broadcom.com",
    "time": "Wed Apr 20 07:57:36 2011 +0000"
  },
  "committer": {
    "name": "David S. Miller",
    "email": "davem@davemloft.net",
    "time": "Thu Apr 21 17:05:55 2011 -0700"
  },
  "message": "tg3: Adjust rx prod ring bd replenish thresholds\n\nThe oldest tg3 devices had large rx producer ring BD caches.  Back then,\nit made sense to make the BD cache replenish threshold only a function\nof the number of rx buffers posted by the driver.  Since then, the BD\ncache sizes have shrunk to 25% of their original size and, in some\ncases, the ring sizes have quadrupled in size.  Under such conditions,\nstatic BD cache replenish thresholds no longer match the hardware\nconstraints.\n\nThis patch attempts to factor in the BD cache size into the bd cache\nreplenish strategy, taking the existing hardware bugs into account.\n\nSigned-off-by: Matt Carlson \u003cmcarlson@broadcom.com\u003e\nReviewed-by: Michael Chan \u003cmchan@broadcom.com\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "58787ea8b7a4062d4707e205051e098a65e419b8",
      "old_mode": 33188,
      "old_path": "drivers/net/tg3.c",
      "new_id": "4aecb0a82e564dfb6762a4582c87a2487d14738f",
      "new_mode": 33188,
      "new_path": "drivers/net/tg3.c"
    },
    {
      "type": "modify",
      "old_id": "db50bfe046e46dc164dfd27d36cc5bef76f353d7",
      "old_mode": 33188,
      "old_path": "drivers/net/tg3.h",
      "new_id": "dd331f8d3f7a53555d0e6ab9da085648dbab71fe",
      "new_mode": 33188,
      "new_path": "drivers/net/tg3.h"
    }
  ]
}