From: Kalpak Shah <Kalpak.Shah@Sun.COM>
To: lustre-devel@lists.lustre.org
Subject: [Lustre-devel] storing SOM epoch in EA
Date: Tue, 19 Feb 2008 20:41:31 +0530 [thread overview]
Message-ID: <1203433891.3999.8.camel@localhost> (raw)
In-Reply-To: <op.t6r08rkfatmt0c@garden>
On Tue, 2008-02-19 at 17:59 +0300, Mikhail Pershin wrote:
> On Tue, 19 Feb 2008 15:02:02 +0300, Yuriy Umanets <Yury.Umanets@Sun.COM>
> wrote:
>
> > Alex Zhuravlev wrote:
> >> Yuriy Umanets wrote:
> >>
> >>> EA is separate block is evil. It makes things slow.
> >>>
> >>
> >> we have fast EAs (stored in inode, this is why we make them large) for
> >> years.
> >>
> > Well, people used horses for ages but this did not stop them from
> > building cars :) Guys, I gave you idea, not worse than using EAs. I will
> > not insist it is great. If you can't estimate its value yourself, well,
> > let it be. We have such a nice thing as IAM and you keep talking about
> > EAs...
> >
> > Seriously, IMHO what is bad about EAs:
> >
> > 1. You need to control their size, you need to bother;
> > 2. Large-fast inodes make create/lookup slow. You need to load this
> > thing to memory after all. I think this is complement to additional
> > seeks caused by IAM;
>
> but this is still better than extra block for EA or IAM. Btw IAM data is
> also in memory and takes it no less than extra inode size possibly
>
> > 3. Storing epoch in EA makes you use this chain to access epoch:
> > fid->inode->epoch (in EA), IAM makes it shorter: fid->epoch (in IAM);
>
> not true actually. inode will be read anyway until you are proposing to
> put whole inode body in IAM, so there is no benefits. Moreover inode->ea
> is direct mapping while fid->epoch will need index lookup and may invoke
> several blocks to read if IAM is large and it will be large in this case,
> so IO will be not better than even EA in extra block.
>
> > 4. Large inodes consume more RAM;
>
> this is the same as 2.
>
> Guys, don't forget about DMU as well.
For the DMU, we will be using 1024-byte dnodes by default to store the
striping information. So the epoch can be stored in the in-dnode system
attributes. 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. (The exact number of
striped will again depend on the design of in-dnode EAs)
Thanks,
Kalpak.
>
next prev parent reply other threads:[~2008-02-19 15:11 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 [this message]
2008-02-19 15:23 ` Ricardo M. Correia
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=1203433891.3999.8.camel@localhost \
--to=kalpak.shah@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.