[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <1286265215-9025-1-git-send-email-walken@google.com>
Date: Tue, 5 Oct 2010 00:53:32 -0700
From: Michel Lespinasse <walken@...gle.com>
To: linux-mm@...ck.org, Linus Torvalds <torvalds@...ux-foundation.org>,
Ying Han <yinghan@...gle.com>
Cc: linux-kernel@...r.kernel.org,
Andrew Morton <akpm@...ux-foundation.org>,
Rik van Riel <riel@...hat.com>,
Nick Piggin <npiggin@...nel.dk>,
Peter Zijlstra <peterz@...radead.org>
Subject: [PATCH 0/3] V2: Reduce mmap_sem hold times during file backed page faults
This is the second iteration of our change dropping mmap_sem when a disk
access occurs during a page fault to a file backed VMA.
Changes since V1:
- Cleaned up 'Retry page fault when blocking on disk transfer' applying
linus's suggestions
- Added 'access_error API cleanup'
Tests:
- microbenchmark: thread A mmaps a large file and does random read accesses
to the mmaped area - achieves about 55 iterations/s. Thread B does
mmap/munmap in a loop at a separate location - achieves 55 iterations/s
before, 15000 iterations/s after.
- We are seeing related effects in some applications in house, which show
significant performance regressions when running without this change.
- I am looking for a microbenchmark to expose the worst case overhead of
the page fault retry. Would FIO be a good match for that use ?
Michel Lespinasse (3):
filemap_fault: unique path for locking page
Retry page fault when blocking on disk transfer.
access_error API cleanup
arch/x86/mm/fault.c | 44 +++++++++++++++++++++++++++++---------------
include/linux/mm.h | 2 ++
mm/filemap.c | 41 ++++++++++++++++++++++++++++++++---------
mm/memory.c | 3 ++-
4 files changed, 65 insertions(+), 25 deletions(-)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists