{"push_id":3106895098,"size":2,"distinct_size":2,"ref":"refs/heads/oreo-mr1","head":"2fd414bb41131221e7788a2b2b21f92b862fb8cd","before":"aba544a32ed3deb87e33b33f1deda0aa330e4abb","commits":[{"sha":"19d5978209bd9bef897523098dcd13f9d07e5cd4","author":{"name":"Naresh Malladi","email":"5b88851218a5b3c58e6db9c7f07eb0d1478814bc@codeaurora.org"},"message":"drivers: cpu-idle: lpm-levels: Use cpuidle disable sysfs\n\nUse cpuidle generic disable sysfs interface. So that LPM\nmodes can be controlled through this interface also.\n\necho {1,0} > /sys/devices/system/cpu/cpuN/cpuidle/stateN/disable\n\nIf LPM modes are disabled via any of the interface, they will\nnot be exercised\n\nChange-Id: I2fcfd2ce8a23e539b3d732f3fa85813876dc3f3c\nSigned-off-by: Naresh Malladi <namall@codeaurora.org>\nSigned-off-by: khusika <khusikadhamar@gmail.com>","distinct":true,"url":"https://api.github.com/repos/rezaadi0105/android_kernel_xiaomi_msm8953/commits/19d5978209bd9bef897523098dcd13f9d07e5cd4"},{"sha":"2fd414bb41131221e7788a2b2b21f92b862fb8cd","author":{"name":"NeilBrown","email":"1c00aa603bb92d594c03cff60ecf8e63b2a5bcb1@suse.de"},"message":"workqueue: allow rescuer thread to do more work.\n\nWhen there is serious memory pressure, all workers in a pool could be\nblocked, and a new thread cannot be created because it requires memory\nallocation.\n\nIn this situation a WQ_MEM_RECLAIM workqueue will wake up the\nrescuer thread to do some work.\n\nThe rescuer will only handle requests that are already on ->worklist.\nIf max_requests is 1, that means it will handle a single request.\n\nThe rescuer will be woken again in 100ms to handle another max_requests\nrequests.\n\nI've seen a machine (running a 3.0 based \"enterprise\" kernel) with\nthousands of requests queued for xfslogd, which has a max_requests of\n1, and is needed for retiring all 'xfs' write requests.  When one of\nthe worker pools gets into this state, it progresses extremely slowly\nand possibly never recovers (only waited an hour or two).\n\nWith this patch we leave a pool_workqueue on mayday list\nuntil it is clearly no longer in need of assistance.  This allows\nall requests to be handled in a timely fashion.\n\nWe keep each pool_workqueue on the mayday list until\nneed_to_create_worker() is false, and no work for this workqueue is\nfound in the pool.\n\nI have tested this in combination with a (hackish) patch which forces\nall work items to be handled by the rescuer thread.  In that context\nit significantly improves performance.  A similar patch for a 3.0\nkernel significantly improved performance on a heavy work load.\n\nThanks to Jan Kara for some design ideas, and to Dongsu Park for\nsome comments and testing.\n\ntj: Inverted the lock order between wq_mayday_lock and pool->lock with\n    a preceding patch and simplified this patch.  Added comment and\n    updated changelog accordingly.  Dongsu spotted missing get_pwq()\n    in the simplified code.\n\nCc: Dongsu Park <dongsu.park@profitbricks.com>\nCc: Jan Kara <jack@suse.cz>\nCc: Lai Jiangshan <laijs@cn.fujitsu.com>\nSigned-off-by: NeilBrown <neilb@suse.de>\nSigned-off-by: Tejun Heo <tj@kernel.org>\nSigned-off-by: Pranav Vashi <neobuddy89@gmail.com>\nSigned-off-by: khusika <khusikadhamar@gmail.com>","distinct":true,"url":"https://api.github.com/repos/rezaadi0105/android_kernel_xiaomi_msm8953/commits/2fd414bb41131221e7788a2b2b21f92b862fb8cd"}]}
{"actor":{"display_login":"rezaadi0105"}}