All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alex Zhuravlev <Alex.Zhuravlev@Sun.COM>
To: lustre-devel@lists.lustre.org
Subject: [Lustre-devel] storing SOM epoch in EA
Date: Tue, 19 Feb 2008 18:42:03 +0300	[thread overview]
Message-ID: <47BAF8CB.7090903@sun.com> (raw)
In-Reply-To: <05e801c8730c$87cbc7a0$0281a8c0@ebpc>

well, this was one of the reasons I asked lustre-devel@ for inputs.
what else we do consider important to store in inode.

probably we should list all existing and planned EAs and rank them.

also, I've got to think that for some cases we don't need to load
LOV EA. for example, for getattr in case of SOM (size/blocks are
cached on MDS). or for revalidation when client already has LOV EA.

thanks, Alex

Eric Barton wrote:
> Rather than discussing this one EA at a time, should we not
> consider any other EAs (e.g. being considered in current 
> architecture work) that might contend for space in the inode?
> 
>> -----Original Message-----
>> From: lustre-devel-bounces at lists.lustre.org 
>> [mailto:lustre-devel-bounces at lists.lustre.org] On Behalf Of 
>> Alex Zhuravlev
>> Sent: 19 February 2008 9:49 AM
>> To: lustre-devel at lists.lustre.org
>> Subject: [Lustre-devel] storing SOM epoch in EA
>>
>> Good day,
>>
>> some time ago we discussed that it would be very helpful to
>> store epoch in inode on mds. the perfect solution could be
>> to store epoch in old inode body, but there is no much space
>> for this in the body and with DMU we'll have this problem
>> again.
>>
>> given the minimal inode size we use on MDS is 512 bytes, we
>> can store upto 13 stripes in the body. larger EAs go to a
>> dedicated block. if we add 8 byte epoch, then we can store
>> upto 12 stripes in the body. so, epoch stored in EA affects
>> only files with exactly 13 stripes. files with different
>> stripes are unaffected at all.
>>
>> couple lesser concerns are:
>> 1) cpu usage
>> 2) epoch on old filesystem with insufficient inode space
>>
>> any objections to use EA to store SOM epoch?
>>
>> thanks, Alex
>> _______________________________________________
>> Lustre-devel mailing list
>> Lustre-devel at lists.lustre.org
>> http://lists.lustre.org/mailman/listinfo/lustre-devel
>>
> 
> _______________________________________________
> Lustre-devel mailing list
> Lustre-devel at lists.lustre.org
> http://lists.lustre.org/mailman/listinfo/lustre-devel

  reply	other threads:[~2008-02-19 15:42 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
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 [this message]
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=47BAF8CB.7090903@sun.com \
    --to=alex.zhuravlev@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.