readahead stats/tracing, backwards prefetching and more (v3)
From: | Wu Fengguang <fengguang.wu@intel.com> | |
To: | Andrew Morton <akpm@linux-foundation.org> | |
Subject: | [PATCH 00/10] readahead stats/tracing, backwards prefetching and more (v3) | |
Date: | Mon, 19 Dec 2011 18:23:08 +0800 | |
Message-ID: | <20111219102308.488847921@intel.com> | |
Cc: | Andi Kleen <andi@firstfloor.org> | |
Archive‑link: | Article |
Andrew, This introduces the per-cpu readahead stats, tracing, backwards prefetching, fixes context readahead for SSD random reads and does some other minor changes. Changes since v2: - use per-cpu counters for readahead stats - make context readahead more conservative - simplify readahead tracing format and use __print_symbolic() - backwards prefetching and snap to EOF fixes and cleanups Changes since v1: - use bit fields: pattern, for_mmap, for_metadata, lseek - comment the various readahead patterns - drop boot options "readahead=" and "readahead_stats=" - add for_metadata - add snapping to EOF [PATCH 01/10] block: limit default readahead size for small devices [PATCH 02/10] readahead: make context readahead more conservative [PATCH 03/10] readahead: record readahead patterns [PATCH 04/10] readahead: tag mmap page fault call sites [PATCH 05/10] readahead: tag metadata call sites [PATCH 06/10] readahead: add vfs/readahead tracing event [PATCH 07/10] readahead: add /debug/readahead/stats [PATCH 08/10] readahead: basic support for backwards prefetching [PATCH 09/10] readahead: dont do start-of-file readahead after lseek() [PATCH 10/10] readahead: snap readahead request to EOF block/genhd.c | 20 ++ fs/Makefile | 1 fs/ext3/dir.c | 1 fs/ext4/dir.c | 1 fs/read_write.c | 3 fs/trace.c | 2 include/linux/fs.h | 41 ++++ include/linux/mm.h | 4 include/trace/events/vfs.h | 78 +++++++++ mm/Kconfig | 15 + mm/filemap.c | 9 - mm/readahead.c | 301 +++++++++++++++++++++++++++++++++-- 12 files changed, 461 insertions(+), 15 deletions(-) Thanks, Fengguang -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/