diff options
author | André Fabian Silva Delgado <emulatorman@parabola.nu> | 2015-08-04 13:14:50 -0300 |
---|---|---|
committer | André Fabian Silva Delgado <emulatorman@parabola.nu> | 2015-08-04 21:01:26 -0300 |
commit | 0f94121f209de0bdcd48ded525dd37084cac18f2 (patch) | |
tree | 11b952d4acca53913aa1b509f106d6adec664574 /libre/linux-libre/0002-block-loop-avoiding-too-many-pending-per-work-I-O.patch | |
parent | 0a1492bc9ff6ba6967a9d514f2e126b0a105a7bf (diff) | |
download | abslibre-0f94121f209de0bdcd48ded525dd37084cac18f2.tar.gz abslibre-0f94121f209de0bdcd48ded525dd37084cac18f2.tar.bz2 abslibre-0f94121f209de0bdcd48ded525dd37084cac18f2.zip |
linux-libre-4.1.4_gnu-1: updating version
* update Maintainer and Contributor tags
* update pkgbase comments
* enable CONFIG_CROS_EC_CHARDEV and CONFIG_CROS_EC_LPC (FS#45688 -> https://bugs.archlinux.org/task/45688)
Diffstat (limited to 'libre/linux-libre/0002-block-loop-avoiding-too-many-pending-per-work-I-O.patch')
-rw-r--r-- | libre/linux-libre/0002-block-loop-avoiding-too-many-pending-per-work-I-O.patch | 52 |
1 files changed, 0 insertions, 52 deletions
diff --git a/libre/linux-libre/0002-block-loop-avoiding-too-many-pending-per-work-I-O.patch b/libre/linux-libre/0002-block-loop-avoiding-too-many-pending-per-work-I-O.patch deleted file mode 100644 index fcad0c0b9..000000000 --- a/libre/linux-libre/0002-block-loop-avoiding-too-many-pending-per-work-I-O.patch +++ /dev/null @@ -1,52 +0,0 @@ -From 63eb7031005b6f22fc1dab9f0c29435f1b52a96b Mon Sep 17 00:00:00 2001 -From: Ming Lei <ming.lei@canonical.com> -Date: Tue, 5 May 2015 19:49:55 +0800 -Subject: [PATCH 2/2] block: loop: avoiding too many pending per work I/O - -If there are too many pending per work I/O, too many -high priority work thread can be generated so that -system performance can be effected. - -This patch limits the max_active parameter of workqueue as 16. - -This patch fixes Fedora 22 live booting performance -regression when it is booted from squashfs over dm -based on loop, and looks the following reasons are -related with the problem: - -- not like other filesyststems(such as ext4), squashfs -is a bit special, and I observed that increasing I/O jobs -to access file in squashfs only improve I/O performance a -little, but it can make big difference for ext4 - -- nested loop: both squashfs.img and ext3fs.img are mounted -as loop block, and ext3fs.img is inside the squashfs - -- during booting, lots of tasks may run concurrently - -Fixes: b5dd2f6047ca108001328aac0e8588edd15f1778 -Cc: stable@vger.kernel.org (v4.0) -Cc: Justin M. Forbes <jforbes@fedoraproject.org> -Signed-off-by: Ming Lei <ming.lei@canonical.com> -Acked-by: Tejun Heo <tj@kernel.org> -Signed-off-by: Jens Axboe <axboe@fb.com> ---- - drivers/block/loop.c | 2 +- - 1 file changed, 1 insertion(+), 1 deletion(-) - -diff --git a/drivers/block/loop.c b/drivers/block/loop.c -index 9786aa3..cef6fa8 100644 ---- a/drivers/block/loop.c -+++ b/drivers/block/loop.c -@@ -725,7 +725,7 @@ static int loop_set_fd(struct loop_device *lo, fmode_t mode, - goto out_putf; - error = -ENOMEM; - lo->wq = alloc_workqueue("kloopd%d", -- WQ_MEM_RECLAIM | WQ_HIGHPRI | WQ_UNBOUND, 0, -+ WQ_MEM_RECLAIM | WQ_HIGHPRI | WQ_UNBOUND, 16, - lo->lo_number); - if (!lo->wq) - goto out_putf; --- -2.4.5 - |