From: David Rientjes <rientjes@google.com>
To: Bryton Lee <brytonlee01@gmail.com>
Cc: Christoph Lameter <cl@linux.com>,
iamjoonsoo.kim@lge.com, penberg@kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm: move MACRO SLAB_NEVER_MERGE and SLAB_MERGE_SAME to file linux/slab.h
Date: Wed, 21 Jan 2015 14:44:49 -0800 (PST) [thread overview]
Message-ID: <alpine.DEB.2.10.1501211443410.2716@chino.kir.corp.google.com> (raw)
In-Reply-To: <CAC2pzGd_p37Pi53ZEQShMj9BAECPXZCsxQwm=kKLACwmSBB99w@mail.gmail.com>
On Wed, 7 Jan 2015, Bryton Lee wrote:
> thanks for review my patch.
>
> I want to move these macros to linux/slab.h cause I don't want perform
> merge in slab level. for example. ss read /proc/slabinfo to finger out
> how many requests pending in the TCP listern queue. it use slabe name
> "tcp_timewait_sock_ops" search in /proc/slabinfo, although the name is
> obsolete. so I committed other patch to iproute2, replaced
> tcp_timewait_sock_ops by request_sock_TCP, but it still not work, because
> slab request_sock_TCP merge into kmalloc-256.
>
> how could I prevent this merge happen. I'm new to kernel, this is my first
> time submit a kernel patch, thanks!
>
Any bit in SLAB_NEVER_MERGE will cause the allocator to not merge the slab
caches, it's not necessary to all of them be set as it seems you're
implying.
--
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>
prev parent reply other threads:[~2015-01-21 22:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-07 2:01 Bryton Lee
2015-01-07 3:16 ` Christoph Lameter
2015-01-07 7:32 ` Bryton Lee
2015-01-21 22:44 ` David Rientjes [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=alpine.DEB.2.10.1501211443410.2716@chino.kir.corp.google.com \
--to=rientjes@google.com \
--cc=akpm@linux-foundation.org \
--cc=brytonlee01@gmail.com \
--cc=cl@linux.com \
--cc=iamjoonsoo.kim@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=penberg@kernel.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