From: Michal Hocko <mhocko@kernel.org>
To: jing xia <jing.xia.mail@gmail.com>
Cc: Mikulas Patocka <mpatocka@redhat.com>,
Mike Snitzer <snitzer@redhat.com>,
agk@redhat.com, dm-devel@redhat.com,
linux-kernel@vger.kernel.org
Subject: Re: dm bufio: Reduce dm_bufio_lock contention
Date: Wed, 1 Aug 2018 09:03:12 +0200 [thread overview]
Message-ID: <20180801070312.GC16767@dhcp22.suse.cz> (raw)
In-Reply-To: <CAN=25QNrENVFbb9UAAAJJqKsEeMY+qNs5cQA4EGwgB2dMYTZug@mail.gmail.com>
On Wed 01-08-18 10:48:00, jing xia wrote:
> We reproduced this issue again and found out the root cause.
> dm_bufio_prefetch() with dm_bufio_lock enters the direct reclaim and
> takes a long time to do the soft_limit_reclaim, because of the huge
> number of memory excess of the memcg.
> Then, all the task who do shrink_slab() wait for dm_bufio_lock.
>
> Any suggestions for this?Thanks.
Do not use soft limit?
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2018-08-01 7:03 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-12 8:03 [PATCH] dm bufio: Reduce dm_bufio_lock contention Jing Xia
2018-06-12 21:20 ` Mike Snitzer
2018-06-13 14:02 ` Mikulas Patocka
2018-06-14 7:18 ` jing xia
2018-06-14 7:31 ` Michal Hocko
2018-06-14 18:34 ` Mikulas Patocka
2018-06-15 7:32 ` Michal Hocko
2018-06-15 11:35 ` Mikulas Patocka
2018-06-15 11:55 ` Michal Hocko
2018-06-15 12:47 ` Mikulas Patocka
2018-06-15 13:09 ` Michal Hocko
2018-06-18 22:11 ` Mikulas Patocka
2018-06-18 22:11 ` Mikulas Patocka
2018-06-19 10:43 ` Michal Hocko
2018-06-22 1:17 ` Mikulas Patocka
2018-06-22 9:01 ` Michal Hocko
2018-06-22 9:09 ` Michal Hocko
2018-06-22 12:52 ` Mikulas Patocka
2018-06-22 13:05 ` Michal Hocko
2018-06-22 18:57 ` Mikulas Patocka
2018-06-25 9:09 ` Michal Hocko
2018-06-25 13:53 ` Mikulas Patocka
2018-06-25 13:53 ` Mikulas Patocka
2018-06-25 14:14 ` Michal Hocko
2018-06-25 14:42 ` Mikulas Patocka
2018-06-25 14:42 ` Mikulas Patocka
2018-06-25 14:57 ` Michal Hocko
2018-06-29 2:43 ` Mikulas Patocka
2018-06-29 2:43 ` Mikulas Patocka
2018-06-29 8:29 ` Michal Hocko
2018-06-22 12:44 ` Mikulas Patocka
2018-06-22 13:10 ` Michal Hocko
2018-06-22 18:46 ` Mikulas Patocka
2018-08-01 2:48 ` jing xia
2018-08-01 7:03 ` Michal Hocko [this message]
2018-09-03 22:23 ` Mikulas Patocka
2018-09-04 7:08 ` Michal Hocko
2018-09-04 15:18 ` Mike Snitzer
2018-09-04 16:08 ` Michal Hocko
2018-09-04 17:30 ` Mikulas Patocka
2018-09-04 17:30 ` Mikulas Patocka
2018-09-04 17:45 ` Michal Hocko
2018-09-04 17:45 ` Michal Hocko
2018-06-14 7:16 ` jing xia
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=20180801070312.GC16767@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=agk@redhat.com \
--cc=dm-devel@redhat.com \
--cc=jing.xia.mail@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mpatocka@redhat.com \
--cc=snitzer@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.