From: Daniel Jordan <daniel.m.jordan@oracle.com>
To: Tejun Heo <tj@kernel.org>
Cc: Daniel Jordan <daniel.m.jordan@oracle.com>,
Johannes Weiner <hannes@cmpxchg.org>,
Michal Hocko <mhocko@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Roman Gushchin <guro@fb.com>,
linux-mm@kvack.org, cgroups@vger.kernel.org,
linux-kernel@vger.kernel.org, kernel-team@fb.com,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: [PATCH] mm: memcontrol: asynchronous reclaim for memory.high
Date: Thu, 20 Feb 2020 14:55:35 -0500 [thread overview]
Message-ID: <20200220195535.7xblt45akld6eftj@ca-dmjordan1.us.oracle.com> (raw)
In-Reply-To: <20200220184545.GH698990@mtj.thefacebook.com>
On Thu, Feb 20, 2020 at 01:45:45PM -0500, Tejun Heo wrote:
> The setup cost can be lazy optimized but it'd still have to bounce the
> tiny pieces of work to different threads instead of processing them in
> one fell swoop from the same context, which most likely is gonna be
> untenably expensive.
I see, your last mail is clearer now. If it's easy to do, a pointer to where
this happens would help so we're on the same page.
thanks,
Daniel
next prev parent reply other threads:[~2020-02-20 19:55 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-19 18:12 [PATCH] mm: memcontrol: asynchronous reclaim for memory.high Johannes Weiner
2020-02-19 18:37 ` Michal Hocko
2020-02-19 19:16 ` Johannes Weiner
2020-02-19 19:53 ` Michal Hocko
2020-02-19 21:17 ` Johannes Weiner
2020-02-20 9:46 ` Michal Hocko
2020-02-20 14:41 ` Johannes Weiner
2020-02-19 21:41 ` Daniel Jordan
2020-02-19 22:08 ` Johannes Weiner
2020-02-20 15:45 ` Daniel Jordan
2020-02-20 15:56 ` Tejun Heo
2020-02-20 18:23 ` Daniel Jordan
2020-02-20 18:45 ` Tejun Heo
2020-02-20 19:55 ` Daniel Jordan [this message]
2020-02-20 20:54 ` Tejun Heo
2020-02-19 19:17 ` Chris Down
2020-02-19 19:31 ` Andrew Morton
2020-02-19 21:33 ` Johannes Weiner
2020-02-26 20:25 ` Shakeel Butt
2020-02-26 22:26 ` Johannes Weiner
2020-02-26 23:36 ` Shakeel Butt
2020-02-26 23:46 ` Johannes Weiner
2020-02-27 0:12 ` Yang Shi
2020-02-27 2:42 ` Shakeel Butt
2020-02-27 9:58 ` Michal Hocko
2020-02-27 12:50 ` Johannes Weiner
2020-02-26 23:59 ` Yang Shi
2020-02-27 2:36 ` Shakeel Butt
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=20200220195535.7xblt45akld6eftj@ca-dmjordan1.us.oracle.com \
--to=daniel.m.jordan@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=cgroups@vger.kernel.org \
--cc=guro@fb.com \
--cc=hannes@cmpxchg.org \
--cc=kernel-team@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=peterz@infradead.org \
--cc=tj@kernel.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;
as well as URLs for NNTP newsgroup(s).