public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Wu Fengguang <wfg@mail.ustc.edu.cn>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/6] Adaptive readahead updates 3
Date: Mon, 26 Jun 2006 09:52:56 +0800	[thread overview]
Message-ID: <351286764.22182@ustc.edu.cn> (raw)
Message-ID: <20060626015256.GA6120@mail.ustc.edu.cn> (raw)
In-Reply-To: <20060625130704.464870100@localhost.localdomain>

Andrew,

On Sun, Jun 25, 2006 at 09:07:04PM +0800, Wu Fengguang wrote:
> Most patches here are focused on seperating out readahead overheads.

Here are some notes that I forgot to include in the mail:

The three patches:
        [PATCH 3/6] readahead: kconfig option READAHEAD_ALLOW_OVERHEADS
        [PATCH 4/6] readahead: kconfig option READAHEAD_SMOOTH_AGING
        [PATCH 5/6] readahead: kconfig option READAHEAD_HIT_FEEDBACK

make the menuconfig look like this:
        [*] Adaptive file readahead (EXPERIMENTAL)
        [*]   Allow extra features with overheads
        [*]     Readahead debug and accounting (NEW)
        [*]     Readahead hit feedback (NEW)
        [ ]     Fine grained readahead aging (NEW)

With all of the three new options disabled(the defaults), it becomes comparable
to the stock readahead in efficiency when reading big files:

Summary:
                      user       sys       cpu         total
ARA     avg           0.13       5.42      91.62%      6.02 
STOCK   avg           0.13       5.47      91.64%      6.09

Details:

ARA
cp work/sparse /dev/null  0.13s user 5.44s system 92% cpu 5.987 total
cp work/sparse /dev/null  0.11s user 5.42s system 91% cpu 6.028 total
cp work/sparse /dev/null  0.14s user 5.47s system 92% cpu 6.087 total
cp work/sparse /dev/null  0.13s user 5.46s system 91% cpu 6.087 total
cp work/sparse /dev/null  0.13s user 5.45s system 91% cpu 6.070 total
cp work/sparse /dev/null  0.13s user 5.41s system 92% cpu 6.003 total
cp work/sparse /dev/null  0.13s user 5.42s system 91% cpu 6.036 total
cp work/sparse /dev/null  0.13s user 5.36s system 91% cpu 6.003 total
cp work/sparse /dev/null  0.14s user 5.39s system 92% cpu 6.003 total
cp work/sparse /dev/null  0.14s user 5.42s system 92% cpu 6.028 total
cp work/sparse /dev/null  0.12s user 5.36s system 92% cpu 5.937 total
cp work/sparse /dev/null  0.12s user 5.36s system 92% cpu 5.961 total
cp work/sparse /dev/null  0.13s user 5.47s system 92% cpu 6.062 total

STOCK
cp work/sparse /dev/null  0.13s user 5.49s system 92% cpu 6.068 total
cp work/sparse /dev/null  0.15s user 5.38s system 92% cpu 6.012 total
cp work/sparse /dev/null  0.12s user 5.49s system 91% cpu 6.112 total
cp work/sparse /dev/null  0.12s user 5.52s system 92% cpu 6.103 total
cp work/sparse /dev/null  0.13s user 5.57s system 91% cpu 6.203 total
cp work/sparse /dev/null  0.11s user 5.45s system 92% cpu 6.037 total
cp work/sparse /dev/null  0.13s user 5.52s system 92% cpu 6.120 total
cp work/sparse /dev/null  0.14s user 5.43s system 91% cpu 6.070 total
cp work/sparse /dev/null  0.12s user 5.49s system 92% cpu 6.078 total
cp work/sparse /dev/null  0.13s user 5.51s system 92% cpu 6.128 total
cp work/sparse /dev/null  0.13s user 5.45s system 92% cpu 6.061 total
cp work/sparse /dev/null  0.15s user 5.40s system 91% cpu 6.037 total
cp work/sparse /dev/null  0.14s user 5.49s system 92% cpu 6.086 total
cp work/sparse /dev/null  0.13s user 5.46s system 91% cpu 6.106 total

Thanks,
Wu

      parent reply	other threads:[~2006-06-26  1:52 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   ` [PATCH 3/6] readahead: kconfig option READAHEAD_ALLOW_OVERHEADS Wu Fengguang
     [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   ` Wu Fengguang [this message]

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=351286764.22182@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