{"push_id":763556384,"size":3,"distinct_size":3,"ref":"refs/heads/cm-12.1","head":"e6f85dfd5850037ea76ed803ba28913fe7df440b","before":"3ec881490b6fd895fb411293fc1d465c20e065c7","commits":[{"sha":"5727d9751605f9331a5a3b2d26bfcff88615f2c4","author":{"email":"596727c8a0ea4db3ba2ceceedccbacd3d7b371b8@suse.cz","name":"Jan Kara"},"message":"ext4: Speedup WB_SYNC_ALL pass called from sync(2)\n\nWhen doing filesystem wide sync, there's no need to force transaction\ncommit (or synchronously write inode buffer) separately for each inode\nbecause ext4_sync_fs() takes care of forcing commit at the end (VFS\ntakes care of flushing buffer cache, respectively). Most of the time\nthis slowness doesn't manifest because previous WB_SYNC_NONE writeback\ndoesn't leave much to write but when there are processes aggressively\ncreating new files and several filesystems to sync, the sync slowness\ncan be noticeable. In the following test script sync(1) takes around 6\nminutes when there are two ext4 filesystems mounted on a standard SATA\ndrive. After this patch sync takes a couple of seconds so we have about\ntwo orders of magnitude improvement.\n\n      function run_writers\n      {\n        for (( i = 0; i < 10; i++ )); do\n          mkdir $1/dir$i\n          for (( j = 0; j < 40000; j++ )); do\n            dd if=/dev/zero of=$1/dir$i/$j bs=4k count=4 &>/dev/null\n          done &\n        done\n      }\n\n      for dir in \"$@\"; do\n        run_writers $dir\n      done\n\n      sleep 40\n      time sync\n\nSigned-off-by: Jan Kara <jack@suse.cz>\nSigned-off-by: \"Theodore Ts'o\" <tytso@mit.edu>\nSigned-off-by: Chet Kener <Cl3Kener@gmail.com>\nSigned-off-by: flar2 <asegaert@gmail.com>\nSigned-off-by: franciscofranco <franciscofranco.1990@gmail.com>\nSigned-off-by: Blechd0se <alex.christ@hotmail.de>\nSigned-off-by: Ryan Andri <ryan.omnia@gmail.com>","distinct":true,"url":"https://api.github.com/repos/ryanaepple/android_kernel_motorola_msm8610/commits/5727d9751605f9331a5a3b2d26bfcff88615f2c4"},{"sha":"9fd789de1f1ecd775be62a54156dd560d4e1eb9e","author":{"email":"fc176ef48eac265831811cf4c9ec8bd8a9651f49@gmail.com","name":"Andre Saddler"},"message":"cpufreq: Add OndemandPLUS Gov\n\nSigned-off-by: houst0nn <houstonn@gmail.com>\nSigned-off-by: Ryan Andri <ryan.omnia@gmail.com>","distinct":true,"url":"https://api.github.com/repos/ryanaepple/android_kernel_motorola_msm8610/commits/9fd789de1f1ecd775be62a54156dd560d4e1eb9e"},{"sha":"e6f85dfd5850037ea76ed803ba28913fe7df440b","author":{"email":"7d26b35203412f18a7dea4f8e1db1a75b1c5b706@semaphore.gr","name":"Stratos Karafotis"},"message":"cpufreq: Break out early when frequency equals target_freq\n\nMany drivers keep frequencies in frequency table in ascending\nor descending order. When governor tries to change to policy->min\nor policy->max respectively then the cpufreq_frequency_table_target\ncould return on first iteration. This will save some iteration cycles.\n\nSo, break out early when a frequency in cpufreq_frequency_table\nequals to target one.\n\nTesting this during kernel compilation using ondemand governor\nwith a frequency table in ascending order, the\ncpufreq_frequency_table_target returned early on the first\niteration at about 30% of times called.\n\nSigned-off-by: Stratos Karafotis <stratosk@semaphore.gr>\nSigned-off-by: Ryan Andri <ryan.omnia@gmail.com>","distinct":true,"url":"https://api.github.com/repos/ryanaepple/android_kernel_motorola_msm8610/commits/e6f85dfd5850037ea76ed803ba28913fe7df440b"}]}