All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Braam <Peter.Braam@Sun.COM>
To: lustre-devel@lists.lustre.org
Subject: [Lustre-devel] read ahead
Date: Thu, 13 Dec 2007 12:09:28 -0700	[thread overview]
Message-ID: <47618368.7000202@sun.com> (raw)
In-Reply-To: <4760B247.4030505@sun.com>



Tom.Wang wrote:
> Hi, Peter
>
> I just talked with Matt about his pCIFS test. In his test, there are 2 
> clients, 2 OST, (stripe_count =2, stripe_size=1M).
> Each client run 1 thread to read a shared file. Each thread(client) 
> will only read data of the shared file from 1 OST, so
> read request is discontiguous (1M step stride I/O) for each of thread, 
> which will not trigger read-ahead,  because
> read-ahead window will be reset once it met discontinuous  read  
> request.  So  kept  read-ahead in the same step
> of stride step ((stripe_count -1) * stripe_size) instead of 
> contiguous  could just fix this problem, and it is what we are
> working now.
>
Finally!  This makes a lot of sense.

> Btw:  we also need this in lustre collective read  ADIO driver,  
> since  we  will also  need  reorganize the  data  as  1client-> 1OST 
>          model  like pCIFS does.

I now see why this stripe behavior with read-ahead is so very important 
for Lustre in some cases.

It would also be important to know that in basic cases we really get as 
good read performance as write.

- Peter -

>          Another alternative way maybe move read-ahead mechanism to 
> osc layer, but maybe a bad idea.
> Thanks
> WangDi
>

  parent reply	other threads:[~2007-12-13 19:09 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-11 18:25 [Lustre-devel] read ahead Peter Braam
2007-12-11 18:42 ` Nikita Danilov
2007-12-11 23:47   ` Andreas Dilger
2007-12-12  0:57     ` Mark Seger
2007-12-12  5:53     ` Nikita Danilov
2007-12-14  0:21       ` Andreas Dilger
2007-12-20 10:20         ` Alex Lyashkov
2007-12-20 20:44           ` Andreas Dilger
2007-12-12 15:52     ` chas williams - CONTRACTOR
2007-12-12 16:41       ` Oleg Drokin
2007-12-13 15:15         ` chas williams - CONTRACTOR
2007-12-13 15:23           ` Oleg Drokin
     [not found]     ` <475F7759.2080103@sun.com>
     [not found]       ` <47603E32.6070203@sun.com>
     [not found]         ` <4760B247.4030505@sun.com>
2007-12-13 19:09           ` Peter Braam [this message]
2007-12-11 18:43 ` Oleg Drokin
2007-12-11 18:59   ` Peter Braam
2007-12-11 19:16     ` Oleg Drokin

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=47618368.7000202@sun.com \
    --to=peter.braam@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.