All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ricardo M. Correia <Ricardo.M.Correia@Sun.COM>
To: lustre-devel@lists.lustre.org
Subject: [Lustre-devel] storing SOM epoch in EA
Date: Tue, 19 Feb 2008 15:23:11 +0000	[thread overview]
Message-ID: <1203434591.10570.3.camel@localhost> (raw)
In-Reply-To: <1203433891.3999.8.camel@localhost>


On Ter, 2008-02-19 at 20:41 +0530, Kalpak Shah wrote:

> The epoch will need to be stored in an external block or
> FatZap (depending on implementation of in-dnode EAs) only in-case the
> file is striped across more than 10-15 OSTs.


That may not be true.
For example, with Matthew's proposed design, we could put the epoch as a
system attribute with "higher priority" (lower index) than LOV data,
which means it would always fit in the dnode even if we have lots of
LOVs.

Regards,
Ricardo

--

Ricardo Manuel Correia
Lustre Engineering

Sun Microsystems, Inc.
Portugal
Phone +351.214134023 / x58723
Mobile +351.912590825
Email Ricardo.M.Correia at Sun.COM
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lustre.org/pipermail/lustre-devel-lustre.org/attachments/20080219/81be0367/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 6g_top.gif
Type: image/gif
Size: 1257 bytes
Desc: not available
URL: <http://lists.lustre.org/pipermail/lustre-devel-lustre.org/attachments/20080219/81be0367/attachment.gif>

  reply	other threads:[~2008-02-19 15:23 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-19  9:48 [Lustre-devel] storing SOM epoch in EA Alex Zhuravlev
2008-02-19 10:28 ` Yuriy Umanets
2008-02-19 10:30   ` Alex Zhuravlev
2008-02-19 10:38     ` Yuriy Umanets
2008-02-19 10:59   ` Vitaly Fertman
2008-02-19 11:11     ` Yuriy Umanets
2008-02-19 11:18       ` Alex Zhuravlev
2008-02-19 12:02         ` Yuriy Umanets
2008-02-19 12:09           ` Alex Zhuravlev
2008-02-19 14:28             ` Yuriy Umanets
2008-02-19 14:47               ` Alex Zhuravlev
2008-02-19 15:10                 ` Yuriy Umanets
2008-02-19 12:13           ` Alex Zhuravlev
2008-02-19 14:30             ` Yuriy Umanets
2008-02-19 14:36               ` Nikita Danilov
2008-02-19 14:44                 ` Yuriy Umanets
2008-02-19 14:39               ` Yuriy Umanets
2008-02-19 14:42               ` Alex Zhuravlev
2008-02-19 20:13               ` Andreas Dilger
2008-02-19 14:59           ` Mikhail Pershin
2008-02-19 15:11             ` Kalpak Shah
2008-02-19 15:23               ` Ricardo M. Correia [this message]
2008-02-19 15:14             ` Yuriy Umanets
2008-02-19 15:19               ` Alex Zhuravlev
2008-02-19 15:28               ` Vitaly Fertman
2008-02-19 15:18             ` Ricardo M. Correia
2008-02-19 16:21         ` Nikita Danilov
2008-02-19 16:27           ` Alex Zhuravlev
2008-02-20 16:10             ` Nikita Danilov
2008-02-19 15:31 ` Eric Barton
2008-02-19 15:42   ` Alex Zhuravlev
2008-02-19 20:19   ` Andreas Dilger
2008-02-19 20:33 ` [Lustre-devel] on-disk SOM attributes [former storing SOM epoch in EA] Vitaly Fertman

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=1203434591.10570.3.camel@localhost \
    --to=ricardo.m.correia@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.