All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alex Zhuravlev <Alex.Zhuravlev@Sun.COM>
To: lustre-devel@lists.lustre.org
Subject: [Lustre-devel] proposal on implementing a new readahead in clio
Date: Tue, 26 Jan 2010 13:02:32 +0300	[thread overview]
Message-ID: <4B5EBDB8.1030303@sun.com> (raw)
In-Reply-To: <4B56F907.3090308@sun.com>

Hi,

I think we could help a lot if you restructure the proposal a bit:

first of all, describe the algorithm w/o implementation details,
probably using notion of event: read event extending window, io to
get data ahead, read-ahead io completion, hit/miss, etc.

then map these events to specific code paths? explain what kind of
information/mechanism layers miss to implement the algorithm?

z.

On 1/20/10 3:37 PM, jay wrote:
> Hello,
>
> We have discussed the implementation of new readahead in CLIO. Here I
> just send the design document out to ask for comments.
>
> We have already had several inputs from Z(aka bzzz) and other engineers.
> I'm not going to copy those ideas here directly, because I'm afraid to
> distort something, so please reply this email to show your ideas -
> thanks in advance.
>
> Jay
>
>
>
> _______________________________________________
> Lustre-devel mailing list
> Lustre-devel at lists.lustre.org
> http://lists.lustre.org/mailman/listinfo/lustre-devel

      parent reply	other threads:[~2010-01-26 10:02 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-20 12:37 [Lustre-devel] proposal on implementing a new readahead in clio jay
2010-01-22 10:53 ` jay
2010-01-23  7:09   ` Alexey Lyashkov
2010-01-24  1:01     ` jay
2010-01-24  9:18       ` Alexey Lyashkov
2010-01-25  6:17         ` jay
2010-01-25  4:05       ` Nicolas Williams
2010-01-25  6:55         ` Matt Wu
2010-01-25  7:23           ` Andreas Dilger
2010-01-25 15:34             ` Nicolas Williams
2010-01-26 10:02 ` Alex Zhuravlev [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=4B5EBDB8.1030303@sun.com \
    --to=alex.zhuravlev@sun.com \
    --cc=lustre-devel@lists.lustre.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.