From: Balbir Singh <bsingharora@gmail.com>
To: Laurent Dufour <ldufour@linux.vnet.ibm.com>,
paulmck@linux.vnet.ibm.com, peterz@infradead.org,
akpm@linux-foundation.org, kirill@shutemov.name,
ak@linux.intel.com, mhocko@kernel.org, dave@stgolabs.net,
jack@suse.cz, Matthew Wilcox <willy@infradead.org>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
haren@linux.vnet.ibm.com, khandual@linux.vnet.ibm.com,
npiggin@gmail.com, Tim Chen <tim.c.chen@linux.intel.com>
Subject: Re: [RFC v5 00/11] Speculative page faults
Date: Fri, 07 Jul 2017 11:54:07 +1000 [thread overview]
Message-ID: <1499392447.23251.1.camel@gmail.com> (raw)
In-Reply-To: <b9988c09-265a-022a-266d-e51250fe3f2c@linux.vnet.ibm.com>
On Mon, 2017-07-03 at 19:32 +0200, Laurent Dufour wrote:
> The test is counting the number of records per second it can manage, the
> higher is the best. I run it like this 'ebizzy -mTRp'. To get consistent
> result I repeat the test 100 times and measure the average result, mean
> deviation and max. I run the test on top of 4.12 on 2 nodes, one with 80
> CPUs, and the other one with 1024 CPUs:
>
> * 80 CPUs Power 8 node:
> Records/s 4.12 4.12-SPF
> Average 38941,62 64235,82
> Mean deviation 620,93 1718,95
> Max 41988 69623
>
> * 1024 CPUs Power 8 node:
> Records/s 4.12 4.12-SPF
> Average 39516,64 80689,27
> Mean deviation 1387,66 1319,98
> Max 43281 90441
>
This seems like a very interesting result
Balbir Singh.
--
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:[~2017-07-07 1:55 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-16 17:52 [RFC v5 00/11] Speculative page faults Laurent Dufour
2017-06-16 17:52 ` [RFC v5 01/11] mm: Dont assume page-table invariance during faults Laurent Dufour
2017-07-07 7:07 ` Balbir Singh
2017-07-10 17:48 ` Laurent Dufour
2017-07-11 4:26 ` Balbir Singh
2017-08-08 10:04 ` Anshuman Khandual
2017-08-08 9:45 ` Anshuman Khandual
2017-08-08 12:11 ` Laurent Dufour
2017-06-16 17:52 ` [RFC v5 02/11] mm: Prepare for FAULT_FLAG_SPECULATIVE Laurent Dufour
2017-08-08 10:24 ` Anshuman Khandual
2017-08-08 10:42 ` Peter Zijlstra
2017-06-16 17:52 ` [RFC v5 03/11] mm: Introduce pte_spinlock " Laurent Dufour
2017-08-08 10:35 ` Anshuman Khandual
2017-08-08 12:16 ` Laurent Dufour
2017-06-16 17:52 ` [RFC v5 04/11] mm: VMA sequence count Laurent Dufour
2017-08-08 10:59 ` Anshuman Khandual
2017-08-08 11:04 ` Peter Zijlstra
2017-06-16 17:52 ` [RFC v5 05/11] mm: fix lock dependency against mapping->i_mmap_rwsem Laurent Dufour
2017-08-08 11:17 ` Anshuman Khandual
2017-08-08 12:20 ` Laurent Dufour
2017-08-08 12:49 ` Jan Kara
2017-08-08 13:08 ` Laurent Dufour
2017-08-08 13:15 ` Peter Zijlstra
2017-08-08 13:34 ` Laurent Dufour
2017-06-16 17:52 ` [RFC v5 06/11] mm: Protect VMA modifications using VMA sequence count Laurent Dufour
2017-06-16 17:52 ` [RFC v5 07/11] mm: RCU free VMAs Laurent Dufour
2017-06-16 17:52 ` [RFC v5 08/11] mm: Provide speculative fault infrastructure Laurent Dufour
2017-06-16 17:52 ` [RFC v5 09/11] mm: Try spin lock in speculative path Laurent Dufour
2017-07-05 18:50 ` Peter Zijlstra
2017-07-06 13:46 ` Laurent Dufour
2017-07-06 14:48 ` Peter Zijlstra
2017-07-06 15:29 ` Laurent Dufour
2017-07-06 16:13 ` Peter Zijlstra
2017-06-16 17:52 ` [RFC v5 10/11] x86/mm: Add speculative pagefault handling Laurent Dufour
2017-06-16 17:52 ` [RFC v5 11/11] powerpc/mm: Add speculative page fault Laurent Dufour
2017-07-03 17:32 ` [RFC v5 00/11] Speculative page faults Laurent Dufour
2017-07-07 1:54 ` Balbir Singh [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=1499392447.23251.1.camel@gmail.com \
--to=bsingharora@gmail.com \
--cc=ak@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=dave@stgolabs.net \
--cc=haren@linux.vnet.ibm.com \
--cc=jack@suse.cz \
--cc=khandual@linux.vnet.ibm.com \
--cc=kirill@shutemov.name \
--cc=ldufour@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=npiggin@gmail.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=tim.c.chen@linux.intel.com \
--cc=willy@infradead.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).