[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <572EACAC.9010405@hpe.com>
Date: Sat, 7 May 2016 23:04:12 -0400
From: Waiman Long <waiman.long@....com>
To: Ingo Molnar <mingo@...nel.org>
CC: Peter Zijlstra <peterz@...radead.org>,
Ingo Molnar <mingo@...hat.com>, <linux-kernel@...r.kernel.org>,
Davidlohr Bueso <dave@...olabs.net>,
Jason Low <jason.low2@...com>,
Dave Chinner <david@...morbit.com>,
Scott J Norton <scott.norton@....com>,
Douglas Hatch <doug.hatch@....com>
Subject: Re: [PATCH v2] locking/rwsem: Add reader-owned state to the owner
field
On 05/07/2016 12:56 AM, Ingo Molnar wrote:
> * Waiman Long<Waiman.Long@....com> wrote:
>
>> On a 4-socket Haswell machine running on a 4.6-rc1 based kernel, the
>> fio test with multithreaded randrw and randwrite tests on the same
>> file on a XFS partition on top of a NVDIMM were run, the aggregated
>> bandwidths before and after the patch were as follows:
>>
>> Test BW before patch BW after patch % change
>> ---- --------------- -------------- --------
>> randrw 988 MB/s 1192 MB/s +21%
>> randwrite 1513 MB/s 1623 MB/s +7.3%
> What testcase/suite is this? I'd like to run this on other machines as well.
>
> Thanks,
>
> Ingo
I just used fio on a nvdimm based xfs filesystem. It is essentially like
a ramfs filesystem in term of performance. Attached were config files
that I used.
Cheers,
Longman
View attachment "rw.fio" of type "text/plain" (420 bytes)
View attachment "wo.fio" of type "text/plain" (427 bytes)
Powered by blists - more mailing lists