From: Timofey Titovets <nefelim4ag@gmail.com>
To: linux-mm@kvack.org
Cc: nefelim4ag@gmail.com, akpm@linux-foundation.org
Subject: [PATCH] mempool.c: Replace io_schedule_timeout with io_schedule
Date: Sun, 14 Dec 2014 15:34:46 +0300 [thread overview]
Message-ID: <1418560486-21685-1-git-send-email-nefelim4ag@gmail.com> (raw)
io_schedule_timeout(5*HZ);
Introduced for avoidance dm bug:
http://linux.derkeiler.com/Mailing-Lists/Kernel/2006-08/msg04869.html
According to description must be replaced with io_schedule()
I replace it and recompile kernel, tested it by following script:
---
dev=""
block_dev=zram #loop
if [ "$block_dev" == "loop" ]; then
f1=$RANDOM
f2=${f1}_2
truncate -s 256G ./$f1
truncate -s 256G ./$f2
dev="$(losetup -f --show ./$f1) $(losetup -f --show ./$f2)"
rm ./$f1 ./$f2
else
modprobe zram num_devices=8
# needed ~1g free ram for test
echo 128G > /sys/block/zram7/disksize
echo 128G > /sys/block/zram6/disksize
dev="/dev/zram7 /dev/zram6"
fi
md=/dev/md$[$RANDOM%8]
echo "y\n" | mdadm --create $md --chunk=4 --level=1 --raid-devices=2 $(echo $dev)
[ "$block_dev" == "loop" ] && losetup -d $(echo $dev) &
mkfs.xfs -f $md
mount $md /mnt
cat /dev/zero > /mnt/$RANDOM &
cat /dev/zero > /mnt/$RANDOM &
wait
umount -l /mnt
mdadm --stop $md
if [ "$block_dev" == "zram" ]; then
echo 1 > /sys/block/zram7/reset
echo 1 > /sys/block/zram6/reset
fi
---
i.e. i can't get this error for fast test with zram and slow test with loop devices
Signed-off-by: Timofey Titovets <nefelim4ag@gmail.com>
---
mm/mempool.c | 6 +-----
1 file changed, 1 insertion(+), 5 deletions(-)
diff --git a/mm/mempool.c b/mm/mempool.c
index e209c98..ae230c9 100644
--- a/mm/mempool.c
+++ b/mm/mempool.c
@@ -253,11 +253,7 @@ repeat_alloc:
spin_unlock_irqrestore(&pool->lock, flags);
- /*
- * FIXME: this should be io_schedule(). The timeout is there as a
- * workaround for some DM problems in 2.6.18.
- */
- io_schedule_timeout(5*HZ);
+ io_schedule();
finish_wait(&pool->wait, &wait);
goto repeat_alloc;
--
2.1.3
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next reply other threads:[~2014-12-14 12:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-14 12:34 Timofey Titovets [this message]
2014-12-17 23:06 ` Andrew Morton
2014-12-18 0:37 ` Timofey Titovets
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1418560486-21685-1-git-send-email-nefelim4ag@gmail.com \
--to=nefelim4ag@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-mm@kvack.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox