From: Alexey Dobriyan <adobriyan@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, willy@infradead.org,
vjitta@codeaurora.org, sumit.semwal@linaro.org,
rientjes@google.com, mhocko@kernel.org,
mgorman@techsingularity.net, labbott@redhat.com,
iamjoonsoo.kim@lge.com, hannes@cmpxchg.org, guro@fb.com,
cl@linux.com, vbabka@suse.cz
Subject: Re: + mm-slab-shorten-kmalloc-cache-names-for-large-sizes.patch added to -mm tree
Date: Fri, 7 Sep 2018 22:58:16 +0300 [thread overview]
Message-ID: <20180907195816.GA28375@avx2> (raw)
In-Reply-To: <20180906224849.1JOWr%akpm@linux-foundation.org>
On Thu, Sep 06, 2018 at 03:48:49PM -0700, akpm@linux-foundation.org wrote:
> - {"kmalloc-1024", 1024}, {"kmalloc-2048", 2048},
> - {"kmalloc-4096", 4096}, {"kmalloc-8192", 8192},
> - {"kmalloc-16384", 16384}, {"kmalloc-32768", 32768},
> - {"kmalloc-65536", 65536}, {"kmalloc-131072", 131072},
> - {"kmalloc-262144", 262144}, {"kmalloc-524288", 524288},
> - {"kmalloc-1048576", 1048576}, {"kmalloc-2097152", 2097152},
> - {"kmalloc-4194304", 4194304}, {"kmalloc-8388608", 8388608},
> - {"kmalloc-16777216", 16777216}, {"kmalloc-33554432", 33554432},
> - {"kmalloc-67108864", 67108864}
> + {"kmalloc-1k", 1024}, {"kmalloc-2k", 2048},
> + {"kmalloc-4k", 4096}, {"kmalloc-8k", 8192},
> + {"kmalloc-16k", 16384}, {"kmalloc-32k", 32768},
> + {"kmalloc-64k", 65536}, {"kmalloc-128k", 131072},
> + {"kmalloc-256k", 262144}, {"kmalloc-512k", 524288},
> + {"kmalloc-1M", 1048576}, {"kmalloc-2M", 2097152},
> + {"kmalloc-4M", 4194304}, {"kmalloc-8M", 8388608},
> + {"kmalloc-16M", 16777216}, {"kmalloc-32M", 33554432},
> + {"kmalloc-64M", 67108864}
I'd rather use KB and MB suffixes or at least capital 'K'.
next parent reply other threads:[~2018-09-07 19:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180906224849.1JOWr%akpm@linux-foundation.org>
2018-09-07 19:58 ` Alexey Dobriyan [this message]
2018-09-08 14:03 ` + mm-slab-shorten-kmalloc-cache-names-for-large-sizes.patch added to -mm tree Johannes Weiner
2018-09-08 15:54 ` Matthew Wilcox
2018-09-08 16:10 ` Randy Dunlap
2018-09-08 20:56 ` Matthew Wilcox
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=20180907195816.GA28375@avx2 \
--to=adobriyan@gmail.com \
--cc=cl@linux.com \
--cc=guro@fb.com \
--cc=hannes@cmpxchg.org \
--cc=iamjoonsoo.kim@lge.com \
--cc=labbott@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@techsingularity.net \
--cc=mhocko@kernel.org \
--cc=rientjes@google.com \
--cc=sumit.semwal@linaro.org \
--cc=vbabka@suse.cz \
--cc=vjitta@codeaurora.org \
--cc=willy@infradead.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 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.