From: Pavel Tatashin <pasha.tatashin@oracle.com>
To: linux-mm@kvack.org, sparclinux@vger.kernel.org
Subject: [PATCH v1 0/3] Zeroing hash tables in allocator
Date: Tue, 28 Feb 2017 09:55:43 -0500 [thread overview]
Message-ID: <1488293746-965735-1-git-send-email-pasha.tatashin@oracle.com> (raw)
On large machines hash tables can be many gigabytes in size and it is
inefficient to zero them in a loop without platform specific optimizations.
Using memset() provides a standard platform optimized way to zero the
memory.
Pavel Tatashin (3):
sparc64: NG4 memset/memcpy 32 bits overflow
mm: Zeroing hash tables in allocator
mm: Updated callers to use HASH_ZERO flag
arch/sparc/lib/NG4memcpy.S | 71 ++++++++++++++++-------------------
arch/sparc/lib/NG4memset.S | 26 ++++++------
fs/dcache.c | 18 ++-------
fs/inode.c | 14 +------
fs/namespace.c | 10 +----
include/linux/bootmem.h | 1 +
kernel/locking/qspinlock_paravirt.h | 3 +-
kernel/pid.c | 7 +--
mm/page_alloc.c | 12 ++++-
9 files changed, 67 insertions(+), 95 deletions(-)
--
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 reply other threads:[~2017-02-28 14:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-28 14:55 Pavel Tatashin [this message]
2017-02-28 14:55 ` [PATCH v1 1/3] sparc64: NG4 memset/memcpy 32 bits overflow Pavel Tatashin
2017-02-28 15:12 ` David Miller
2017-02-28 15:56 ` Pasha Tatashin
2017-02-28 18:59 ` Matthew Wilcox
2017-02-28 19:34 ` Pasha Tatashin
2017-02-28 19:58 ` Matthew Wilcox
2017-02-28 14:55 ` [PATCH v1 2/3] mm: Zeroing hash tables in allocator Pavel Tatashin
2017-02-28 14:55 ` [PATCH v1 3/3] mm: Updated callers to use HASH_ZERO flag Pavel Tatashin
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=1488293746-965735-1-git-send-email-pasha.tatashin@oracle.com \
--to=pasha.tatashin@oracle.com \
--cc=linux-mm@kvack.org \
--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;
as well as URLs for NNTP newsgroup(s).