All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wu Fengguang <wfg@mail.ustc.edu.cn>
To: Iozone <capps@iozone.org>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Adaptive read-ahead
Date: Fri, 26 May 2006 15:25:38 +0800	[thread overview]
Message-ID: <348628334.03674@ustc.edu.cn> (raw)
Message-ID: <20060526072538.GF5135@mail.ustc.edu.cn> (raw)
In-Reply-To: <104a01c6806f$4be100c0$fd00000a@americas.hpqcorp.net>

Don Capps,

On Thu, May 25, 2006 at 09:51:32PM -0500, Iozone wrote:
> >On Thu, May 25, 2006 at 08:53:09AM -0500, Iozone wrote:
> >>Wu Fengguang,
> >>
> >>   I noticed someone asking for real-world examples
> >>   where a novel read-ahead would be helpful.
> >>
> >>   Ok... 
> >>
> >>   Examples:
> >>
> >>       Structural analysis codes:
> >>           Writes large files, forward sequential.
> >>           then reads them backwards.
> >>
> >>       Weather codes:
> >>           Input from vertical scanning radar is written
> >>           to a file, then the file is processed by strata.
> >>           (Written in column order, read in row order..
> >>             thus a strided reader)
> >
> >Precious data! Thanks very much.
> 
>        The next time you get in your car, or on an airplane,
>        remember that the structural design was done using
>        the structures codes. Without these codes, people
>        , to put it simply, would die.  Also these codes permit 
>        molecular modeling that increases material strength of 
>        the design while reducing weight and cost.  GM, Ford, 
>        AirBus, Boing, and many others run these codes every hour
>        of every day. Yes, they are important, really :-)
> 
>        Without the weather codes, folks would not have
>        received early notification of the tornados, again
>        it's pretty important to those programs :-)
>    
>        Humorus note: Golf club manufacturers are also using
>        structure codes to design better clubs that help bad
>        golfers hit the ball further... Not exactly a noble goal,
>        but yet another example of the critical competitive 
>        nature of the business world and their depencency
>        on structural analysis codes :-)
 
Wow...

> >>       It was the study of these codes that lead to the inclusion
> >>       of Iozone's backwards reader, and strided reader
> >>       test cases :-)
> >>
> >>       If your system does not have a novel read-ahead 
> >>       algorithm then these types of applications will blind
> >>       side the traditional read-ahead algorithm and the 
> >>       performance will be unacceptable.
> >
> >Till now I have not implemented the strided readahead feature.
> >Maybe we should tamp the existing features first :)
> 
>        Or, you could implement the strided feature, as it's
>        pretty easy to detect.  Just need to trigger on two
>        equa-distance accesses: A -> B and B -> C  where
>        C-B = B-A then  the prediction D is C + distance between 
>        A->B or B->C.
>        The math turns out to be  easy to optimize:
>            D= C+(B-A) 
>        for both forward and backward strided readers. 
> 
>        Example:
>        A = 1, B = 3  C=5
> 
>        Forward strided reader reading 1, 3, 5 -> predict 7
>        3-1=2  and 5-3 = 2 and therefore  predict 5+2 = 7
>        or going backwards,  reading 7,5, 3 -> predict 1
>        5-7 = -2 and 3-5 = -2 and  3 + (-2) = 1 ... Cool huh :-)

Maybe it's useful for HPC applications, too. I'll consider it on
time of convenient.  Though it can still be tricky for implementing.
So I'd concentrate on the top-priority thing first: to stabilize the
existing features, so that the majority can enjoy them earlier.

>        Hmmm, I still remember what I wrote 8 years ago... Now that's 
>        amazing.  I can't remember what I had for breakfast today,
>        but this stuff seems fresh in memory banks :-)  (weird)

It's a lucky thing for you to do it 8 years ago ;-)

Thanks,
Wu

           reply	other threads:[~2006-05-26  7:25 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <104a01c6806f$4be100c0$fd00000a@americas.hpqcorp.net>]

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=348628334.03674@ustc.edu.cn \
    --to=wfg@mail.ustc.edu.cn \
    --cc=capps@iozone.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.