From: "Török Edwin" <edwintorok@gmail.com>
To: Ying Han <yinghan@google.com>
Cc: Nick Piggin <npiggin@suse.de>, Mike Waychison <mikew@google.com>,
Ingo Molnar <mingo@elte.hu>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
akpm <akpm@linux-foundation.org>,
David Rientjes <rientjes@google.com>,
Rohit Seth <rohitseth@google.com>,
Hugh Dickins <hugh@veritas.com>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [RFC v1][PATCH]page_fault retry with NOPAGE_RETRY
Date: Fri, 05 Dec 2008 08:50:04 +0200 [thread overview]
Message-ID: <4938CF1C.9020503@gmail.com> (raw)
In-Reply-To: <604427e00812041427j7f1c8118p48b1b5b577143703@mail.gmail.com>
On 2008-12-05 00:27, Ying Han wrote:
> I am trying your test program(scalability) in house, but somehow i got
> different result as you saw. i created 8 files each with 1G size on
> separate drives( to avoid the latency disturbing of disk seek). I got
> this number without applying the batch based on 2.6.26. May i ask how
> to reproduce the mmap issue you mentioned?
>
Hi,
Try using more files, and of smaller size. I was using /usr/bin, which
has 3632 files, and 571M total.
I am using XFS filesystem: /dev/mapper/vg--all-lv--usr on /usr type xfs
(rw,noatime,logbsize=262144,logbufs=8,logdev=/dev/sdg6,inode64)
> 8 CPU
> read_worker
> 1 threads Real time: 101.058262 s (since task start)
> 2 threads Real time: 50.670456 s (since task start)
> 4 threads Real time: 25.904657 s (since task start)
> 8 threads Real time: 20.090677 s (since task start)
> --------------------------------------------------------------------------------
> mmap_worker
> 1 threads Real time: 101.340662 s (since task start)
> 2 threads Real time: 51.484646 s (since task start)
> 4 threads Real time: 28.414534 s (since task start)
> 8 threads Real time: 21.785818 s (since task start)
>
Try 16 threads, so that there is more contention on the read side as well.
Best regards,
--Edwin
WARNING: multiple messages have this Message-ID (diff)
From: "Török Edwin" <edwintorok@gmail.com>
To: Ying Han <yinghan@google.com>
Cc: Nick Piggin <npiggin@suse.de>, Mike Waychison <mikew@google.com>,
Ingo Molnar <mingo@elte.hu>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
akpm <akpm@linux-foundation.org>,
David Rientjes <rientjes@google.com>,
Rohit Seth <rohitseth@google.com>,
Hugh Dickins <hugh@veritas.com>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [RFC v1][PATCH]page_fault retry with NOPAGE_RETRY
Date: Fri, 05 Dec 2008 08:50:04 +0200 [thread overview]
Message-ID: <4938CF1C.9020503@gmail.com> (raw)
In-Reply-To: <604427e00812041427j7f1c8118p48b1b5b577143703@mail.gmail.com>
On 2008-12-05 00:27, Ying Han wrote:
> I am trying your test program(scalability) in house, but somehow i got
> different result as you saw. i created 8 files each with 1G size on
> separate drives( to avoid the latency disturbing of disk seek). I got
> this number without applying the batch based on 2.6.26. May i ask how
> to reproduce the mmap issue you mentioned?
>
Hi,
Try using more files, and of smaller size. I was using /usr/bin, which
has 3632 files, and 571M total.
I am using XFS filesystem: /dev/mapper/vg--all-lv--usr on /usr type xfs
(rw,noatime,logbsize=262144,logbufs=8,logdev=/dev/sdg6,inode64)
> 8 CPU
> read_worker
> 1 threads Real time: 101.058262 s (since task start)
> 2 threads Real time: 50.670456 s (since task start)
> 4 threads Real time: 25.904657 s (since task start)
> 8 threads Real time: 20.090677 s (since task start)
> --------------------------------------------------------------------------------
> mmap_worker
> 1 threads Real time: 101.340662 s (since task start)
> 2 threads Real time: 51.484646 s (since task start)
> 4 threads Real time: 28.414534 s (since task start)
> 8 threads Real time: 21.785818 s (since task start)
>
Try 16 threads, so that there is more contention on the read side as well.
Best regards,
--Edwin
--
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 prev parent reply other threads:[~2008-12-05 6:50 UTC|newest]
Thread overview: 82+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-22 6:47 [RFC v1][PATCH]page_fault retry with NOPAGE_RETRY Ying Han
2008-11-22 6:47 ` Ying Han
2008-11-22 7:15 ` Andrew Morton
2008-11-22 7:15 ` Andrew Morton
2008-11-23 9:18 ` Ingo Molnar
2008-11-23 9:18 ` Ingo Molnar
2008-11-23 18:24 ` Andrew Morton
2008-11-23 18:24 ` Andrew Morton
2008-11-25 18:42 ` Ying Han
2008-11-25 18:42 ` Ying Han
2008-11-26 12:32 ` Nick Piggin
2008-11-26 12:32 ` Nick Piggin
2008-11-26 19:57 ` Mike Waychison
2008-11-26 19:57 ` Mike Waychison
2008-11-27 8:55 ` Nick Piggin
2008-11-27 8:55 ` Nick Piggin
2008-11-27 9:28 ` Mike Waychison
2008-11-27 9:28 ` Mike Waychison
2008-11-27 10:00 ` Peter Zijlstra
2008-11-27 10:00 ` Peter Zijlstra
2008-11-27 10:14 ` Nick Piggin
2008-11-27 10:14 ` Nick Piggin
2008-11-27 19:22 ` Mike Waychison
2008-11-27 19:22 ` Mike Waychison
2008-11-28 9:41 ` Nick Piggin
2008-11-28 9:41 ` Nick Piggin
2008-11-28 22:46 ` Mike Waychison
2008-11-28 22:46 ` Mike Waychison
2008-11-27 11:08 ` KOSAKI Motohiro
2008-11-27 11:08 ` KOSAKI Motohiro
2008-11-27 19:10 ` Mike Waychison
2008-11-27 19:10 ` Mike Waychison
2008-11-27 11:39 ` Török Edwin
2008-11-27 11:39 ` Török Edwin
2008-11-27 12:03 ` Nick Piggin
2008-11-27 12:03 ` Nick Piggin
2008-11-27 12:21 ` Török Edwin
2008-11-27 12:21 ` Török Edwin
2008-11-27 12:32 ` Peter Zijlstra
2008-11-27 12:32 ` Peter Zijlstra
2008-11-27 12:39 ` Nick Piggin
2008-11-27 12:39 ` Nick Piggin
2008-11-27 12:52 ` Török Edwin
2008-11-27 12:52 ` Török Edwin
2008-11-27 13:05 ` Nick Piggin
2008-11-27 13:05 ` Nick Piggin
2008-11-27 13:10 ` Török Edwin
2008-11-27 13:10 ` Török Edwin
2008-11-27 13:12 ` Nick Piggin
2008-11-27 13:12 ` Nick Piggin
2008-11-27 13:23 ` Török Edwin
2008-11-27 13:23 ` Török Edwin
2008-11-28 12:10 ` Nick Piggin
2008-11-28 12:10 ` Nick Piggin
2008-11-30 19:38 ` Török Edwin
2008-11-30 19:38 ` Török Edwin
2008-12-01 8:52 ` Nick Piggin
2008-12-01 8:52 ` Nick Piggin
2008-12-01 11:13 ` Nick Piggin
2008-12-01 11:13 ` Nick Piggin
2008-12-01 11:37 ` Török Edwin
2008-12-01 11:37 ` Török Edwin
2008-12-04 22:27 ` Ying Han
2008-12-04 22:27 ` Ying Han
2008-12-05 6:50 ` Török Edwin [this message]
2008-12-05 6:50 ` Török Edwin
2008-11-27 13:08 ` Nick Piggin
2008-11-27 13:08 ` Nick Piggin
2008-11-27 19:03 ` Mike Waychison
2008-11-27 19:03 ` Mike Waychison
2008-11-28 9:37 ` Nick Piggin
2008-11-28 9:37 ` Nick Piggin
2008-11-28 23:02 ` Mike Waychison
2008-11-28 23:02 ` Mike Waychison
2008-11-30 19:54 ` Török Edwin
2008-11-30 19:54 ` Török Edwin
2008-12-01 4:50 ` Mike Waychison
2008-12-01 4:50 ` Mike Waychison
2008-12-01 8:58 ` Nick Piggin
2008-12-01 8:58 ` Nick Piggin
2008-12-01 11:45 ` Nick Piggin
2008-12-01 11:45 ` Nick Piggin
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=4938CF1C.9020503@gmail.com \
--to=edwintorok@gmail.com \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=hpa@zytor.com \
--cc=hugh@veritas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mikew@google.com \
--cc=mingo@elte.hu \
--cc=npiggin@suse.de \
--cc=rientjes@google.com \
--cc=rohitseth@google.com \
--cc=yinghan@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 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.