From: David Miller <davem@davemloft.net>
To: nitin.m.gupta@oracle.com
Cc: sowmini.varadhan@oracle.com, aaron.young@oracle.com, bp@suse.de,
sparclinux@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sparc64: Make SLUB the default allocator
Date: Thu, 27 Oct 2016 10:55:39 -0400 (EDT) [thread overview]
Message-ID: <20161027.105539.1624301498966110301.davem@davemloft.net> (raw)
In-Reply-To: <1477520897-47950-1-git-send-email-nitin.m.gupta@oracle.com>
From: Nitin Gupta <nitin.m.gupta@oracle.com>
Date: Wed, 26 Oct 2016 15:27:56 -0700
> SLUB has better debugging support.
>
> Signed-off-by: Nitin Gupta <nitin.m.gupta@oracle.com>
...
> @@ -7,7 +7,9 @@ CONFIG_LOG_BUF_SHIFT=18
> CONFIG_BLK_DEV_INITRD=y
> CONFIG_PERF_EVENTS=y
> # CONFIG_COMPAT_BRK is not set
> -CONFIG_SLAB=y
> +CONFIG_SLUB_DEBUG=y
> +CONFIG_SLUB=y
> +CONFIG_SLUB_CPU_PARTIAL=y
> CONFIG_PROFILING=y
> CONFIG_OPROFILE=m
> CONFIG_KPROBES=y
This patch made me try to find guidance on other architectures as to what
they put in their defconfig files.
And it seems to me that they leave things like this to the user, and the
defconfig only really contains things that really are required by the
architecture or are architecture specific.
So maybe instead of making arbitrary choices for these values which
one set of users want and another set of users do not (I prefer SLAB,
it is faster, and I know what the downsides wrt. NUMA balancing
compared to SLAB are and am willing to accept that), we should do
what other platforms do and not specify things like this at all.
prev parent reply other threads:[~2016-10-27 14:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-26 22:27 Nitin Gupta
2016-10-27 14:55 ` David Miller [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=20161027.105539.1624301498966110301.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=aaron.young@oracle.com \
--cc=bp@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=nitin.m.gupta@oracle.com \
--cc=sowmini.varadhan@oracle.com \
--cc=sparclinux@vger.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
all inboxes | Powered by JetHome®