From: Wu Fengguang <wfg@mail.ustc.edu.cn>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org, Wu Fengguang <wfg@mail.ustc.edu.cn>
Subject: [PATCH 3/6] readahead: kconfig option READAHEAD_ALLOW_OVERHEADS
Date: Sun, 25 Jun 2006 21:07:07 +0800 [thread overview]
Message-ID: <351240952.86721@ustc.edu.cn> (raw)
Message-ID: <20060625130922.216691316@localhost.localdomain> (raw)
In-Reply-To: 20060625130704.464870100@localhost.localdomain
[-- Attachment #1: readahead-kconfig-allow-overheads.patch --]
[-- Type: text/plain, Size: 843 bytes --]
Introduce a kconfig option READAHEAD_ALLOW_OVERHEADS to enable users
to choose extra features that have overheads.
Features with overheads will be disabled by default.
Signed-off-by: Wu Fengguang <wfg@mail.ustc.edu.cn>
---
--- linux-2.6.17-mm2.orig/mm/Kconfig
+++ linux-2.6.17-mm2/mm/Kconfig
@@ -182,10 +182,15 @@ config ADAPTIVE_READAHEAD
It is known to work well for many desktops, file servers and
postgresql databases. Say Y to try it out for yourself.
+config READAHEAD_ALLOW_OVERHEADS
+ bool "Allow extra features with overheads"
+ default n
+ depends on ADAPTIVE_READAHEAD
+
config DEBUG_READAHEAD
bool "Readahead debug and accounting"
default y
- depends on ADAPTIVE_READAHEAD
+ depends on READAHEAD_ALLOW_OVERHEADS
select DEBUG_FS
help
This option injects extra code to dump detailed debug traces and do
--
next prev parent reply other threads:[~2006-06-25 13:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20060625130704.464870100@localhost.localdomain>
2006-06-25 13:07 ` [PATCH 0/6] Adaptive readahead updates 3 Wu Fengguang
[not found] ` <20060625130921.549904049@localhost.localdomain>
2006-06-25 13:07 ` [PATCH 1/6] readahead: context based method - slow start Wu Fengguang
[not found] ` <20060626023529.GB6120@mail.ustc.edu.cn>
2006-06-26 2:35 ` [updated PATCH " Wu Fengguang
[not found] ` <20060625130921.987235199@localhost.localdomain>
2006-06-25 13:07 ` [PATCH 2/6] readahead: backward prefetching method fix Wu Fengguang
[not found] ` <20060625130922.216691316@localhost.localdomain>
2006-06-25 13:07 ` Wu Fengguang [this message]
[not found] ` <20060625130922.816467605@localhost.localdomain>
2006-06-25 13:07 ` [PATCH 5/6] readahead: kconfig option READAHEAD_HIT_FEEDBACK Wu Fengguang
[not found] ` <20060625130923.154258797@localhost.localdomain>
2006-06-25 13:07 ` [PATCH 6/6] readahead: remove the size limit of max_sectors_kb on read_ahead_kb Wu Fengguang
[not found] ` <20060626015256.GA6120@mail.ustc.edu.cn>
2006-06-26 1:52 ` [PATCH 0/6] Adaptive readahead updates 3 Wu Fengguang
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=351240952.86721@ustc.edu.cn \
--to=wfg@mail.ustc.edu.cn \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.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