From: "George Spelvin" <linux@horizon.com>
To: dave@sr71.net
Cc: linux@horizon.com, linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH 3/3] Kconfig: organize memory-related config options
Date: 2 Feb 2014 04:50:17 -0500 [thread overview]
Message-ID: <20140202095017.32007.qmail@science.horizon.com> (raw)
> +config MMAP_ALLOW_UNINITIALIZED
> + bool "Allow mmapped anonymous memory to be uninitialized"
> + depends on EXPERT && !MMU
> + default n
> + help
> + Normally, and according to the Linux spec, anonymous memory obtained
> + from mmap() has it's contents cleared before it is passed to
^^^^
"its", please.
If you really want to make me happy, clarify the CONFIG_SLOB help to
explain what a large system is. More than 4 CPUs? More tha 32 GB
of RAM? E-ATX motherboard?
--
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>
WARNING: multiple messages have this Message-ID (diff)
From: "George Spelvin" <linux@horizon.com>
To: dave@sr71.net
Cc: linux@horizon.com, linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH 3/3] Kconfig: organize memory-related config options
Date: 2 Feb 2014 04:50:17 -0500 [thread overview]
Message-ID: <20140202095017.32007.qmail@science.horizon.com> (raw)
> +config MMAP_ALLOW_UNINITIALIZED
> + bool "Allow mmapped anonymous memory to be uninitialized"
> + depends on EXPERT && !MMU
> + default n
> + help
> + Normally, and according to the Linux spec, anonymous memory obtained
> + from mmap() has it's contents cleared before it is passed to
^^^^
"its", please.
If you really want to make me happy, clarify the CONFIG_SLOB help to
explain what a large system is. More than 4 CPUs? More tha 32 GB
of RAM? E-ATX motherboard?
next reply other threads:[~2014-02-02 9:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-02 9:50 George Spelvin [this message]
2014-02-02 9:50 ` [PATCH 3/3] Kconfig: organize memory-related config options George Spelvin
-- strict thread matches above, loose matches on Subject: below --
2014-01-31 17:24 [PATCH 0/3] General Kconfig reorganization Dave Hansen
2014-01-31 17:24 ` [PATCH 3/3] Kconfig: organize memory-related config options Dave Hansen
2014-01-31 17:24 ` Dave Hansen
2014-02-04 16:02 ` Dave Hansen
2014-02-04 16:02 ` Dave Hansen
2014-02-04 16:14 ` Michal Hocko
2014-02-04 16:14 ` Michal Hocko
2014-01-02 20:20 [PATCH 1/3] kconfig: consolidate arch-specific seccomp options Dave Hansen
2014-01-02 20:20 ` [PATCH 3/3] Kconfig: organize memory-related config options Dave Hansen
2014-01-02 20:20 ` Dave Hansen
2014-02-05 14:28 ` Michal Hocko
2014-02-05 14:28 ` Michal Hocko
2014-02-05 16:27 ` Dave Hansen
2014-02-05 16:27 ` Dave Hansen
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=20140202095017.32007.qmail@science.horizon.com \
--to=linux@horizon.com \
--cc=dave@sr71.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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.