From: Matthew Wilcox <willy@infradead.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Johannes Weiner <hannes@cmpxchg.org>,
Alexey Dobriyan <adobriyan@gmail.com>,
linux-kernel@vger.kernel.org, vjitta@codeaurora.org,
sumit.semwal@linaro.org, rientjes@google.com, mhocko@kernel.org,
mgorman@techsingularity.net, labbott@redhat.com,
iamjoonsoo.kim@lge.com, 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: Sat, 8 Sep 2018 13:56:13 -0700 [thread overview]
Message-ID: <20180908205613.GA6043@bombadil.infradead.org> (raw)
In-Reply-To: <bd363bd7-9e28-5499-235f-6e6c3c66c829@infradead.org>
On Sat, Sep 08, 2018 at 09:10:46AM -0700, Randy Dunlap wrote:
> On 09/08/2018 08:54 AM, Matthew Wilcox wrote:
> > On Sat, Sep 08, 2018 at 10:03:06AM -0400, Johannes Weiner wrote:
> >> On Fri, Sep 07, 2018 at 10:58:16PM +0300, Alexey Dobriyan wrote:
> >>> I'd rather use KB and MB suffixes or at least capital 'K'.
> >> I like k and M better.
> > k and M work for me too. It we were going to be anal then we should
> > go with the IEC standard of KiB and MiB, but we're trying to make
>
> But ^K and ^M.
>
> Small 'k' .. I don't know what that is.
SI uses 'k' for kilo and 'K' for Kelvin. It's an anomaly because all
the other magnifying prefixes use capital letters, but it's km, not Km;
kg, kV, kJ, kN, kW and kΩ.
prev parent reply other threads:[~2018-09-08 20:56 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 ` + mm-slab-shorten-kmalloc-cache-names-for-large-sizes.patch added to -mm tree Alexey Dobriyan
2018-09-08 14:03 ` Johannes Weiner
2018-09-08 15:54 ` Matthew Wilcox
2018-09-08 16:10 ` Randy Dunlap
2018-09-08 20:56 ` Matthew Wilcox [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=20180908205613.GA6043@bombadil.infradead.org \
--to=willy@infradead.org \
--cc=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=rdunlap@infradead.org \
--cc=rientjes@google.com \
--cc=sumit.semwal@linaro.org \
--cc=vbabka@suse.cz \
--cc=vjitta@codeaurora.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).