From: Pekka Enberg <penberg@iki.fi>
To: Alexey Dobriyan <adobriyan@gmail.com>, akpm@linux-foundation.org
Cc: linux-mm@kvack.org, cl@linux.com, penberg@kernel.org,
rientjes@google.com, iamjoonsoo.kim@lge.com,
ecryptfs@vger.kernel.org, linux-xfs@vger.kernel.org,
kasan-dev@googlegroups.com, netdev@vger.kernel.org
Subject: Re: [PATCH 2/2] slab, slub, slob: convert slab_flags_t to 32-bit
Date: Sun, 22 Oct 2017 09:40:27 +0300 [thread overview]
Message-ID: <ed694fcb-c1b8-849f-dc5d-145aa8872ad2@iki.fi> (raw)
In-Reply-To: <20171021100635.GA8287@avx2>
On 21/10/2017 13.06, Alexey Dobriyan wrote:
> struct kmem_cache::flags is "unsigned long" which is unnecessary on
> 64-bit as no flags are defined in the higher bits.
>
> Switch the field to 32-bit and save some space on x86_64 until such
> flags appear:
>
> add/remove: 0/0 grow/shrink: 0/107 up/down: 0/-657 (-657)
> function old new delta
> sysfs_slab_add 720 719 -1
> ...
> check_object 699 676 -23
>
> Signed-off-by: Alexey Dobriyan <adobriyan@gmail.com>
Acked-by: Pekka Enberg <penberg@kernel.org>
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2017-10-22 6:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-21 10:02 [PATCH 1/2] slab, slub, slob: add slab_flags_t Alexey Dobriyan
2017-10-21 10:06 ` [PATCH 2/2] slab, slub, slob: convert slab_flags_t to 32-bit Alexey Dobriyan
2017-10-22 6:40 ` Pekka Enberg [this message]
2017-10-22 6:40 ` [PATCH 1/2] slab, slub, slob: add slab_flags_t Pekka Enberg
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=ed694fcb-c1b8-849f-dc5d-145aa8872ad2@iki.fi \
--to=penberg@iki.fi \
--cc=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=cl@linux.com \
--cc=ecryptfs@vger.kernel.org \
--cc=iamjoonsoo.kim@lge.com \
--cc=kasan-dev@googlegroups.com \
--cc=linux-mm@kvack.org \
--cc=linux-xfs@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=penberg@kernel.org \
--cc=rientjes@google.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;
as well as URLs for NNTP newsgroup(s).