From: Michal Hocko <mhocko@kernel.org>
To: Mikulas Patocka <mpatocka@redhat.com>
Cc: Mike Snitzer <snitzer@redhat.com>,
jing xia <jing.xia.mail@gmail.com>,
agk@redhat.com, dm-devel@redhat.com,
linux-kernel@vger.kernel.org
Subject: Re: dm bufio: Reduce dm_bufio_lock contention
Date: Tue, 4 Sep 2018 19:45:43 +0200 [thread overview]
Message-ID: <20180904174543.GQ14951@dhcp22.suse.cz> (raw)
In-Reply-To: <alpine.LRH.2.02.1809041328320.8875@file01.intranet.prod.int.rdu2.redhat.com>
On Tue 04-09-18 13:30:44, Mikulas Patocka wrote:
>
>
> On Tue, 4 Sep 2018, Michal Hocko wrote:
>
> > Regarding other other workloads. AFAIR the problem was due to the
> > wait_iff_congested in the direct reclaim. And I've been arguing that
> > special casing __GFP_NORETRY is not a propoer way to handle that case.
> > We have PF_LESS_THROTTLE to handle cases where the caller cannot be
> > really throttled because it is a part of the congestion control. I dunno
> > what happened in that regards since then though.
> > --
> > Michal Hocko
> > SUSE Labs
>
> So, could you take this patch https://patchwork.kernel.org/patch/10505523/
> and commit it to the kernel?
>
> You agreed with that patch, but you didn't commit it.
Because I do not maintain any tree that Linus pulls from. You need to
involve Andrew Morton to get this to the mm tree and then to Linus.
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2018-09-04 17:45 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-12 8:03 [PATCH] " 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-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 14:14 ` Michal Hocko
2018-06-25 14:42 ` Mikulas Patocka
2018-06-25 14:57 ` Michal Hocko
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
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:45 ` Michal Hocko [this message]
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=20180904174543.GQ14951@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®