From: Michal Hocko <mhocko@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Christopher Lameter <cl@linux.com>,
mm-commits@vger.kernel.org, yong.wu@mediatek.com,
yingjoe.chen@mediatek.com, yehs1@lenovo.com, willy@infradead.org,
will.deacon@arm.com, vbabka@suse.cz, tfiga@google.com,
stable@vger.kernel.org, rppt@linux.vnet.ibm.com,
robin.murphy@arm.com, rientjes@google.com, penberg@kernel.org,
mgorman@techsingularity.net, matthias.bgg@gmail.com,
joro@8bytes.org, iamjoonsoo.kim@lge.com, hsinyi@chromium.org,
hch@infradead.org, Alexander.Levin@microsoft.com,
drinkcat@chromium.org, linux-mm@kvack.org
Subject: Re: + mm-add-sys-kernel-slab-cache-cache_dma32.patch added to -mm tree
Date: Fri, 26 Apr 2019 07:47:58 +0200 [thread overview]
Message-ID: <20190426054758.GE12337@dhcp22.suse.cz> (raw)
In-Reply-To: <20190425214615.b46db647b6a6a82db92e4143@linux-foundation.org>
On Thu 25-04-19 21:46:15, Andrew Morton wrote:
> This patch is presently in limbo. Should we just drop it?
There was no strong justification for it except "we alredy do export dma
cache so why not dma32". Christopher was arguing that slabinfo (in tree
tool) is going to use it but that merely prints it without any
additional considerations. So I would just drop it until there is a real
use case (aka somebody is going to use it for something _useful_).
--
Michal Hocko
SUSE Labs
prev parent reply other threads:[~2019-04-26 5:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190319183751.rWqkf%akpm@linux-foundation.org>
2019-03-19 19:18 ` Michal Hocko
2019-03-20 0:17 ` Nicolas Boichat
2019-03-20 7:07 ` Michal Hocko
2019-03-20 0:37 ` Christopher Lameter
2019-03-20 7:05 ` Michal Hocko
2019-04-26 4:46 ` Andrew Morton
2019-04-26 5:47 ` Michal Hocko [this message]
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=20190426054758.GE12337@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=Alexander.Levin@microsoft.com \
--cc=akpm@linux-foundation.org \
--cc=cl@linux.com \
--cc=drinkcat@chromium.org \
--cc=hch@infradead.org \
--cc=hsinyi@chromium.org \
--cc=iamjoonsoo.kim@lge.com \
--cc=joro@8bytes.org \
--cc=linux-mm@kvack.org \
--cc=matthias.bgg@gmail.com \
--cc=mgorman@techsingularity.net \
--cc=mm-commits@vger.kernel.org \
--cc=penberg@kernel.org \
--cc=rientjes@google.com \
--cc=robin.murphy@arm.com \
--cc=rppt@linux.vnet.ibm.com \
--cc=stable@vger.kernel.org \
--cc=tfiga@google.com \
--cc=vbabka@suse.cz \
--cc=will.deacon@arm.com \
--cc=willy@infradead.org \
--cc=yehs1@lenovo.com \
--cc=yingjoe.chen@mediatek.com \
--cc=yong.wu@mediatek.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