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 13:08:22 -0400 [thread overview]
Message-ID: <1210352902.23307.242.camel@pc.ilinx> (raw)
In-Reply-To: <C449C4F5.418F%peter.braam@sun.com>
On Fri, 2008-05-09 at 09:08 -0600, Peter Braam wrote:
> Nono - striping should only be used to get more bandwidth from servers. The
> correct solution to the problem you point out is a lock conversion,
Indeed, I have heard that term being used and figured that that is what
it was all about, however...
> planned
> long ago, still far away maybe (Nikita?).
Given that it's not yet available and won't be for some time, isn't
breaking a file up into many objects via striping a sufficient
alternative to the problem?
Are there other problems caused by striping a file (that technically
doesn't need more bandwidth) that outweigh the benefits of not having to
toss so much cache away when a file is written to (i.e. assuming the
cost of reading the file is high such as it would be on a WAN link)?
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/2051fccf/attachment.pgp>
next prev parent reply other threads:[~2008-05-09 17:08 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
2008-05-09 15:08 ` Peter Braam
2008-05-09 17:08 ` Brian J. Murrell [this message]
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=1210352902.23307.242.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.