From: Matthew Wilcox <willy@infradead.org>
To: "Elliott, Robert (Persistent Memory)" <elliott@hpe.com>
Cc: Cannon Matthews <cannonmatthews@google.com>,
Michal Hocko <mhocko@kernel.org>,
Mike Kravetz <mike.kravetz@oracle.com>,
Andrew Morton <akpm@linux-foundation.org>,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Andres Lagar-Cavilla <andreslc@google.com>,
Salman Qazi <sqazi@google.com>, Paul Turner <pjt@google.com>,
David Matlack <dmatlack@google.com>,
Peter Feiner <pfeiner@google.com>,
Alain Trinh <nullptr@google.com>
Subject: Re: [PATCH v2] RFC: clear 1G pages with streaming stores on x86
Date: Wed, 25 Jul 2018 07:38:50 -0700 [thread overview]
Message-ID: <20180725143850.GA2886@bombadil.infradead.org> (raw)
In-Reply-To: <DF4PR8401MB11806B9D2A7FE04B1F5ECBF8AB540@DF4PR8401MB1180.NAMPRD84.PROD.OUTLOOK.COM>
On Wed, Jul 25, 2018 at 05:02:46AM +0000, Elliott, Robert (Persistent Memory) wrote:
> Even with that, one CPU core won't saturate the memory bus; multiple
> CPU cores (preferably on the same NUMA node as the memory) need to
> share the work.
It's probably OK to not saturate the memory bus; it'd be nice if other
cores were allowed to get work done. If your workload is single-threaded,
you're right, of course, but who has a single-threaded workload these
days?!
next prev parent reply other threads:[~2018-07-25 14:38 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-24 20:46 [PATCH] RFC: clear 1G pages with streaming stores on x86 Cannon Matthews
2018-07-24 20:53 ` Andrew Morton
2018-07-25 2:50 ` Cannon Matthews
2018-07-24 21:09 ` Matthew Wilcox
2018-07-25 2:37 ` [PATCH v2] " Cannon Matthews
2018-07-25 5:02 ` Elliott, Robert (Persistent Memory)
2018-07-25 14:38 ` Matthew Wilcox [this message]
2018-07-25 17:30 ` Cannon Matthews
2018-07-25 18:23 ` Matthew Wilcox
2018-07-25 18:48 ` Cannon Matthews
2018-07-25 12:57 ` Michal Hocko
2018-07-25 17:55 ` Cannon Matthews
2018-07-26 13:19 ` Michal Hocko
2018-07-27 0:05 ` Huang, Ying
2018-07-30 16:29 ` Borislav Petkov
2018-07-31 0:28 ` Cannon Matthews
2018-07-31 0:45 ` Matthew Wilcox
2018-07-25 2:46 ` [PATCH] " Cannon Matthews
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=20180725143850.GA2886@bombadil.infradead.org \
--to=willy@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=andreslc@google.com \
--cc=cannonmatthews@google.com \
--cc=dmatlack@google.com \
--cc=elliott@hpe.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=mike.kravetz@oracle.com \
--cc=nullptr@google.com \
--cc=pfeiner@google.com \
--cc=pjt@google.com \
--cc=sqazi@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).