From: Brian J. Murrell <Brian.Murrell@Sun.COM>
To: lustre-devel@lists.lustre.org
Subject: [Lustre-devel] Wide area use of Lustre and client caches
Date: Fri, 09 May 2008 10:25:10 -0400 [thread overview]
Message-ID: <1210343110.23307.203.camel@pc.ilinx> (raw)
In-Reply-To: <C449357C.4160%peter.braam@sun.com>
On Thu, 2008-05-08 at 22:55 -0600, Peter Braam wrote:
>
> His use pattern was interesting ? a number of Windows clients must be
> browsing files stored in Lustre in this remote location. It was
> expected that the files would be fairly large, would be viewed by
> multiple clients, and that few or no modifications would be made.
Even still it's useful during implementation to think of the use case of
that remote client having read a file and caching and holding a read
lock on that file, say 1GB in size, and then another client wanting to
update say, 1KB in the middle of the file. It would be beneficial for
that 1GB file to have a small (but still practical) stripe size so that
the amount of cache that needs to be thrown away to accommodate the
write is relatively small.
b.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
URL: <http://lists.lustre.org/pipermail/lustre-devel-lustre.org/attachments/20080509/554406bd/attachment.pgp>
next prev parent reply other threads:[~2008-05-09 14:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-09 4:55 [Lustre-devel] Wide area use of Lustre and client caches Peter Braam
2008-05-09 14:25 ` Brian J. Murrell [this message]
2008-05-09 15:08 ` Peter Braam
2008-05-09 17:08 ` Brian J. Murrell
2008-05-09 18:17 ` Nikita Danilov
2008-05-09 23:01 ` Andreas Dilger
[not found] <372618435.977041214909597153.JavaMail.root@dahlback.prod.local>
2008-07-01 11:03 ` Daire Byrne
2008-07-01 14:56 ` Peter Braam
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=1210343110.23307.203.camel@pc.ilinx \
--to=brian.murrell@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.