mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ram Pai <linuxram@us.ibm.com>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fix readahead breakage for sequential after random reads
Date: 27 Jul 2004 08:34:34 -0700	[thread overview]
Message-ID: <1090942474.18635.6.camel@dyn319181.beaverton.ibm.com> (raw)
In-Reply-To: <E1BpMZQ-00016B-00@dorka.pomaz.szeredi.hu>

On Tue, 2004-07-27 at 00:40, Miklos Szeredi wrote:
> Ram Pai <linuxram@us.ibm.com> wrote:
> >
> > Also I think the bug that Miklos, found is really hard to reproduce. Did
> > he find this bug by code inspection? Its really really hard to get into
> > a state where the current window is of size 1 page with zero pages in
> > the readahead window, and then the sequential read pattern to just right
> > then. 
> 
> I found it by accident. I did my testing with the following read
> sequence:
> 
> page offset  num pages
> 7            1
> 0            1
> 35           1
> 23           1
> 42           1
> 33           1
> 29           1
> 100          200
> 
> I did not measure actual performance, but only looked at the length of
> the page vector passed to my filesystem's readpages() method.

right. this pattern is just about right to get into that bad state. Had
you had some more random reads then readahead algorithm will go into the
slow-read mode(readahead-off mode) and you will not bump into this bug.

RP

> 
> Miklos
> 


  reply	other threads:[~2004-07-27 15:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-18 22:30 Miklos Szeredi
2004-07-26 23:29 ` Andrew Morton
2004-07-26 23:56   ` Ram Pai
2004-07-27  0:08     ` Andrew Morton
2004-07-27  4:18       ` Ram Pai
2004-07-27  7:40         ` Miklos Szeredi
2004-07-27 15:34           ` Ram Pai [this message]
2004-08-04 17:38         ` Ram Pai
2004-08-04 19:39           ` Shane Shrybman

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=1090942474.18635.6.camel@dyn319181.beaverton.ibm.com \
    --to=linuxram@us.ibm.com \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    /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

all inboxes | Powered by JetHome®