linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Nicolas Boichat <drinkcat@chromium.org>
To: Michal Hocko <mhocko@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	mm-commits@vger.kernel.org,  Yong Wu <yong.wu@mediatek.com>,
	Yingjoe Chen <yingjoe.chen@mediatek.com>,
	 Huaisheng Ye <yehs1@lenovo.com>,
	Matthew Wilcox <willy@infradead.org>,
	 Will Deacon <will.deacon@arm.com>,
	Vlastimil Babka <vbabka@suse.cz>, Tomasz Figa <tfiga@google.com>,
	 stable@vger.kernel.org, Mike Rapoport <rppt@linux.vnet.ibm.com>,
	 Robin Murphy <robin.murphy@arm.com>,
	David Rientjes <rientjes@google.com>,
	 Pekka Enberg <penberg@kernel.org>,
	Mel Gorman <mgorman@techsingularity.net>,
	 Matthias Brugger <matthias.bgg@gmail.com>,
	Joerg Roedel <joro@8bytes.org>,
	 Joonsoo Kim <iamjoonsoo.kim@lge.com>,
	Hsin-Yi Wang <hsinyi@chromium.org>,
	hch@infradead.org,  Christoph Lameter <cl@linux.com>,
	Levin Alexander <Alexander.Levin@microsoft.com>,
	linux-mm@kvack.org
Subject: Re: + mm-add-sys-kernel-slab-cache-cache_dma32.patch added to -mm tree
Date: Wed, 20 Mar 2019 08:17:52 +0800	[thread overview]
Message-ID: <CANMq1KAoya365L9+iGD7Uu34r_9zbbRjSHjB7L_8vi=avTtLnQ@mail.gmail.com> (raw)
In-Reply-To: <20190319191721.GC30433@dhcp22.suse.cz>

On Wed, Mar 20, 2019 at 3:18 AM Michal Hocko <mhocko@kernel.org> wrote:
>
> On Tue 19-03-19 11:37:51, Andrew Morton wrote:
> > From: Nicolas Boichat <drinkcat@chromium.org>
> > Subject: mm: add /sys/kernel/slab/cache/cache_dma32
> >
> > A previous patch in this series adds support for SLAB_CACHE_DMA32 kmem
> > caches.  This adds the corresponding /sys/kernel/slab/cache/cache_dma32
> > entries, and fixes slabinfo tool.
>
> I believe I have asked and didn't get a satisfactory answer before IIRC. Who
> is going to consume this information?

No answer from me, but as a reminder, I added this note on the patch
(https://patchwork.kernel.org/patch/10720491/):
"""
There were different opinions on whether this sysfs entry should
be added, so I'll leave it up to the mm/slub maintainers to decide
whether they want to pick this up, or drop it.
"""

> --
> Michal Hocko
> SUSE Labs


  reply	other threads:[~2019-03-20  0:18 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 [this message]
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

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='CANMq1KAoya365L9+iGD7Uu34r_9zbbRjSHjB7L_8vi=avTtLnQ@mail.gmail.com' \
    --to=drinkcat@chromium.org \
    --cc=Alexander.Levin@microsoft.com \
    --cc=akpm@linux-foundation.org \
    --cc=cl@linux.com \
    --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=mhocko@kernel.org \
    --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